An automation is a connection between any two application environments. Before you begin, ensure that you have access to the credentials for a user ID that has the highest administrative privileges for each application, as these permissions are required to read the meta-data (eg: available projects and fields).

An application license that you have purchased may be used in as many automations you want. If you wish to create an automation using a new application, a new license must be purchased. Please reach out to to learn more.

Creating a New Automation

Below are the steps to begin creating a new automation:

  1. Click the New Automation button on either the Value Stream (1st screenshot) or List View (2nd Screenshot) screen within the Automations tab.

  2. Select an application from the left-side column, by clicking the drop-down menu below the Application field. Repeat for your second application on the right-side column.

  3. Choose the type of automation from the Type field dropdown. This will allow you to categorize based on its purpose (Synchronization, Trigger, Monitor, DataCollection). In the Name field, enter a unique name for your automation. Note that only letters and numbers are supported in this field.

  4. Click Configure to begin configuring your automation.


Note that these steps can be skipped if you click on a link between two existing connections on your Value Stream view. See more about that procedure here.

Configuring Your Connections

After starting your new automation, you will be redirected to the Connection tab. You'll notice that this tab displays the applications that you had selected in the previous screen. 

Below are the steps to establish a connection between ConnectALL and your application environments.

  1. Enter a unique connection name by clicking the (+) icon next to the Connection Name field. This will provide a pop-up screen where you can fill in the necessary fields. If you have an existing connection that you'd like to use for this automation, click the magnifying glass icon. The Available Connections screen is displayed, where you will then click on the relevant connection to auto-populate. Repeat this process with the other application.


    You have to select the time zone if you have not already chosen one for this particular connection. If you have selected a timezone for this particular connection in the connections screen, that timezone is automatically displayed when you select a connection.

  2. Click Validate Connection to test the connection. ConnectALL will then see if it can connect to the URL with the user credentials provided. 

    If successful, you will see a pop-up that looks like the screenshot below. If the connection fails, then ConnectALL is unable to connect to the server. we recommend trying to re-enter the connection credentials in case something was misspelled or mistyped.

  3. The Type that you'd set in an earlier step will be reflected here. If you wish to change it, then use the dropdown to do so. You will also be able to set your Conflict Management Strategy. Check this section for further details.

  4. Click Configure to complete your connection. 

    You will only be allowed to configure the application link if the connection is successfully validated. Therefore, the Configure button will be greyed out unless and until you have validated your connections. 

Once the Connections Tab is completed and saved, the Entity Mapping Tab will appear as shown below. This is where the metadata is mapped between the systems. See the Entity Mapping section for more details.

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 InWhen 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.
NoneNo conflict management logic will be used. This strategy is intended for use in unidirectional automations and unidirectional field mappings where a conflict-management strategy is not needed. Note that setting the strategy to None disables the internal processing and caching of the field values. If you do use None in a bidirectional automation, however, the field values will be swapped in the event of a conflict (a mapped field changing on both sides of the automation in the same poll interval).