2020.1

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331 for an explanation of the settings for properties.
Accessing properties and runtime parameters
There are different ways to access properties and runtime parameters in a data mapping
workflow.
l
Property-based fields. A property-based field is filled with the value of a property. See
"Property-based field" on page265.
l
Step settings. Properties can be selected in the Condition, Multiple Conditions and
Repeat step properties (see "Condition step" on page251, "Multiple Conditions step" on
page254 and "Repeat step" on page249).
l
Script. Scripts can access properties through the "DataMapper Scripts API" on page368.
(See also: "Using scripts in the DataMapper" on page371.)
l
The sourceRecord object has a properties array that lets you access custom
properties that are added to each individual record, i.e. the scope of the property is
set to Each record. (See: "sourceRecord" on page403.)
To change the value of such a property you could use an Action step (see "Action
step" on page255). Note that the property's value will be reset at the beginning of
each source record.
l
The data object has a properties array that lets you access custom properties
that are added to the data as a whole, i.e. the scope of the property is set to Entire
data. (See: "data" on page385.) These are read-only.
l
To access a runtime parameter inside of any JavaScript code within the data
mapping configuration, use
automation.parameters.runtimeparametername. (See: "Objects" on
page378.) Runtime parameters are read-only.
Extracting data
Data are extracted via Extraction steps into fields in the Data Model. This topic explains how to
do that.
Fields can also be filled with other data: the result of a JavaScript or the value of a property. To
learn how to do that, see "Fields" on page263.
Page 225