7.4

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.
File Size Condition
File Size conditions test the size of the job file they receive. Note that the job file may include data selections, attachments and
documents that were added by other tasks. If a file does not exist, it's file size will be 0kb.
File Size Condition properties are as follows:
General tab
l File size is: Select whether the condition is to check if the job file is smaller (less than) or larger (more than) then the
specified value.
l Kbytes: Enter the minimum (more than) or maximum (less than) size setting in kilobytes.
l Invert condition result: Select to toggle the result of the condition (true becomes false and vice versa).
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l HTTP PDF Invoice Request
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.
Go Sub
The GoSub action task transfers the execution of the calling process to the specified subprocess. When a process encounters
a GoSub action, it halts its own execution, start the subprocess and waits for it to complete before resuming its workflow with
the next task.
Every subprocess starts with a BeginSub input task and ends with a EndSub output task, both of which have nothing to con-
figure and cannot be replaced or deleted. The simply represents entry and exit points for the subprocess.
While it is possible to place a GoSub action within a subprocess, doing so will hide the subprocess from any GoSub
action, in order to avoid circular referencing (aka an infinite loop).
General tab