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.
Process Logic Tasks
A process is like a flowchart. The data files captured by the input tasks become job files (see
"Data File and Job File" on page20) that travel down the process. Many processes include
multiple process logic tasks.
In the Process area, conditional branches appear with their associated condition, allowing you
to understand the logic of the whole process at a glance. When PlanetPress Workflow comes to
a condition, it tests the condition and sends the job file down one of the two branches based on
the test result. So every time a job file travels down the process, it is either routed down the
True or False branch.
Page 374