Changes in Suffixes Used in the Mapper
The suffixes used in the mapper have undergone some changes. Due to this, you may receive a mapper-related warning in the dialog when importing an existing app. Click Continue and the app imports successfully. After the import completes, be sure to remap the properties in the activities that show errors. This ensures that they switch to the new suffix format.
The following table lists the changes in the suffixes:
Original suffix appearing in imported apps | New suffix used by the Mapper (after you remap) | For example | Used when mapping |
---|---|---|---|
Activity_id. Activity_parameter |
$Activity[Activity_id]. Activity_parameter |
Old suffix:
New suffix after remapping property:
|
When mapping to a parameter in the Activity's output. Used to resolve Activity params. |
$TriggerData | $trigger | Old suffix:
New suffix after remapping property:
|
When mapping from the output of the trigger to the flow input |
N/A
There was no equivalent for this in the old mapper |
$flow.headers.parameter $flow.body.parameter |
$flow is a newly introduced suffix, which did not have an equivalent suffix in the old mapper.
|
When mapping to any parameter in the flow's header or input schema (schema entered on the Input tab of Flow Inputs & Outputs dialog) which is the same as the output of the trigger, since the output of the trigger is mapped to the input of the flow. Used to resolve parameters from within the current flow. If a flow has a single trigger and no input parameters defined, then the output of the trigger is made available via
|