2018.1
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 2018.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
- 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
- Triggers
- Load balancing
- Objectif Lune Printer Driver (PS)
- Associating PlanetPress Design documents and PReS printer queues
- About processes and subprocesses
- Using Scripts
- Special workflow types
- About Tasks
- About variables
- Workflow add-ons
- About related programs and services
- The Interface
- Customizing the Workspace
- PReS Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- PlanetPress Design document properties
- Using the Clipboard and Drag & Drop
- 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...
- Delete objects and groups from the Configuration Components pane
- Other 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 1 plugin preferences
- HTTP Server Input 2 plugin preferences
- LPD Input plugin preferences
- 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
- Zoom in or out within Process Area
- Adding Branches
- Replacing tasks, conditions or branches
- Removing tasks or branches
- Task Properties dialog
- Cutting, copying and pasting tasks and branches
- Moving a task or branch using drag-and-drop
- Disabling tasks and branches
- Resize rows and columns of the Process Area
- Selecting a resource file in task properties
- Highlight a task or branch
- Undo a command
- Redo a command
- The Quick Access Toolbar
- The PReS Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgments
l
Barcode_1_Left: Metadata field providing the distance (in pixels) from the left of the page
to the left side part of the first barcode.
l
Barcode_1_Right: Metadata field providing the distance (in pixels) from the left of the
page to the right side part of the first barcode.
Accessing a barcode value from the Workflow tool
One method to access a barcode value from the Workflow configuration tool is to use a
VBScript with the Open Script task, using the Watch.ExpandString command with a Metadata
command as its input parameter, in between double quotes. For example, the following script
line gives the value of the first BarcodeValue Metadata field of the first datapage:
watch.expandstring("GetMeta(BarcodeValue[0],0,Job.Group[0].Document[0].Datapage[0])")
Another method is to use a Set Job Infos and Variables task to copy a Metadata field into a
Workflow variable.
Limitations
l
Some barcodes created with PlanetPress 5 could not be read by the Barcode Scan task,
so please use PlanetPress version 6 or 7 to create barcoded documents.
l When using a secondary input, a known issue of the Workflow Tool can cause some
unexpected behavior, like having the same Metadata file reused instead of a new one
being created for each data file captured. To work around this issue, simply add a
Rename action task to set a unique file name (Ex. %u) to each new file before the
Barcode Scan task, after each secondary input.
Change Emulation
Change Emulation action tasks are used to tell the tasks that follow them to use a different
emulation to format the data they receive (see: "About data emulation" on page52). These
tasks do not perform any operation as such on the data, but rather they modify the way
subsequent tasks process the data they receive.
Change Emulation action tasks are typically used when a secondary input task brings new
data that is not structured like the initial data into the process. By default, every task included in
a process uses the emulation associated with the sample data file to structure the data before
processing it. Any task that must use a different emulation must be preceded by a Change
Page 264