8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- 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
- 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, added in PReS Suite 7.5, 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.
Create PDF
The Create PDF action task allows users running PReS Workflow to create native PDF outputs without an
active PReS Image license. It very similar to the Digital Action task (See "Digital Action" on page 231) but
is more limited. It does not contain the advanced PDFoptions that are offered by the PReS Image solution,
but is useful for creating simple PDFfiles using the default quality.
Note
This feature is part of the PDFTools, which is only available in PReS Workflow.
PDFs created with the new Create PDF action task will effectively replace the current data file in any given
process using such a task.
Input
Any data file supported by PReS Workflow.
Processing
In the case of regular data files, these files will need to be merged with a PReS Connect document.
In the case of a PDFdata file, two things can happen. The PDFcan be used as a data file for a Design
document, or it can be part of a straight PDFworkflow. When this is the case, this task will rather apply the
active metadata to the PDFdata file (see "PDF Workflow" on page 145 for more information on this).