When you are mapping fields, in the field mapping tab, you will notice some fields displayed below the regular fields for both the left and right side applications (below image). These fields are called system fields and they allow you to sync the field information that cannot be mapped using the regular work items available in the field mapping tab for an application. The system fields include _CONSTANT, _DO_NOT_SYNC, _ISSUE-TYPE, etc., ConnectALL supports the below system fields which describes the metadata information of the applications. These fields will be available for all the applications that ConnectALL supports.
Project and IssueType
The Automation Properties pane in the Entity Mapping tab contains metadata information. For example, in Jira, the project and issuetype in the Automation Properties pane represent the metadata fields. In the below image the "project" and "issue type" represent the metadata of a Jira application.
On the Field Mapping tab, both the '_PROJECT' and 'ISSUETYPE' fields are metadata fields that allow you to access specific information. When mapped to string fields, the _PROJECT and _ISSUETYPE fields will then respectively populate the project and issue type configured in the automations.
Note that these fields can change depending on the field that a particular application uses. For example, some applications use entities instead of issues, and for such applications, the _ISSUETYPE metadata field will turn to _ENTITY (example: Salesforce). So the fields that are displayed depend on the application itself.
These fields will have sync direction set to the right or left (The sync direction will be away from that field) and can be mapped only once. Also, they can be mapped to non-meta data fields, non-constant fields, and non-_DO_NOT_SYNC fields.
The data type of these metadata fields will be _METADATA. These fields have two attributes, namely ID and Name. Name will be the selected default attribute. However, it can be changed to ID by clicking on the cogwheel icon next to the field mapping, and then updating the CA Field Type field on the Field Configuration pop-up.
This field allows you to access specific information related to a record that you have mapped. The _MESSAGE ID field allows you to access the unique record ID based upon a record that ConnectALL has synced and created. Note that every record sync in ConnectALL will have a unique ID, and this _MESSAGEID field is used for the unique ID sync. These fields will have a sync direction set to the right and can be mapped only once. Also, they can be mapped to non-metadata fields, non-constant fields, and non-_DO_NOT_SYNC fields.
Do Not Sync
The _DO_NOT_SYNC field allows the data to be available for the business rule scripts without synchronizing. Say you want to build data based on a business script, and you don't want that data to be synchronized, you can do that using the _DO_NOT_Sync fields. This field will have a sync direction pointing to the left (no data flows out of _DO_NOT_SYNC). Also, note that a _DO_NOT_SYNC field can be mapped multiple times and it can be mapped to non-metadata fields, non-constant fields, and non-_DO_NOT_SYNC fields.
Currently, this feature supports only a single project configuration. In the future, it will be extended to a Multi-Project configuration.
As the name suggests, the field ‘_CONSTANT’ is used for mapping fields that have constant values. In other words, this field allows you to tell ConnectALL, that the value mapped will remain a constant in both applications. Let’s say you have an automation between Jira (source) and Microfocus ALM (destination). In Jira, you have the priority value set as ‘2’ and you’ve mapped this value to ‘Constant’ in ALM. The field mapping will look like: _CONSTANT → Priority, and the value mapping for this row will be set as 2/Medium. So every time a record is created in ALM, the priority value in Jira will be 2.
This field allows you to map the URL of a record to the other application. When you map the _url field to a custom field with datatype string/URL, the URL of the record id will be synced. For example, you have an automation between Jira and ServiceNow and you have mapped the URL field (of Jira) >> customstring (of ServiceNow), and you create a record in Jira, say ab-1234. When you do that, the entire URL of the record will be synced to the custom field. The custom field in ServiceNow will hold the data as:
The Default Relationships field is used in mapping issue links of two applications. When creating an automation, if ConnectALL allows you to choose the issue links through ‘Link Type’ fields, you can use this field.
As an example, a user could map the 'Default Relationship' of Jira and the 'Link Type' field of Cherwell. And the relationship between an 'Incident' and a 'Problem' in Cherwell, in this case, would be established by value mapping.