Execute Data Mapping

The Execute Data Mapping Action Task generates a record set by executing a data mapping configuration on a data source. It can also automatically create a record set from a PDF/VT file without using a data mapping configuration.

Input

Optional. Both main options can refer to external files, but either one can be the active data file using %F. By default the Data Source is set to use the active data file as input.

Processing

The task executes the selected data mapping configuration on the appropriate data source, or converts the PDF/VT into a Record Set directly.

If the data mapping configuration expects a database data source, the Data Source option is ignored and the database is accessed instead. If a PDF/VT file is used, the data mapping configuration option is optional - if one is present, it must be able to read the PDF/VT.

Output

The output to this task is twofold. On the OL Connect Server side, a Record Set containing multiple records is created and saved. On PlanetPress Workflow side, metadata is returned with information about each record set.

Alternatively, it is possible to ignore creation of the Record Set on the OL Connect Server and simply return an XML file containing the full Record Set structure.

Properties

The Execute Data Mapping Action Task properties are as follows:

General Tab

Data mapping configuration: Enter the full path to a valid data mapping configuration (.oldatamapper) file, or use the browse button to find the path.
Data Source or PDF/VT file: Enter the full path to a valid data source compatible with the above data mapping configuration or a PDF/VT file, or use the browse button to find the path.
Output Type group:
- Output IDs in Metadata: Select to only output the Record and Job IDs in the metadata. This does not permit sorting and filtering, but it enhances performance since only minimal data is exchanged between the OL Connect Server and PlanetPress Workflow.
- Output records in Metadata: Select to output the full Record table (no Details table) as metadata in the task. It is then possible to sort and filter the metadata using the regular metadata tools, as long as the Update Records from Metadata option is used in further tasks to use the modified metadata.
- Output results in XML data file: Select to output an XML structure containing the full Record Set including all details table. When this option is used, the Record Set is not saved on the OL Connect Server, the data is simply returned and processing stops on the server side. This option cannot be used with other OL Connect tasks.

Connect Proxy Tab

This tab is common to all OL Connect tasks and defines where to process the jobs send through these tasks. When these fields are empty, they use the defaults set in the OL Connect User Options page of the preferences. Note that defaults are not used unless the configuration is sent to the Workflow service.

Connect Proxy Address: Enter the machine name or IP Address where the OL Connect Server resides.
Port: Enter the port to use to communicate with the OL Connect Server. Default: 9340
Username: Enter the username expected by the OL Connect Server.
Password: Enter the password expected by the OL Connect Server for the above username.

On Error Tab

By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and the task just under it (not within a branch) will be given control of the job file without any modification. Any initial input task that generates an error will stop the process from running as a whole, and output tasks will not generate output. The On Error tab can be used to overwrite the default behaviors.

Send to Process: Check this option to send the job file to an error management process.
Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available:
- Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process.
- Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
- Stop Process: The process is stopped and no more processing is done. No further output is produced.
Log Message: Check this option to enable logging a custom error message in the PlanetPress Suite Workflow Tools' log file.
Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PlanetPress Suite Workflow Tools' log file. You can use any variables available in PlanetPress Workflow to customize the message.
Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content.
ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PlanetPress Suite Workflow Tools' log file.
Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID.
Reset to defaults: Resets all options in this tab to their default values.

If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.

Common Errors

Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc.

Comments Tab

The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in The Task Comments Pane.