2019.2

l Execute JavaScript code.
l Set the value for a record property. Record properties are defined in the Preprocessor
step; see "Preprocessor step" on page274.
l Stop the processing of the current record and move on to the next one. Normally an
extraction workflow is automatically executed on all records in the source data. By
stopping the processing of the current record, you can filter out some records or skip
records partially. Note that if the extraction workflow has already extracted some data
before it gets stopped, the record containing that partial data will still be stored in the
Connect Database; to skip a record entirely, the Action step must occur before any data is
extracted for that record.
l Stop the data mapping. If fields of the current record were already extracted, then those
fields are stored as usual, but the rest of the record and any following records are skipped.
The Action step can run multiple specific actions one after the other in order.
Adding an Action step
To add an Action step, right-click on the Steps pane and select Add a Step > Add Action.
Configuring an Action step
For information about how to configure the Action step, see "Text and PDF Files" on page369.
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" on page226).
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.
Page 284