Introduction

When using applications such as Jira, ServiceNow, Tricentis Tosca, or Microfocus ALM, you will be working with entities. And in each of these applications, when a record is created for any entity, a record ID is created for that record.

In scenarios where you create multiple automation to link different entities of two applications, ConnectALL enables you to translate the record IDs of the records in one particular automation through another automation to the destination application. (i.e) You will be able to translate the ‘Record ID’ of an app-record used in automation (automation A) through another automation (automation B).  ConnectALL achieves this by reading the record IDs used in the other automations (of the same app URL) and translating them to the destination. To make ConnectALL read the record IDs from another automation, you are required to enable the option – ‘Translate Record ID’ in the ‘Field Configuration' screen. 

Note that to use this feature the automations should belong to the same URL.

Enabling Record ID Translation

1. Create an automation or modify an existing automation, and navigate to the Field Mapping tab.
2. Under Field Mapping Properties, click the cogwheel icon against a mapped row. The Field Configuration screen will be displayed.
3. Click to select the ‘Enable’ check box against the Translate record id field. The Automation field displays the automation that you can select to read the record IDs from.
4. Check the box next to the desired automation from the ‘Source’ or the ‘Destination’ application. The below image illustrates this.

Note: Enabling Translate record id, and selecting an automation from where you want to read the record IDs, can be done either in the ‘Source’ and/or in the ‘Destination’ application. Your record IDs will be translated based on the selection.

Let’s see how Record ID translation is done in some common automation combinations.

Tosca and ALM

When you are creating multiple automations to link different entities of Microfocus ALM and Tricentis Tosca, It is possible to translate the ‘Record ID’ of records linked in one particular automation, through another automation.

For example, lets say you have three automations:

• Automation A – Execution list (Tosca) and Test Set (MicroFocus ALM)
• Automation B – TestCase (Tosca) and TestCase (MicroFocus ALM)
• Automation C – Execution Entry (Tosca) and Test Instance (MicroFocus ALM)

In the above scenario, it is possible to translate the record IDs of Automation (A) and Automation (B),  through the third Automation— (C). The below table illustrates this.

In the above scenario, in the automation, click the cogwheel icon against the Test Case ↔ Test ID and  Execution List ↔ CycleId field mapping rows. 

Enable the ‘Translate record ID’ option against the Translate Record ID field on both sides. When you do that and select,

• • Automation B under Test Case (in the row Test Case ↔ Test ID) — Whenever a record is created, the record ID  'Test ID=4442' will get translated to '502 (Test Case)' and will be synced to Tosca. 
  • Automation A under Execution List (in the row Execution List ↔ CycleId) — Whenever a record is created, the ID 'Cycle ID= 4441 will get translated to '501 (Execution List)' and will get synced to Tosca.

Atlassian Jira and ServiceNow

In the case of Jira and ServiceNow, you would have noticed that Jira has Summary, Description fields, and ServiceNow also has Summary and Description fields. When you are creating multiple automations to link the above entities of Jira and ServiceNow, It is possible to translate the ‘Record ID’ of a particular field linked through a particular automation/automations, through a different automation.

For example, let’s say you have two automations:

• Automation 'jira2snow' between Jira’s bug and ServiceNow’s issue, linking the following fields:
• Short description (ServiceNow) ↔ Summary (Jira)
• Description (ServiceNow) ↔ Description (Jira).
  

Once you have created the automation linking the fields as described above, create a record from Jira and sync it to ServiceNow. When the record syncs successfully, a sys_id in ServiceNow will be created. Let’s call that ‘X’.

• Automation 'TestRecordID' linking the following fields:

• Short Description (ServiceNow) ↔ Summary (Jira)
• Description (ServiceNow) ↔ Description (Jira)
• Correlation ID ↔  External ID 

Now, we are going to enable the record ID translation in automation B, through the 3rd field Mapping row between Correlation ID and External ID, and select automation 'jira2snow' in the Automations field drop-down list. The below image illustrates that.

Now, as you have selected the automation 'jira2snow, the record ID 'X' that got generated for the record in automation 'jira2snow’ will be synced to the destination field (Correlation ID) of ServiceNow in this automation.