Data mapping

If your usecase needs values on page to be pre-filled from previous interactions or data sources, “Prefill with value” feature can be used:

📘

Prefil with values

Select a field to pre-fill. You can select from source fields from previous interactions, Apps, Data received from URL, Data receive by API Init or Static data.

Generally, data mapping feature is used not only in the Form Page interactions, but also throughout the Design Studio (such as Apps as well) to use fields from previous interactions.

Data mapping feature includes the ability to:

• By clicking Add source field users can add fields from the ones gathered in previous interactions.
• When Relevant only is selected, the system will automatically offer fields that are applicable (e.g. for “Phone number field” system will look up for the Mobile/Phone from previous interactions.) If the desired field is not there, deselect Relevant only and use Search.

It’s also possible to add not only fields one by one, but also a whole Response Data (JSON object) from a particular interaction that returns data via API or traverse to the specific field in that response object. For that, the user should click on the root and select necessary fields in the drop-down menu.

If some field is an array it’s going to show all the elements in it, but it’s also possible to specify certain array element in the response:

• [0] for the first item
• [1] for the second
• [-1] to access last one

Usually it’s best practice to include all the elements.

If there is a scenario that data from one field might come with empty value or will not exist in the flow, it’s possible to add multiple fields to one, and then, if first one will be empty, second (and next subsequent) fields in the list will get into the response:

Static Data

Maybe there is the need to specify some static data in the field for some testing purposes when there is no payload - then, static data comes in handy.

Click on Add static data, then choose name, type and type in the value of the field. Users then can choose from string, number (Integer), boolean (true/false) and date (mm/dd/yyyy) based on the type of the field that is being pre-filled.

Disable editing of pre-filled fields

For some specific business scenarios we might want to restrict updating pre-filled field values (e.g. PII data such as DOB, SSN etc) but rather ones that are returned from specific service or a document scan, without the ability to amend them.