...
- When we click on an item in either lists list the details about the dependencies will be displayed in textual format at the bottom of the interface. This part can be shown/hidden with the
button in top-right corner of the Triggers tab.
The triggers of and triggers triggered by lists form the core of the Triggers panel so we will explain their usage in detail.
...
Direct triggers are displayed with a white background. For example, in our snapshot the first four items (the generated variables /eda/main:YMD and /eda/lag:YMD, and the nodes an and fc) are direct triggers because they all appear in the selected node's trigger expression, which reads as:
...
When the dependencies are enabled (using the Dependencies button at the top-right corner of this panel) an additional set of triggers will be shown with a grey background. A node or attribute is regarded as a trigger through dependency when it
- directly triggers a parent of the currently-selected node
- directly triggers a child of the currently-selected node and it is not the an ancestor of it
To find out more about a 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:
Here e.g. In this example, 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).
...
The list on the right shows the nodes that are triggered by the currently-selected node.
A node is directly triggered when the currently-selected node appears in its trigger expression. Directly triggered nodes are displayed with a 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:
...