Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Triggers tab consist of five separate sub-panels. Theese 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 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)

...

The triggers of and triggers by lists form the central part of the Triggers panel so we will explain their usage in detail.

Info

The status of all the nodes and attributes appearing in the trigger lists are updated in the same way as in the tree or table views. Likewise a large set of actions is available from the context menu.

Info
titleBroadcast selection

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.

Triggers of the selected node

...

  • a node or attribute that appears in the selected node's trigger expression
  • a limit that the correctly currently-selected node consumes
  • a date or time attribute of the currently-selected nodesnode

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:

...

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 through dependency 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 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 The trigger expression of /eda/lag/logfiles we can see that this really the case verifies this fact:

Code Block
./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 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.

Image Removed

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.

In the extended list the Triggers through parent ... blocks show the nodes/attributes triggering each ancestor.

Image Removed

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.

Image Removed

Nodes triggered by the selected node

...

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).

...

titleHyperlinked text

...

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.

...