When two separate applications are connected, there is the possibility that related entities can each be updated simultaneously, creating a conflict. It is important to know when this happens and how a conflict gets resolved. When a conflict occurs, it is logged, and ConnectALL sends an email to the user’s email address mentioned in the Notifications field (on the Entity Mapping tab in the app link). If no email address is specified in the entity mapping tab, the user configured in the Email Settings page will receive an email.
In the Configuration tab, there is a Conflict Management Strategy drop-down box with 4 options:
The application that you select as Fixed takes precedence in case of conflict and the values from the Fixed application will always overwrite the other.
|First In||When you select First In, the change made by the application that writes first will be considered during synchronization (if there is a conflict), and the submission of the second application will be discarded.|
|Last In||When you select Last In, the change made by the application that writes last will be considered during synchronization (if there is a conflict), and the submission of the first application will be overwritten.|
|Swap||No conflict management logic will be used. The Swap strategy is the same as None, which is intended for use in unidirectional app-links and unidirectional field mappings where a conflict-management strategy is not needed. Note that setting the strategy to None/Swap disables the internal processing and caching of the field values. However, If you use Swap in a bidirectional app-link, in the event of a conflict (a mapped field changing on both sides of the app-link in the same poll interval), the field values will be swapped.|
Once the Configuration Tab is completed and saved, the Entity Mapping Tab will appear. This is where the metadata is mapped between the systems.