8.4

better if the application has no user interface.
l Parameters: Enter parameters that will be passed to the external program when it is launched.
Each parameter should be enclosed in quotation marks and separated by a space
("Param1""Param2" "Param3") except command line options (such as -f, /n). The exact
parameters accepted are unique to the executable and defined in its documentation if it exists.
l Start in: Enter the folder in which the external program is to run. This is important, for example, if
the program is to generate files that are to be picked up in a specific location for further
processing, or if it requires resources that are located in a specific folder. Leave blank to run the
program in the folder of the executable file.
l Run minimized: Select to prevent a window (a DOS box, for instance) from being displayed on
the desktop. When selected, the program runs in a background window.
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 triggered 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 triggered.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on " Task Properties Dialog" on page 587.
By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and
the task just under it (not within a branch)will be given control of the job file without any modification. Any
initial input task that generates an error will stop the process from running as a whole, and output tasks will