8.6

l
ID:Enter an error ID. This IDwill be visible in the Windows Event Viewer. However, the
IDis not visible in the PlanetPress Workflow log file.
l
Store the IDin variable:Select in which jobinfo, local or global variable you want to
store the error ID.
l Reset to defaults:Resets all options in this tab to their default values.
When storing the message or ID, if they are stored in a jobinfo they will be available in any
error handling process where errors are being forwarded. If your process continues after the
error, the contents of the variables selected in this window will be available to the rest of your
process, or as long as they are not overwritten.
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 PlanetPress 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 OKbutton, and are displayed in the Task Comments Pane.
Output Tasks
Output tasks are exits from PlanetPress 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 PlanetPress 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 PlanetPress 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 PlanetPress Image output task, PlanetPress Workflow considers its job done once it
has sent its request to PlanetPress Image, not once PlanetPress Image has finished
generating the actual image file.
Page 567