2022.1

Note
Runtime parameters are always added to the file currently visible in the workspace.
To add a parameter:
1. Click the Add button. The Add Parameter dialog opens.
2. Give the runtime parameter a name. The name is needed to access the parameter in a
script and to set its source in the automation tool.
3. Optionally, set a debug value. Note that the debug value is never actually used outside of
the DataMapper. Its only purpose is to make it easier to design and test the data mapping
configuration. The actual value of a runtime parameter comes from the automation tool,
e.g. the Execute Data Mapping task or the All in One task in PlanetPress Workflow.
4. Click OK.
Editing a runtime parameter
To modify a runtime parameter, click its name or value in the Parameters pane and enter the
new name or value.
To remove a runtime parameter, select it and click the Remove button ( ).
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298.
l Step settings. Properties can be selected in the Condition, Multiple Conditions and
Repeat step properties (see "Condition step" on page284, "Multiple Conditions step" on
page287 and "Repeat step" on page282).
l Script. Scripts can access properties through the "DataMapper Scripts API" on page408.
(See also: "Using scripts in the DataMapper" on page411.)
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453.)
To change the value of such a property you could use an Action step (see "Action
Page 255