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 related to the currently-selected node.
The Triggers tab consists of five 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)
...
| Info | ||
|---|---|---|
| ||
The graphical representation of the nodes and attributes appearing in the trigger lists are the same as in the tree view. The states of these items are continuously 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 to the other views, e.g. to make it selected in the tree view. The dependency details list contains textual information with hyperlinks: when you click on a path the selection will be broadcast to the other views. |
...
To find out more about a 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:
...
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:
...