2022.1

l
Message: Enabled only when the Log Message option is checked. Enter a message that
will be logged in the PReS Workflow log file. You can use any variables available in
PReS Workflow to customize the message.
l
Store the message in variable: Select in which jobinfo, local or global variable you
want to store the message content.
l
ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the
ID is not visible in the PReS 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.
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 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 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
indicating 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 simultaneously advising the person that sent the job that it failed.
Page 100