2018.2

In scripts, fixed automation properties are retrieved via the automation object (see "Objects" on
page328), for example automation.jobInfo.JobInfo9 or automation.properties.OriginalFilename.
Note
Other variables used in a Workflow configuration are made available to the data mapping
configuration via the Properties subsection of the Preprocessor step (see below).
Properties
The Properties subsection is used to create specific properties that are used throughout the
workflow. Properties can be accessed through some of the interface elements such as the
Condition and Repeat step properties, or in scripts, through the "DataMapper Scripts API" on
page318.
Note
Properties are evaluated in the order they are placed in the list, so properties can use the
values of previously defined properties in their expression.
l
Name: The name of the property used to refer to its value.
l
Scope: What this property applies to:
l
Entire Data: These properties are static properties that cannot be changed once
they have been set, in other words they are Global constants.
l
Each Record: These properties are evaluated and set at the beginning of each
Source Record. These properties can be modified once they have been set, but are
always reset at the beginning of each Source Record.
l
Automation variable: These properties initialize variables coming from the
PlanetPress Workflow automation tool. The name of the property needs to be the
same as the variable name in Workflow. They can be either a Local variable or a
Global variable. For either one, only the actual name is to be used, so for %
{MyLocalVar} use only MyLocalVar, and for %{global.MyGlobalVar} use
MyGlobalVar. If a global and a local variable have the same name (%{myvar} and
%{global.myvar} ), the local variable's value is used and the global one is ignored.
To access a Workflow variable inside of any JavaScript code within the data
Page 283