...
A more advanced way to see dependencies is to use the Triggers tab in the Info Panel. This provides a powerful place for viewing all detailed information about the dependencies connected to the currently-selected node. The
Triggers tab contains two further tabs each showing a different kind of dependency.
| Info | ||
|---|---|---|
| ||
The text in the Triggers tab contain hyperlinks: when you click on a node/attribute path the selection will be broadcast to the other views. However, please note that the trigger expression itself (see below) does not contain hyperlinks. |
Triggers of the selected node
Triggers tab consist of five separate sub-panels. Theese are as follows:
- At the top the trigger expression of the node (if available) is displayed. It can be hidden/shown with the Expression button.
- Just below the trigger expression the currently-selected node is visible.
- The area below the currently-selected node is divided into two lists showing
- the triggers of the selected node (on the left)
- the nodes triggered by the selected node (on the right)
- When we click on an item in either lists the details about the dependencies will be displayed 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 by lists form the central part of the Triggers panel so we will explain their usage in detail.
Triggers of the selected node
The list on the left shows the triggers of the currently-selected node.
A direct trigger can be
- a node or attribute that appears in the selected node's trigger expression
- a limit that the correctly selected node consumes
- a date or time attribute of the currently selected nodes
Direct triggers are displayed with 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:
| Code Block |
|---|
(/eda/main:YMD gt /eda/lag:YMD) or (/eda/main:YMD eq /eda/lag:YMD and /eda/main/12/an==complete and /eda/main/12/fc==complete) |
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 grey background. A node or attribute is regarded as a dependent trigger when it
- directly triggers a parent/ancestor of the currently selected node
- directly triggers a child/descendant of the currently selected node and it is not an ancestor of the currently-selected node
To find out more about a dependent trigger we need to click on it and check its dependency details list. For example if we click on limit /eda/limits:mars 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).
Nodes triggered by the selected node
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 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: fb == complete and archive == complete, i.e. node archive directly triggers node clean.
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. /If we check the trigger expression of /eda/lag/logfiles we can see that this really the case:
./00 == complete and ./12 == complete and /eda/main:YMD gt /eda/lag:YMD
of eda/lag/12 that is the parent of . node that node /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 first tab shows the triggers of the selected node. The top part displays the trigger expression of the node itself (if there is any). Below this block the triggers directly triggering the node are listed. This list is constructed by parsing the trigger expression of the node. The limits holding the node and the date and time attributes of the node are also listed here.
...
There are the Triggers through child ... blocks as well. These show only those node/attributes that trigger the child node but lie outside all its ancestors.
Nodes triggered by the selected node
The second tab shows the nodes that are triggered by the selected node. Collecting information for this tab requires scanning the whole tree and can take a longer time (a progress bar indicates how the scan proceeds).
By default the tab contains a block showing the nodes directly triggered by the selected node (i.e. the trigger expressions of these nodes contain the selected node).
| Info | ||
|---|---|---|
| ||
The text in the Triggers tab contain hyperlinks: when you click on a node/attribute path the selection will be broadcast to the other views. However, please note that the trigger expression itself (see below) does not contain hyperlinks. |
By toggling the Dependencies button the dependencies are scanned both upwards (through the ancestors) and downwards (through the children) in the tree and the list gets extended.
...