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.
- Source: Indicates the source of the Record Set metadata:
- Data Mapping Configuration: Executes data mapping on the appropriate source. Select the appropriate data mapping configuration in the list:
- "None" filename: Select to execute default, basic data mapping on the input PDV/VT file.
- "%o": Select to use a dynamic data mapping configuration name. Click on %o to change the expression that determines the name of the data mapping configuration to use.
- Configuration Names: Select the appropriate data mapping configuration. Adding configurations is done through the Send to Workflow option in the DataMapper Module.
- Open data model of selected configuration: Click to view the data model attached to the configuration in the Data Mapper module, to verity that the right one is used. Only works for configurations listed (will not work for "None" or "Dynamic" options).
- Filter: Retrieves records from the Connect Database. This is identical to using the Retrieve Entities task.
- Filter type: Determines at which level to retrieve the records:
- Record: Retrieves one or more Records, whether or not they are part of a Record Set. Output similar to the Create Record Set task.
- Record Set: Retrieves one or more Record Sets, including all their records. Output similar to the Create Record Set task.
- Filter:
- Add a condition: Click to add a new condition line. This adds the line to the current condition level, by default with an AND operator.
- Switch conditions: Click to swap two conditions on the same level, or two groups of conditions.
- Delete the selected condition: Click to delete the currently selected conditions in the list.
- Clear the rule: Click to delete all rules in the list. Note: This cannot be undone.
- Import a rule: Click to open the Browse dialog and load a Rules file. This will load its rules into the list.
- Export the rule: Click to open a Save dialog and save the Rules file to disk.
- Rule Viewer: Displays a text-based view of the condition using operators and parentheses.
- Sort contents: Defines how records are sorted.
- Sort items based on: Displays the current sorting method. To modify the sorting method, click on the [...] button at the right of the box to open the Sort Parameters dialog.
- Metadata: Uses existing metadata, generally the output of a Create Record Set or a Retrieve Entities task set to retrieve Records or Record Sets. This source has no options as it expects valid metadata.
- PDF/VT with Content Creation: Expects a PDF/VT file as an input and executes basic data mapping on the file. This is the same as using the passthrough option in the Create Record Set task. Content Items are created automatically. When this source is selected, the Content Creation tab is disabled.
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.
- Template: Select the appropriate template or option to execute it:
- "None" filename: Select to skip Content Creation completely.
- "%o": Select to use a dynamic template name. Click on %o to change the expression that determines the name of the template to use.
- Template Names: Select the appropriate template name from the list. Adding templates is done from the Send to Workflow option in the Designer Module.
- Preview: Displays a preview of the output generated by the Print context of the selected Template. Not available for the PDF/VT or dynamic template names.
- Section: Use the drop-down or type in a variable name to execute a specific section.
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.
- Output Preset: Select the appropriate Output Creation Preset to use:
- "None": Select to prevent the execution of Output Creation.
- "%o": Select to use a dynamic Preset name. Click on %o to change the expression that determines the name of the Preset to use.
- Preset Name: Select the appropriate Preset to create output with. Adding Output Creation Presets is done from the Sent to Workflow option in the Designer Module.
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.