On this page, you can store authentication credentials to other Pricefx partitions or any other (non-partition, non-Pricefx) systems.
Generally, partitions are isolated data buckets that do not allow any data exchange. But some projects have multiple partitions (e.g., one per business unit or per region) and may need to share data between these partitions. In such case they can use the Bound Partition feature.
To add a new bound Pricefx partition credentials, click Add Partition and enter the required information. If you need to call an external system, use the Add System option where the Partition Name field is omitted.
The data exchange between partitions/systems happens via external JSON API, like any other call, so that the security barrier between the partitions/systems is kept. These calls need to be authenticated like any other call. In order to not specify this in the logics themselves (and provide an easy way to update credentials), the connection details of a so called 'bound system' can be saved here. Logics then refer to a given named configuration of such bound partition or system (api.boundCall, api.boundExternalSystemCall). It also provides a way to shield credentials from logic writers.
When using api.boundCall, the bound partition must always be set up against some technical account created specifically for the bound call purpose. Never use personal accounts, since these will get removed when a person leaves the company or by the customer during regular security audit checks. The customer is the authority to maintain accounts and therefore should provide an email address for that account since pricefx.eu/com addresses get automatically deactivated.