Basic Value Mapping in ConnectALL supports the user-defined mapping of field-level value sets between applications. Basic value mapping is a one-to-one mapping of the values. Advanced Value Mappinghowever, lets you configure these values based on some predefined matching rules that are explained below. 

You can enable these fields by checking the box next to Enable Advanced Value MappingNote that advanced value mapping is not available for status and project fields.

Predefined Matching Rules

  • Null
  • Value Else
  • Value Skip
  • Value Same


The "Null" rule is triggered when the source sends Null or no value for a given field. This tells ConnectALL what to do if the field in question has no value.

The "Null" rule allows you to update the destination record with a specific value that you provide. Alternatively, you can "skip" updating the destination by setting the destination value to "Value Skip". Both examples are shown in the screenshot below.

When using Null, the direction must be set unidirectional, and it will always be pointing away from "Null."

Value Else

"Value Else" is useful to specify the mapping for values that are not otherwise specified. It serves as a bit of a "catch-all" for any values that you have not specifically mapped elsewhere.

This rule can be used if you wish to update a field with a specific value when the value does not match any of your other value mappings. This can also be used to skip over a value update in a destination. You can also set it to send the same value to a destination; this happens to be the default behavior of ConnectALL, so there is no need to specify that mapping (It's harmless if you do). All three examples are shown in the screenshot below.

The direction of value will always be unidirectional and pointing away from "Value Else."

Value Same / Value Skip

"Value Same" and "Value Skip" are simple expressions that tell what to do to the destination when the source value matches a rule. The direction will always be pointing towards these expressions. 

Use "Value Same" to tell ConnectALL to duplicate a source value in the destination.

Use "Value Skip" to tell ConnectALL not to update the field if a value is selected. This can be used with specific values or in conjunction with a rule such as "Value Else."

Additional Information

Fields with drop-down values

If the field in which a value mapping is being defined is a drop-down, the advanced values will be populated for mapping as shown below. 

Fields mapped to _CONSTANT / _URL

Advanced value mapping cannot be defined for the field mappings with _CONSTANT or _URL options provided by ConnectALL. The checkbox will be disabled as shown below. 

Comment Visibility Mapping

While using applications like Jira, ServiceNow, and AzureDevOps, there are a few fields that you can use to enter comments. These fields include the 'Comments' field in Jira, the 'System History' field in Azure DevOps, and the Work Notes field, Additional Comments fields in ServiceNow. In an automation between Jira<->ServiceNow, you could map Jira’s 'Comments' field and ServiceNow’s 'Work Notes' field. Similarly, if you are creating an automation between ServiceNow<->AzureDevOps, you could map ServiceNow’s Work Notes field and AzureDevOps' System History field. The comments that you enter in these fields could be synchronized (with conditions) and the visibility of the comments could be controlled when you are syncing the comments fields. The comment visibility mapping feature in ConnectALL allows you to enable/disable the visibility of a comment using conditions such as public, private, null, and value skip. This is commonly done when you are creating an automation between Jira<->ServiceNow or Jira<->Azure DevOps or ServiceNow<->Azure DevOps. Let's look at an example scenario when you create an Automation between Jira and AzureDevOps.


If you have mapped Jira’s comments to AzureDevops’ System.History field (to sync into Jira as a private comment) when comment visibility is enabled, and you have specified:
Private (Jira) <== Null (Azure DevOps).

In this scenario, when you add a comment in the System.History field, then, that comment is synced as a private comment in Jira. Further, all the comments will be synced as private comments and none will be synced as public comments.

We have provided several usecases to explain what happens when you sync comments in a Jira-AzureDevOps app-link or a ServiceNow-AzureDevOps app-link or a Jira-ServiceNow app-link. If you are a Jira user, click here to learn about how you can customize comment synchronization.

Enabling Comment Visibility Mapping

To enable comment visibility mapping:

  1. Click the Modify icon against the mapped fields in the Field Mapping Properties section. The Value Mapping screen will be displayed.
  2. Check the box to select the Enable Comment Visibility Value Mapping option.
  3. Click the Save Mappings button to finish.


In a Jira and ServiceNow automation, when you map Jira’s Comment fields to ServiceNow’s Additional Comments field, the Enable Comment Visibility Value Mapping option will be displayed in the value mapping screen as displayed in the image. This will also occur in a ServiceNow and Azure DevOps automation when you map ServiceNow’s Additional Comments field and AzureDevOps’ System.History field.