...
A node is directly triggered when the currently-selected node appears in its trigger expression. Directly triggered nodes are displayed with white background. For example, in our snapshot the first item (node /eda/lag/12/clean) is directly triggered by the currently-selected node (/eda/lag/12/archive) because the former node's trigger expression reads as:
| Code Block |
|---|
fb == complete and archive == complete |
When the dependencies are enabled an additional set of triggered nodes will be shown with grey background. A node is regarded as a triggered through dependency when either a parent or a child of the currently-selected node triggers it.
To find out more about a dependently node triggered through dependency node we need to click on it and check its dependency details list. For example, if we click on node /eda/lag/logfiles these dependency details will be listed:
...