Triggers defines define a dependency for on a task or family . There can be only one trigger dependency per node, but that can be a complex boolean expression of the status of several nodes. Triggers can not be added to the suite node. A node with a trigger can only be activated when its trigger has expired. A trigger holds the node as long as the trigger’s expression evaluation returns false.
Trigger evaluation occurs when ever whenever the child command communicates with the server. i.e. whenever there is a state change in the suite definition and at least once every 60 seconds. The keywords in trigger expressions are: unknown , suspended , complete , queued , submitted , active , aborted and clear and set for event status. Triggers can also reference Node attributes like event , meter , variable , repeat and generated variables and limits. Triggers can also reference the late flag on a node. Trigger evaluation for node attributes uses integer arithmetic. See Glossary
...
There are many times where we want to add a chain of tasktasks, i,.e. where task tasks must be run sequentially one after the other. The following examples show different styles of chaining tasks which are identical:
...
| Warning |
|---|
In the examples above we use 'defs.s1.t1*' to reference a node by name. This is useful in small designs but will produce maintenance issues in large designs IF the node names are changed. |
...