You can use this integration to create maps comprised of key-value pairs in the form of name:alias. The maps work with the convertField Workflow Engine function to look up the "name" and update the value of a field with the "alias".
The conversion map configuration follows a similar pattern as the configuration for LAM Mapping,
Before you start to set up your integration, ensure you know the following about your conversion map:
The map name.
The keys and values you want create mappings for.
You can use this integration to configure multiple conversion maps. To complete the configuration, you must provide a unique integration name and have at least one conversion map that contains at least one mapping.
Name of the conversion map integration instance.
Type | String |
Required | Yes |
Default | MyMap |
Specifies the name of your conversion map.
Type | String |
Required | No |
Default | conversionName |
Enable the conversion for use in mapping.
Type | Boolean |
Required | Yes |
Default | Unchecked |
Set the match type to case sensitive. Defaults to case insensitive.
Type | Boolean |
Required | Yes |
Default | Unchecked |
Specifies the behavior to perform if there is no match.
Type | One of retain: leave the original value unchanged default: return the default value exclude: actions using this map fail |
Required | Yes |
Default | retain |
Specifies the keys you wish to lookup.
Type | String |
Required | Yes |
Default | <item name> |
Specifies the values you wish to return.
Type | String |
Required | Yes |
Default | <item alias> |
You can use the conversion maps you configure in your workflows. For example, you can use the convertField function to lookup and update a field in an alert or Situation. Remember to use the map name you specified the configuration for the map name in the Workflow Engine Action.
Watch the following video to learn more about Conversion Maps: