7.4

l Program output capture group
l Log the program output: Check to store the program output (messages generated by the execution of the
external program)inside of a job info or variable.
l Store the program output in variable: Use the drop-down to select which variable or job info to will be
used to store the program output.
l Exit Code group
l Store the exit code in job info:Use the drop-down to select which variable or job info will be used to store
the program's exit code. The exit code is a numerical value generated by the program which will indicate
whether its execution was a success or if errors were encountered.
l Verify return value: Check to enable the group and react whenever specific exit codes are returned by the
software.
l If exit code is:Use the drop-down to select how to compare to the exit code. This numerical comparison is
either equal, greater than or lower than.
l Value:The numerical exit code that will be verified.
l Return:Use the drop-down to select whether this exit code should define a success or a failure of the external
program. If "Failure"is chosen, exit codes that match the condition set will cause the On Error tab to be trig-
gered and any other exit code will be considered a success. Inversily, if Success is chosen, exit codes that match
the condition set will cause be considered a success and any other exit code will cause the On Error tab to be trig-
gered.
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.
Load External File
Load External File Action tasks are used to replace the current job file by the designated text file. Loading an external file does
not delete the original file or modify it in any way.
Input
The current data file in the process will be discarded.
Processing
The external file specified in the task's properties is loaded and replaces the current data file.
Output
The loaded file is output. Metadata is not modified in any way, neither are job infos.
Load External File action task properties are as follows:
General tab