2021.1

You can also define custom runtime parameters. With those, you could, for example:
l Pass a JSON structure, containing boundary information as well as the name and
location of fields to be extracted dynamically from a data stream. This way, a generic data
mapping configuration could be used to process several kinds of different files.
l Define default values that are different from one data mapping instance to the next, even
when using the same data mapping configuration.
Defining custom properties and runtime parameters
Defining properties
You can define custom properties properties under Properties in the "Preprocessor step" on
page255 (see "Preprocessor step properties" on page341).
To add a property:
1. Select the Preprocessor step on the Steps pane.
2.
On the Step properties pane, under Properties, click the Add button . See
"Properties" on page343 for an explanation of the settings for properties.
Defining runtime parameters
Custom runtime parameters in a data mapping configuration are defined via the Parameters
pane. This can be found next to the Data Model pane at the right. If it isn't visible, use the menu:
Window > Show View > Parameters to make it visible.
Note
The source of a runtime parameter value must be set in the automation tool, e.g. OL
Connect Workflow, in the Runtime Parameters section of the OL Connect task that uses
the data mapping configuration. (See All In One and Execute Data Mapping in the Online
Help of Workflow.)
To add a runtime parameter, start by opening the data mapping configuration to which the
parameter should be added. Make sure the data mapping configuration is visible in the
workspace; then open the Parameters pane.
Page 229