2018.2
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 2018.2
- Installation and setup
- Basics
- Features
- About Workflow Configurations
- Workflow Configuration resource files
- About data
- Data Repository
- Debugging and error handling
- About printing
- OL Connect print jobs
- PlanetPress Suite print jobs
- PReS Workflow printer queues
- Shared printer queue properties
- Windows Output printer queue
- LPR Output Printer Queue
- FTP Output Printer Queue
- Send to Folder printer queue
- Load balancing
- Associating PlanetPress Design documents and PReS printer queues
- Triggers
- Objectif Lune Printer Driver (PS)
- About processes and subprocesses
- Using Scripts
- Special workflow types
- About Tasks
- About variables
- Special workflow types
- About related programs and services
- The user interface
- Customizing the Workspace
- PReS Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- PlanetPress Design document properties
- Moving and copying configuration components
- Renaming objects in the Configuration Components Pane
- Reordering objects in the Configuration Components pane
- Grouping Configuration Components
- Expanding and collapsing categories and groups in the Configuration Component...
- Deleting something from the Configuration Components pane
- Dialogs
- The Debug Information pane
- The Message Area Pane
- The Object Inspector pane
- The Plug-in Bar
- Preferences
- Other Preferences and Settings
- General appearance preferences
- Object Inspector appearance preferences
- Configuration Components pane appearance preferences
- Default Configuration behavior preferences
- Notification Messages behavior preferences
- Sample Data behavior preferences
- Network behavior preferences
- PlanetPress Capture preferences
- OL Connect preferences
- PDF text extraction tolerance factors
- General and logging preferences
- Messenger plugin preferences
- HTTP Server Input plugin preferences 1
- HTTP Server Input plugin preferences 2
- LPD Input plugin preferences
- NodeJS Server Input plugin preferences 1
- NodeJS Server Input plugin preferences 2
- NodeJS Server Input plugin preferences 3
- Serial Input plugin preferences
- Telnet Input plugin preferences
- PReS Fax plugin preferences
- FTP Output Service preferences
- PReS Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The Process area
- Cutting, copying and pasting tasks and branches
- Highlight a task or branch
- Disabling tasks and branches
- Moving a task or branch using drag-and-drop
- Redo a command
- Removing tasks or branches
- Replacing tasks, conditions or branches
- Resizing the rows and columns of the Process area
- Undo a command
- Zoom in or out within Process Area
- The Quick Access Toolbar
- The PReS Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgments
l ...and step 5 filters out the first page (which means the Metadata unselects the first Data
Page, in effect "hiding" it from the Print Output task).
l Step 6 prints the PDF to a printer. When printing a PDF file in passthrough mode, the
Metadata is inspected to determine which pages should print or not. In this case, Page 1
is unselected in the Metadata, therefore the printer receives the job starting from Page 2,
which is exactly what you want.
l Step 7 prints the entire PDF since no separator page was found.
Now here comes the issue:
l The process moves back up to Task 2 in order to process the second split of the original
PDF. The Metadata file still exists in the process! So far, it doesn't impact the rest of the
process… but wait…
l Let's say in step 3 no separator page is found on page 1 of the second split PDF.
l Step 7 prints that second split PDF… but page 1 is unselected in the Metadata (because
the Metadata was carried over from the last split!) so at the very least, you will be missing
one page. If the second split has more pages than the first one, other pages at the end will
get missing as well, as the Metadata doesn't know about it. Or if it has less pages than the
first one, the last pages will be blank.
To avoid running into the issue, you should use the "Create Metadata" on page470 task to re-
create the Metadata immediately after every split, thus ensuring that the process cannot, in
either branch of the condition, be using the Metadata from the previous split.
Page 83