Define how GID is computed. Properties that can be used depends on module we synchronized
Type of object this configuration is applied to
On the synchronization configurator item's view, everything is editable. You can define :
- ID : must be PortalType_configurator
- Portal Type : Type of object this configurator is related to, usually one per module. Default value must not be change
- Synchronization Order : Integer to let TioSafe the order, the lower the first.
- Publication / Subscription : link to synchronization object. Default values must not change/
GID Part :
GID is used as a global ID between the SaaS application and TioSafe, this means it should depends only on properties exchanged between application so that with a given GID we can retrieve the same object the two applications. GID can be configured with this form as application constraints are not always the same. For example, on one application, all products are uniquely identified by a reference, on another, it is the ean13 which is used to do this. So
- Prefix : prefix used in GID, usefull to distinguish same kind of object coming from differents applications (sale orders coming from multiple e-commerce applicaion). This can prevent collision between reference of sale orders.
- Property : list of object properties that can be used to uniquely identify it, this can be a combination for example : first name + last name + birthdate