8.18.32016-03-14

All In One

The All In One action task is a combination of 4 different OL Connect tasks within a single one. This makes creating Print content faster and more easily, as the task is optimized for this specific purpose with less data exchanged with the server as well as multi-threading support.

The task is build with 3 tabs that represent the 3 main steps of the creation of a Print Output: Data Mapping, Content Creation and Output Creation. In this case, Job Creation is implied and equivalent to a single created job.

Data Mapper Tab

The Data Mapper tab generates a Record Set from a specific source: data mapping on the appropriate source (Current Data File, Database or PDF/VT data file), Retrieving items from the Connect Database (filter setting) or uses the current job Metadata. The resulting Record Set is given to the Content Creation part of the task. In order to optimize the process, blocks of 100 records are sent sequentially to the Content Creation in parallel, instead of waiting for the whole record set to be created.

Content Creation Tab

The Content Creation tab generates Content Items either by merging a Record Set with a Template, or by processing a PDF/VT file into individual content items.

Output Creation Tab

The Output Creation tab generates the output for the current job, using the selected Output Creation Preset. Note that the "Job Creation" task normally necessary when using the individual tasks is implicitly executed before output creation.

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.

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.

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.