7.4

l Instead of skipping through each task, use the Run from here or Step from here options, either from the Debug
tab or by right-clicking on the task where you want to start the process.
Once you have created and fully debugged all your processes, you will be ready to send it to the PlanetPress Workflow Tools
service. See Saving and Sending a Configuration.
About Error Handling
When your process is running, or during debugging, it may happen that the task that is currently running causes an error, and
the task fails. For example, when trying to save to a folder that does not exist, or printing to a printer that cannot be found.
When such an error occurs, in most cases you would want to be aware of it and to take certain actions in order to correct or
report the error. This is where our error handling features come in handy.
Most of the tasks, branches and conditions included in your process can have their own error handling behavior, with the
exception of comments, the Error Input Bin input task, and older legacy tasks from previous versions of PlanetPress Suite that
did not have error handling.
By default, when an error occurs, the task is skipped and the unmodified job file is passed on to the next task. You can over-
write this behavior by changing the options of the On Error tab of the task.
Using the On Error tab
Whenever an error is triggered either during debugging or when a process runs in production, the settings specified in the On
Error tab of the task that generated the error will be used to determine a course of action.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are 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 cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Creating and Using Error Processes
An Error Process is a special type of process that never runs on its own, and cannot be called using the GoSub or Send to Proc-
ess tasks. It can only be used in the On Error tab of a task in your process, and will be triggered if the Send to Process option is
checked in that tab and an error process is selected in the drop-down list.
To create an error process, simply replace the initial input task by the InputErrorBin Input Task, and that process auto-
matically becomes able to handle error jobs sent to it. It is up to you, however, to decide how that error job will be handled.
Debugging and Error Handling