2022.2

When storing the message or ID, if they are stored in a jobinfo they will be available in any error hand-
ling 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.
All error codes are listed in the knowledge base of PReS Workflow. 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 Workflow 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.
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 Process 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 selec-
ted in the drop-down list.
To create an Error process, simply replace the initial input task by the InputErrorBin Input task, and
that process automatically becomes able to handle error jobs sent to it. It is up to you, however, to
decide how that error job will be handled.
For example, you could place the job file in a specific folder, then send an email to a supervisor indic-
ating that a job has failed. Or you could update a database with an error status so that it appears on a
customer's online order. You could also zip the order up and send it to an administrator, while sim-
ultaneously advising the person that sent the job that it failed.
You can have as many error processes as you can normal processes - that is, you are limited to 512
processes, subprocesses, startup processes and error processes combined.
Information available in an Error process
The following information is available from within your Error process when it is triggered.
l
A series of variables containing information about the error, the task that triggered it and the pro-
cess that contained it (see below). These are "System variables" on page240.
l
"Job Info variables" on page239 (%1 to %9).
l
The data file as it was before starting the task.
l
Global variables (which are, of course, available anywhere).
Note: Local variables in the process are not sent to error processes, even if the error process
has a variable of the same name.
Page 84