Scopes in Data Mappings
The Available data pane in the mapper displays the output data from preceding activities, triggers, and flow inputs. This area groups the output elements based on a scope. A scope represents a boundary in the Available data within which an input element can be mapped. For example, when mapping an input element to an element from the output of a trigger, the scope of the input element is represented in Available data as $trigger. The following scopes are currently supported by the mapper.
| Scope Name | Used to... | Available in... |
|---|---|---|
| $trigger | Map flow input to trigger output. | Trigger (Map to Flow Inputs tab) to map flow inputs to trigger outputs. |
| $flow | Map flow output to trigger reply. |
|
| $activity.[activity-name] | Map input elements of the activity to elements from the output of previous activities. |
$activity represents the scope of an activity. [activity-name] indicates the activity whose scope you are defining. Each preceding activity has its own scope in the mapper. |
| $iteration | Keep track of the current iteration and is available only when iterator is enabled for an activity on the Loop tab. | Input tab of an activity that has Loop enabled. This tab is displayed only when the Loop for the activity is enabled. The following elements are displayed under
$iteration:
|
| $property [property-name] | Map to app properties that are defined in the app. | As long as there are app properties defined in the app, this scope is available for mapping from any activity that allows mapping. |
| $loop | Map elements within an array. | $loop is prefixed to the element name when mapping an element that is within an array. The scope of $loop is the current array that you are iterating through. |