Nested condition activity properties
Use a Nested Condition stage to further branch the execution of a sequence job, depending on a condition.
Each nested condition can have one input trigger
and typically has multiple output triggers. For example, you could
use a Nested Condition stage to implement the following control sequence.
Load/init jobA
Run jobA
If ExitStatus of jobA = OK then /*tested by trigger*/
If Today = "Wednesday" then /*tested by nested condition*/
run jobW
If Today = "Saturday" then
run jobS
Else
run JobBYou specify the conditions
that determine the sequence of actions for each output triggers in
the Triggers page. For example, you might link an ExecCommand stage
to your Nested Condition stage. In the Triggers page of the Nested
Condition stage, you enter the following expression.
DayCommand.$CommandOutput = "Wednesday"This expression indicates that the ExecCommand stage runs
the DayCommand activity, which returns the value
of the $CommandOutput variable. In this case, the
value Wednesday is displayed as the command ouput.