8.5
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.5
- System Requirements
- 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
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks
because they are related more to the system than to PReS itself. Some examples would be W3813, W3830,
W3991, W4005. These correspond to issues such as not having any space to write files, permission errors
on folders or files, etc.
Comments Tab
The Comments tab is common to all tasks. It contains a single text area (Task comments)that lets you
write comments about the task. These comments are saved when the dialog is closed with the OKbutton,
and are displayed in the Task Comments Pane.
LPD Input
LPD (Line Printer Daemon) input tasks retrieve data in the form of print files sent from remote computers
using the LPD/LPR protocol. ThePReS Workflow LPD server starts automatically when a configuration that
includes at least one active LPD Input task is started.
To prevent conflicts between competing LPD servers, you must not run any other LPD server than the PReS
Workflow LPD server on PReS Workflow workstation.
LPD tasks are configured primarily through user options (See "LPD Input Plug-In Preferences" on
page643). The only LDP information you enter in each LPD task is the queue name.
Input
This task does not poll an input, it sits there and waits for a job file to be sent through the LPRport.
Processing
When the job is received through LPR, it is saved as a job file. No further processing is done on the file.
Output
The task outputs the job file as is, with no evaluation or modification.