Postprocessor step

The Postprocessor step allows the application to further process the resulting record set after the entire extraction workflow has been executed, using JavaScript.
For example, a postprocessor can export all or parts of the data to a CSV file which can then be used to generate daily reports of the Connect Workflow processes that use this data mapping configuration (see Data mapping configurations).
A postprocessor could also write the results of the extraction process to a file and immediately upload that file to a Workflow process.

The Postprocessor step can contain any number of postprocessors.

Note that postprocessors are not executed automatically while designing the data mapping workflow; you must therefore execute them manually. The reason for this is that postprocessors can potentially be quite lengthy operations that would hinder the automatic refresh of the display whenever anything is changed in the data mapping workflow.

To add a postprocessor:

• Select the Postprocessor step on the Steps pane.

• On the Step properties pane, under Postprocessor, click the Add button .

• Under Postprocessor definition, add the script. Postprocessor tasks must be written in JavaScript (see Using scripts in the DataMapper and DataMapper Scripts API).

Configuring the Postprocessor step

For an explanation of the settings for postprocessors, see Postprocessor step properties.