7.3

As with any task that can refer to network resources, it is important to understand the considerations involved with
paths and permissions of these resources. Please refer to the "Network Considerations" (page 16) page in the
Advanced Configuration and Options chapter (Reference Guide, in English only).
There are some important things to consider when using the External Program Action Task:
l The executable file must accept so-called "command-line options" and be able to run without any sort of user inter-
action. Only certain programs are able to do this and may refer to it as "command-line"or "automation"features.
l The process will always wait for the executable file to finish before it continues to the next task, and does not have any
timeout setting. This mean that if your program fails to exit for any reason, your process will hang.
External Program action task properties are as follows:
General tab
l Program group
l Executable file: Enter the name and path of an executable file (exe or com extension), batch file (bat exten-
sion), or command script (cmd extension) that can run in command mode. Note that the program will be run
without user interaction. Although it may display progress information, it is 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 param-
eter 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 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" (page 54).
©2010 Objectif Lune Inc - 130 -