2019.1

page234). 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.
Preprocessor definition
l
Expression: Enter the JavaScript code to be performed on the data file. See
"DataMapper Scripts API" on page378.
Extract step properties
The Extract step takes information from the data source and places it in the record set that is
the result of the extraction workflow. For more information see "Extract step" on page260 and
"Extracting data" on page238.
Description
This subsection is collapsed by default in the interface, to give more screen space to other
important parts.
Name: The name of the step. This name will be displayed on top of the step's icon in the Steps
pane.
Page 344