2019.2

{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
mapping configuration, use
automation.variables.variablename
.
l
Type: The data type of the property. For more information see "Data types" on page304.
l
Default Value: The initial value of the property. This is a JavaScript expression. See
"DataMapper Scripts API" on page396.
Note
Entire Data Properties are evaluated before anything else, such as Preprocessors,
Delimiters and Boundaries in the Settings pane (see "Data source settings" on
page250). This means these properties cannot read information from the data sample or
from any records. They are mostly useful for static information such as folder locations or
server addresses.
Preprocessor
The Preprocessor subsection defines what preprocessor tasks are performed on the data file
before it is handed over to the data mapping workflow. Preprocessor tasks can modify the data
file in many ways, and each task runs in turn, using the result of the previous one as an input.
l
Name: The name to identify the Preprocessor task. Click this field to rename the
Preprocessor task.
l
Type: The type of Preprocessor task. Currently there is only one type available: script.
The buttons to the right can be used to add, remove and reorder the tasks and to apply them to
the current data file.
The Export button exports the current data file in its current state. Preprocessing may cost a lot
of time when the data file is very large. You could use the exported file instead of the original
file to avoid preprocessing while developing the workflow configuration.
Page 360