Table of Contents
Advertisement
Arguments (Can be explicit or variable-driven)
Output Variable
NOTE: The command must be stored in the
the iTRAC workflow server. Symbolic links are not supported
Variables
The command output can also be 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 can 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 specified explicitly by the person designing the
workflow or can 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. An Error transition should always be included so error conditions can be handled
properly.
NOTE: If the first step of a workflow fails without an error transition, the iTRAC process cannot
proceed.
6.5.6 Activity Step
An activity step is a type of automated step that can be used in a workflow template. The activity
steps are created in the Activity Manager and can consist of internal Sentinel operations or external
scripted operations. After activity steps are created, the user can select from the library of these
activities and include them into in a workflow. For more information on creating each type of
predefined activity, see
Section 6.7.5, "Creating iTRAC Activities," on page
An activity step includes the following attributes:
Name
Description
Activity Assignment
From an activity step, you can set Conditional, Unconditional, Timeout, or Alert, or Error
transitions. An Error transition should always be included so error conditions can be handled
properly.
<Install_directory>/config/exec
directory on
151.
iTRAC Workflows 135
Advertisement
Table of Contents
