A Command Step is a step in which an operating-system level command or script (shell, batch, perl, etc) is executed. The name of the command can be entered explicitly or set as a string variable, and parameters can be passed in the same manner. Output from the command can also be placed back into a string variable.
A Command Step includes the following attributes:
Name of step
Description
Command (May be explicit or variable-driven)
Arguments (May be explicit or variable-driven)
Output Variable
NOTE: The command (or a batch file or script that refers to the command) must be stored in the %ESEC_HOME%\config\exec or $ESEC_HOME/config/exec directory on the iTRAC workflow server, usually the same machine where the Data Access Server (DAS) is installed. Symbolic links are not supported
The command output may also used to set a variable to the appropriate values. Command steps must use String variable types.
The value of the variable can be used as part of a Conditional transition to determine the path the workflow follows. It can also be used later as part of a Decision step to determine the workflow path.
For example, a command step may return a value of 0 for failure and 1 for success. This output can be assigned to a variable, and then a Conditional transition or a Decision step can use this value to determine which workflow path to take.
The command and its arguments can each be entered explicitly by the person designing the workflow or be set as a string variable. If either one is set as a string variable, there must be a previous step in the Template where the variable is set to a string value.
From a Command Step, you can set Conditional, Unconditional, Timeout, or Alert, or Error transitions. It is a good practice to always include an Error transition so that errors can be immediately escalated to someone.