...
The Triggers tab consists of five separate sub-panels. These are as follows:
...
The triggers of and triggers by lists form the central part core of the Triggers panel so we will explain their usage in detail.
| Info | ||
|---|---|---|
| ||
The graphical representation of the nodes and attributes appearing in the trigger lists are the same as in the tree view. The status states of these items is are continuously updated and they come with a large set of actions in their context menu. |
| Info | ||
|---|---|---|
| ||
Double click on a node/attribute in trigger list or run action 'Lookup in tree' from the context menu to broadcast this selection broadcast to the other views, e.g. to make it selected in the tree view. The the dependency details list contains textual information with hyperlinks: when you click on a path the selection will be broadcast to the other views. |
...
- directly triggers a parent of the currently-selected node
- directly triggers a child of the currently-selected node and it is not an the ancestor of the currently-selected nodeit
To find out more about a dependent trigger through dependency we need to click on it and check its dependency details list. For example if we click on limit /eda/limits:mars we get these dependency details will be listed:
Here e.g. the first line tells us that /eda/limits:mars triggers the node /eda/lag/12/archive/ansfc, which is the child of the currently selected node (/eda/lag/12/archive).
...
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 triggered 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:
...
This tells us that /eda/lag/12, which is the parent of the currently selected node (/eda/lag/12/archive), directly triggers /eda/lag/logfiles. The trigger expression of /eda/lag/logfiles verifies this fact:
...