8.8

Table Of Contents
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 text area (Task comments)that lets
you write comments about the task. These comments are saved when the dialog is closed with
the OKbutton, and are displayed in the Task Comments Pane.
Check the option Use as step description to display the text next to the icon of the plugin in
the Process area.
Output Tasks
Output tasks are exits from PReS Workflow processes. They can be used to send data to
specific devices, such as printers, applications, such as email software, or locations, such as
folders. A single process can include multiple branches, each one terminated by an output task,
and so a single process may generate output via a variety of output tasks.
Typically, whenever PReS Workflow sends an output task to an output device, application or
location, it considers its job finished. When it sends data to a printer, for example, it does not
wait for the document to have finished printing to consider its job done. In the same fashion, an
email output task is completed once PReS Workflow has sent its message to the email
software, not when the email has actually been sent from the software. And in the case of a
PReS Image output task, PReS Workflow considers its job done once it has sent its request to
PReS Image, not once PReS Image has finished generating the actual image file.
Other tasks available in PReS Workflow can be used to generate output, such as Digital
Action, Create VDX and PrintForm action tasks. Unlike output tasks, action tasks are only
considered completed once the output file has been generated. In the case of a Digital Action
action task, for example, PReS Workflow will consider the task completed only once the image
file has actually been created. This means that no other task from the same process can be
performed in the meantime. For more information on those tasks, refer to "Action Tasks" on
page264.
Page 615