Using the Mapping Editor

Last Updated: 12/05/2018 Introduced in Version: 2.0

Each step in your application’s flow accepts input data and returns output data. The output data can be used by other steps with in the flow. For some steps, input data can be provided from multiple data outputs that exist in flow. Use the Mapping Editor to select a data source that you would like to use as an input for a selected step in your flow. You can also define how these inputs should be used before proceeding to the next step.

To access the Mapping Editor, select a step in the Flow Designer work space then click the Edit Input Mappings or the Edit Output Mappings link in the Actions toolbar.


In this example, we will be working with a flow that grabs existing Decisions’ accounts and displays their unique ID’s on a popup.

In this flow, the step For Each Step will accept an array of created accounts . To ensure that this is the case, double click the For Each Step in your work space.



On the right hand side of the screen we have the Properties panel. The Data Type is set to accounts.


The Actions toolbar is located on the bottom of the Edit Step panel. We can the Edit Input Mappings and Edit Output Mappings in separate windows. 
The available data inputs for the For Each Step are located on the left side of the screen. In this example we are not renaming or transforming any data before passing it into our For Each Step. We will focus exclusively on the input data

On the left side of the input mappings view, we see a list of possible data sources with their internal parameters. On the right side we see an empty collection object that is waiting for a data input to get mapped to it. This means that our application knows the For Each Step should expect a collection, or list, of data as its input. However, it does not know what that data is or how it should be used. 


To specify which data source will be used as the input for the For Each Step, we can drag a connection from our intended source to the empty collection data input. In this scenario, we want to pass our array of accounts along to some filters that will remove records that don’t match our criteria of: Active, Can use portal, and belongs to domain. We will use GetAll_Output as our input by clicking and dragging its anchor to the empty collection. Once the connection is made we will see the empty collection update with the path GetAll_Output and a default usage of Select Value.


We have just assigned the Accounts array as the input for For Each Step. Now our flow knows that it should expect the input to come in the form we’ve determined for the Account array, and its internal path is GetAll_Output. If we want, we can also determine how exactly the For Each Step handles this data. Since we want the data to remain unchanged going to the next step, we will leave its mapping type as Select Value. If required we could use the data differently by treating it as a constant, exposing its input, nullifying, ignoring, or any of the other input collection options available.

Additional Resources