Navigation nodes are used to navigate the model (in other words, get elements from other elements). A navigation node cannot add data to the document content on its own, but is usually combined with some production nodes.
The following table summarizes the navigation nodes available in the template editor.
Name | Context | Description |
---|---|---|
Only on an AnalystItem. |
Returns the analyst item itself one time for each property in its property table. |
|
Only on a ModelElement. |
Creates an automatic diagram in the model, ready to be generated in the document. |
|
Everywhere. |
Navigate back to an element previously processed by a parent node. |
|
Only on a ModelElement. |
Returns the documents of a given type from a model element. The document types list is computed from the project where the template is edited. Therefore, before using a module-specific type, the module must be installed in the project to make the document type available in the template. |
|
Everywhere. |
Applies a filter to its input element. If the element matches the filter condition, it is processed. Otherwise it is ignored. |
|
Everywhere. |
Applies a Jython custom code to define the navigation from its input element. |
|
Everywhere. |
Browses the model using relations defined at metamodel level. |
|
Only on a ModelElement. |
Returns the notes of a given type from a model element. The note type list is computed from the project where the template is edited. Therefore, before using a module-specific type, the module must be installed in the project to make the note type available in the template. |
|
Only on an AssociationEnd. |
From an association end, returns the opposite association end of the same association. |
|
Only on a ModelElement. |
Gathers the most common navigations available in regards with the current navigation element. It might hide several navigations on the model itself, like in getting the parent classes of a class. |
|
Everywhere. |
Sets the current element as the root of one of the models supported by Modelio (UML, requirements, and so on). Kind of a "goto" in the model. |
|
Everywhere. |
Finds all the instances of a given Metaclass in the current element’s subtree. For example it is possible to get all the packages of a UML project. |
|
Only on a ModelElement. |
Returns the tagged values of a given type from a model element. The tag type list is computed from the project where the template is edited. Therefore, before using a module-specific type, the module must be installed in the project to make the tag type available in the template. |