2020.2

access this property inside of any JavaScript code within the data mapping configuration,
use automation.properties.ProcessName.
l
TaskIndex: This property contains the index (position) of the task inside the process that
is currently executing the data mapping configuration but it has no equivalent in
PlanetPress Workflow. To access this property inside of any JavaScript code within the
data mapping configuration, use automation.properties.ProcessName.
In scripts, fixed automation properties are retrieved via the automation object (see "Objects" on
page383), 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 custom runtime parameters, defined in 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.
For more information see: "Properties and runtime parameters" on page226.
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: The scope of a property determines when the property is set and how it can be
accessed (see "Accessing properties and runtime parameters" on page228).
l
Entire Data: These properties are statically set at the start of a job, before anything
else. They cannot be changed once they have been set, in other words they are
global constants. They are mostly useful for static information such as folder
locations or server addresses.
Page 335