Application Mapping Procedure
To map two applications, follow the below procedure:
- Click Integrations from the top navigation bar. The Integrations page is displayed and the New Application Link section on the right side displays the Application 1 and Application 2 drop-down lists.
- Select an application from the left-side column, by clicking the drop-down menu below the Application 1 field (1).
- Select an application from the right-side column, by clicking the drop-down menu below the Application 2 field (2).
- Enter a unique Application Link Name (3) and click Map Apps (4). A new screen is displayed with the application link name (displayed on top) that you provided in the previous screen. The Configuration tab displays the applications that you selected in the previous screen (Application 1 and Application 2).
Enter a unique connection name by clicking the (+) icon (5) next to the Connection Name field (or) If you have already linked an URL with a connection name, click the magnifying glass icon (6). The Available Connections screen is displayed.
It is possible to create a new connection name (with a URL) or use an existing connection name that you have already created.
- Select the required URL by clicking under the Action column against the URL (7).
- Enter the Username and Password (8). Note that you can modify your existing credentials here, if you have one.
Click Validate Connection (9).
- Click Configure.
You have configured an application link.
Enable Application Link
Managing Application Links
You can also use the options in the Home page to manage an existing application link.
- Clicking the Enable All Links enables all the configured links for this group.
- Clicking the Disable All Links enables all the configured links for this group.
- You can edit the generic polling frequency using the Schedule button.
- Clicking the icon for the application link will enable / disable the links based on the current status.
- You can view the details of a saved application link by selecting Home Page, selecting the desired application link, and clicking on the Load Application Link button.
Once loaded, there are 4 operations you can do to an application link.
- Modify Application Link – You can use this option to modify the existing mapping. This will take you to the edit screen similar to what we saw while configuring the mapping. Modifying the application link will maintain its status of the link eg : disabled link will remain in disable after saving the configuration
- Enable/Disable Application Link – You can use this option to toggle the application link status. Once disabled, Flows will ignore the link until it is enabled again. On the home page, you can easily find the ones that are enabled by looking at the icon.
- Delete Application Link – You can use this option to permanently delete an application link.
- Clone Application Link - You can easily make a copy of the existing application link using this option. The Cloned links will be disabled by default.
Conflict Management Strategy
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 it is resolved. When a conflict occurs, it is logged and an email is sent to the configured users in the Notifications section that are stored in the Entity Mapping tab of each application link. If there is no contact information specified in the Entity Mapping tab, the email(s) will be sent to the user(s) configured in the Email Configurations page.
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, that was originally intended for use in the 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, it results in the field values getting swapped.|
Once the Configuration Tab is completed and saved, the Entity Mapping Tab will appear as shown below. This is where the metadata is mapped between the systems.
Sync Type / Operation
The Sync Type allows switching between PUSH or POLL (default) synchronization types in an application link. PUSH must be enabled when the external application is configured to push data to ConnectALL instead of having ConnectALL poll for modifications from an application.
The Sync Operations represent the configurations of the synchronization direction at the application level. By default, both create & update will be selected in both applications. If any of the create/update events need to be prevented in the application, uncheck the options, this will prevent the event during synchronization to the application.
Entity Mapping Tab
An application can have different metadata that you will use to create the mapping. For example, HP QC has domains, projects, and issue types whereas JIRA only has projects and issue types.
The Date Formats field in an Application Link's advanced properties specifies the format that ConnectALL is expecting the application to use when sending dates/times TO ConnectALL.