8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
l All PReS Connect document templates must use the n-up object on both the front and the back pages
of the duplex document.
l Each instance of the n-up object must have the βchange data page with each repeatβ option checked.
l The total number of repeats on each page (vertical X horizontal) must correspond to the number
specified in the Number of virtual pages per physical page option..
l The Alignment setting of each n-up object must be set according to the deviceβs duplicating
capabilities (long-edge or short edge binding).
Input
Any data file with accompanying metadata.
Processing
The metadata is re-arranged and/or duplicated in order to correspond to the options set forth in this task's
properties.
Output
The original data file is output, along with the modified metadata.
General Tab
l Number of virtual pages that appear on each physical page: This is equivalent to the N in N-Up. This
number should be equal to the total number of virtual pages in your PReS Connect document. For
example, a 2 horizontal x 3 vertical is 6-up, so this number should be 6.
l Number of data pages that make up a single duplex virtual document: Either 1 if your document is
duplex (has a front and back), whether the back has variable data or not, or 2 if your document is
simplex or the data is already properly duplicated so the front and back already match.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on " Task Properties Dialog" on page 584.
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.