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
Prerequisites
Before you can start debugging, these are the prerequisites.
l There must not be any "Unknown tasks" on page510 in the process.
l A sample data file must be selected; see "Choosing a sample data file" on page63.
Note
The sample job file should generally be the exact same format as the data that the
process will receive when PReS Workflow is processing the job at run-time.
About the Debug mode
When debugging your process, it is important to keep in mind that:
l
The initial Input task is never executed. The sample data file is used instead of the initial
run. This is to prevent "live" data from being retrieved by the initial input task while
debugging is being done. If, however, the initial task is critical to the process, it can be
executed by copying the initial input task and pasting it as a secondary input task (the first
Action task to actually run in the process). Do not forget, however, to remove this
duplicate task before saving the configuration!
l If any task makes an operation on the system (for example, capturing files, sending data,
printing, etc), it is actually executed, not simulated.
l
Any task is executed with the permissions of the user that is currently running the PReS
Workflow Configuration tool. When running in Service mode, the user configured in the
Configure Services dialog is used instead. If the credentials are different, a job that runs
in debug mode may fail at run-time if the permissions are not available to the Service.
Please see "Workflow Services" on page628 for more details.
Running in Debug mode
Debugging can be run in different ways:
l
From the Debug tab, click on Run. This executes the complete process, step by step,
until it is completed.
l
From the Debug tab, click on Step. This executes only the first task in the process and
waits for further action. While stepping through a process (using Step, not Run),
Page 89