Dependencies can be created between nodes by using triggers, limits, date and time attributes.These dependencies can all , and can be shown in the tree and table views as attributes.
A more advanced way to see dependencies is to use the Triggers tab in the Info Panel. This provides detailed information about the dependencies connected related to the currently-selected node.
The Triggers Triggers tab consist consists of five separate sub-panels. These 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 this, 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 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 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 continuously updated are updated with each server sync and they come with a large set of actions in their context menu. |
| Info | ||
|---|---|---|
| ||
Double click on a node/attribute in the 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. |
...
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 an ancestor of the currently-selected nodeit
To find out more about a dependent trigger through dependency we need to can click on it and check to see 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. 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 , and is 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:
| 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 node through dependency, 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:
...