2022.2

l
Barcode scan
l
Capture Field Processor
l
All Splitters (Including the Metadata Sequencer)
l
Get Capture Document
l
Loop
l
Capture PGC Splitter
l
PrintShop Mail
Error handling variables
The error handling variables are read only and are filled by the On Error mechanism.
They can be accessed anywhere, but they only appear in the contextual menu of a task property field
when the current process is an error-handling process (that starts with the Error Bin Input task). See
also: "Variable task properties" on page245.
Variable Name
%{error.process} Name of the process where the error was triggered.
%{error.tasktype} The type of task that triggered the error
%{error.taskname} The name of the task that triggered the error
%{error.taskindex} The position of the task in the process
%{error.errormsg}
The error message, as entered in the OnError tab of the task.
This is the same message as appears in PlanetPress Workflow Log file.
%{error.errorid}
The error ID, as entered in the OnError tab of the task.
This is the same ID that appears in the Windows Event Viewer.
%{error.errorlog}
A string containing the logged error message(s) from a task. Multiple error messages are delimited by a "|" (vertical bar) char-
acter.
Local variables
Local variables are set at the level of a process and are not shared with any other process or instance
of that process. Local variables can be used anywhere where a variable is accepted by using its name,
surrounded by curly brackets and preceded by a percent sign, for example: %{myLocalVariable}.
When the process ends, the local variable forgets whatever value was given to it by the process and
goes back to its default value. Local variables are generally used to keep information that is useful for
the process itself but not to any other process or instance of the process. For example, you could store
the current order ID for the process, a name, or an email. You can have as many local variables as you
want in any given process.
Adding a local variable
To add a local variable:
Page 242