2021.2

Comments: The text entered here will be displayed in the tooltip that appears when hovering
over the step in the Steps pane.
Postprocessor
The Postprocessor subsection defines what postprocessors run on the Data Sample at the end
of the data mapping workflow. Each Postprocessor runs in turn, using the result of the previous
one as an input.
l Name: The name to identify the Postprocessor.
l Type: The type of Postprocessor. Currently there is a single type available.
l JavaScript: Runs a JavaScript Expression to modify the Data Sample. See
"DataMapper Scripts API" on page384.
l Use JavaScript Editor: Click to display the Edit Script dialog (see "Using
scripts in the DataMapper" on page387).
l Add Postprocessor: Click to add a new Postprocessor. Its settings can be modified
once it is added.
l Remove Postprocessor: Click to remove the currently selected Postprocessor.
l Move Up: Click to move the Postprocessor up one position.
l Move Down: Click to move the Postprocessor down one position.
l Apply: Run the Postprocessor.
Note that in the DataMapper and Designer, only one data record is active at any given
time. Therefore, the changes made by the post-processes are only visible on the current
data record (i.e. the one currently displayed). If you change data records, you must press
the Apply button on the Postprocessor step once more.
In order to test a case with multiple records you must either use the data mapping
configuration in a print job through the Designer or in the Execute Data Mapping task in
Workflow so that all records will be processed by the Postprocessor step.
Note
The Apply button has an effect at design time only. It is ignored at runtime. When a
data mapping configuration is executed on the server, all postprocessors are
executed in original order.
Page 380