All In One

The All In One task extracts data from the job file, merges the data with a Connect Designer template, and creates print output. (See also: OL Connect print jobs.)

This task is a combination of 4 different OL Connect tasks within a single one. This makes creating Print content easier and faster, as the task is optimized for this specific purpose. It exchanges less data with the server than the separate plugins do and it has multi-threading support: it can produce the data set and content items in parallel.

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 a Print process built with separate plugins, the Job Creation task comes between Content Creation and Output Creation. With the All In One, Job Creation is implied and equivalent to a single created job; it isn't possible to use a Job Preset.

This task can be added as an Action task (see Action Tasks) or as an Output task (see Output Tasks). Adding it as an Action task enables the process or branch to continue after this task. An Output task is always located at the end of a process or branch.

Task properties

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": 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.
      Click the Open data model of selected configuration button to view the data model attached to the configuration in the Data Mapper module, to verify that the right one is used. Only works for configurations listed (will not work for "None" or "Dynamic" options).
    • No storing or post-processing of the data records (faster): This option prevents data from being written to the database. Instead, records are streamed directly into the Content Creation process for immediate merging. Turning this feature on can improve data mapping performance significantly, as well as the time required for the cleanup process. However, since the data is not written to the database, there is no way to do post-processing on the extracted data after the All In One operation has completed. Any post-processors defined in the data mapping configuration will be disabled.
      This option is unchecked by default.
  • 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 Execute Data Mapping or a Retrieve Items 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 Execute Data Mapping task. Content Items are created automatically. When this source is selected, the Content Creation tab is disabled.
    Once the All In One plugin has been executed with this option selected, any task that attempts to access records in the database will fail.

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.

By default the entire Print context is printed. Printing selected Print sections can only be achieved with a Control Script in the template (see Control Scripts in the Designer Help).

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. In this case the All In One can be combined with the Create Job and Create Output tasks and thus also with a Job Preset and Output Preset.
  • "%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.

OL Connect Proxy Tab

This tab is common to all OL Connect tasks and defines where to process the jobs sent through these tasks. When these fields are empty, they use the defaults set in the OL Connect User Options page of the preferences.

• OL 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
• User name: Enter the user name expected by the OL Connect Server.
• Password: Enter the password expected by the OL Connect Server for the above user name.

On Error Tab

Comments Tab

The Comments tab is common to all tasks. It contains a 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.

Check the option Use as step description to display the text next to the icon of the plugin in the Process area.