This is the documentation for Clover Club 12.0.
Documentation for the upcoming version Rampur 13.0 can be found here.
Bound Partitions
- Jan Panoušek
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.Â
The data exchange between partitions happens via external JSON API, like any other call, so that the security barrier between the partitions 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 partition' can be saved here. Logics then refer to a given named configuration of such bound partition. It also provides a way to shield credentials from logic writers.
Base URL – Only fill in this field if the partition that the bound call is calling is on a different cluster. If the called partition is on the same cluster, leave this field empty.
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.