Data referencing is a powerful way to re-use data created in Next Matter process instances. Some use cases require different formatting options, which are not shown in the user interface.

These hidden ways to format references can be inserted anywhere in the process (for example in an instruction field or in an integration step):

  • JSON formatted data reference. This returns a properly formatted json, where for example quotation marks or line breaks are automatically escaped properly.

{{"process_step": STEPID, "process_step_action": ACTIONID, "output_data_variable":"inputValue", "formatting": "json"}}

  • String formatted data reference

{{"process_step": STEPID, "process_step_action": ACTIONID, "output_data_variable":"inputValue", "formatting": "plain"}}

STEPID refers to the id of a step, which can be found in the url of the step either in the editor or the executor. The ACTIONID is the id of the field that should be referenced and can be accessed in the process editor.

Examples for referencing data from different actions types

Adress

{{"process_step": 141487, "process_step_action": 369584, "output_data_variable":"street", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369584, "output_data_variable":"street", "formatting": "plain"}}

Checklist

{{"process_step": 141487, "process_step_action": 369585, "output_data_variable":"itemsChecked", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369585, "output_data_variable":"itemsChecked", "formatting": "plain"}}

Date

{{"process_step": 141487, "process_step_action": 369586, "output_data_variable":"date", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369586, "output_data_variable":"date", "formatting": "plain"}}

File

{{"process_step": 141487, "process_step_action": 369587, "output_data_variable":"files", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369587, "output_data_variable":"files", "formatting": "plain"}}

Multi Value Dropdown

{{"process_step": 141487, "process_step_action": 369589, "output_data_variable":"itemsSelected", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369589, "output_data_variable":"itemsSelected", "formatting": "plain"}}

Radio

{{"process_step": 141487, "process_step_action": 369590, "output_data_variable":"radioItemSelected", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369590, "output_data_variable":"radioItemSelected", "formatting": "plain"}}

Single Value Dropdown

{{"process_step": 141487, "process_step_action": 369592, "output_data_variable":"itemSelected", "formatting": "json"}}
{{"process_step": 141487, "process_step_action": 369592, "output_data_variable":"itemSelected", "formatting": "plain"}}

String

{{"process_step": 141487, "process_step_action": 369591, "output_data_variable":"inputValue", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369591, "output_data_variable":"inputValue", "formatting": "plain"}}

URL

{{"process_step": 141487, "process_step_action": 369593, "output_data_variable":"url", "formatting": "json"}}

{{"process_step": 141487, "process_step_action": 369593, "output_data_variable":"url", "formatting": "plain"}}

In integration step bodies, the following formatting options are supported as well for file and image uploads.

  • "base64": Used only for references to a single file. The file content will be base64-encoded

  • "zip": Used only for file references. All files are downloaded and zipped

  • "base64+zip": The combination of the two: A base64-encoded zip file.

Did this answer your question?