This document presents data mapping on our Platform and provides a detailed description of the new mapper UI.
Components that receive data from previous steps must be mapped to those steps for proper data processing. Data mapper matches the data from trigger Component to the corresponding fields in the action Component, and that’s what we call mapping. You can read all about our current way of data mapping here. The process remains basically the same, but there is a different UI for it.
You will arrive at Step Configuration, which presents some of the following settings in tabs, depending on the Component. You may be familiar with them, but to be sure, let’s go over each one.
In this tab you select the Component for this step.
Here you can select the required Component version. As versions may differ by functionality, sometimes it is essential to use the most recent or a bit older one, depending on the task requirements.
Some Components have more than one way of operation, so you are prompted to select one.
Some Components allow you to configure Local Agent.
Credentials hold authentication data for Components. In this tab you can select from the available credentials, add new ones, verify and save them. Also you can edit and delete existing credentials.
The actual mapping tab. Here you provide data input for fields required by the Component. There are three methods of mapping: Integrator view, JSONata view, and Developer Mode.
Integrator view is the standard mapping view, where you can see all the data fields:
JSONata view is intended for JSONata expressions in fields. You can switch to this view like this:
In both views you can evaluate the expressions and see which data will be seen as the result. As you can see, our
First Name and
Last Name in the field resulted in the complete name:
If you want to code your mapping manually, you can use the Developer Mode:
Data is evaluated the same way in Developer Mode, with green light showing that everything works, and red, if not:
Then, you can switch back to Integrator view:
This is where you retrieve a data sample. A data sample is an example of Component output data. It is essential in building integration flows, because it allows you to see what sort of data the next component in the flow will receive from the previous one. With this information you can configure the next component to act properly on the input it receives.
Tab for Step description. This is optional, but consider adding detailed descriptions to your Steps. This way Flow users won’t have to nag you with questions. Additionally, there may be Credentials here, and a passthrough switch to turn passthrough on and off for this step.