Preprocessor step

The Preprocessor step allows to modify the incoming data through a number of preprocessors prior to executing the rest of the extraction workflow (see Preprocessor actions). It also lets you define properties and runtime parameters that can be used throughout the data mapping workflow.

For a complete overview of the settings for a Preprocessor step, see: Preprocessor step properties.

Properties and runtime parameters

A data mapping configuration's properties hold data that can be used throughout the data mapping workflow to compare against in conditions or to complement the existing data.
Runtime parameters are properties that will pass information from OL Connect Workflow to the data mapping configuration.

For more information see Properties and runtime parameters.

Preprocessor actions

The Preprocessor step can contain any number of actions. They will be performed in sequence before the data is sent to the data mapping workflow.
A preprocessor action could remove certain records altogether.

One example of how a preprocessor action could be used is given in a How-to: Using Preprocessors in DataMapper.

Note that preprocessor actions are not executed automatically while designing the data mapping workflow; you must therefore execute them manually. The reason for this is that preprocessor actions 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 preprocessor action:

  1. Select the Preprocessor step on the Steps pane.

  2. On the Step properties pane, under Actions, click the Add button.

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