2019.1
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 2019.1
- 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
- PlanetPress 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 PlanetPress 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
- 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
- PlanetPress Fax plugin preferences
- FTP Output Service preferences
- PlanetPress Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The user interface
- Customizing the Workspace
- PlanetPress 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
- 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 PlanetPress Workflow Ribbon
- The Task Comments Pane
- Knowledge Base
- Legal Notices and Acknowledgements
"Anoto" and the Anoto logotype are trademarks owned by Anoto AB. PLANETPRESS
CAPTURE is based on Anoto Digital Pen and Paper Technology, which is covered by
over 200 patents worldwide, including but not limited to US6663008, US7172131,
US7248250, US7281668, JP3872498, JP3842283, CN1595440, SE517445,
RU2256225, and AU773011.
Capture Condition
The Capture Condition task checks the status or field contents of a Capture document that has
been processed by the Capture Field Processor action task.
This task is put into effect in the following use cases and example processes:
l Capture Post Processing Workflow
l Capture Web Manager Workflow
Input
A data file in PGC or PDF format that is accompanied by valid Metadata. This Metadata must
contain Capture information and is generally available after a "Capture Fields Processor" on
page473 or "Find Capture Documents" on page481 task. However, it is also possible to
directly retrieve the required information from a specific Document ID. When a specific ID is
used, the data file and Metadata are completely ignored by this task's condition rules, and the
database information is used instead.
Processing
The condition is evaluated using the specified rules, combination (condition is true when...) and
scope (condition scope).
Output
The original data file and Metadata is output by this task. If the rules used in the condition return
True, the data and Metadata is sent down in the condition's branch. Otherwise, this same
information is sent in the trunk.
Task properties
General Tab
Page 465