Manage hierarchies

Define your own navigation options for ARIS. You can use hierarchies to control how ARIS users can quickly navigate to relevant information. These hierarchies map the relationships between superior and subordinate item types.

Create navigation hierarchy #ssc

You can define your own hierarchies for each user-defined modification set.

Prerequisite

  • You have created your own modification set.

  • You have the Portal administrator function privilege.

  • If you want to use a root element, the GUID or the item ID of the root element must be available on the clipboard.

Procedure

  1. Click Application launcher Application launcher > Administration Administration. The Administration opens with the Configuration Configuration view.

  2. Click Publication settings > Manage configuration sets. All available configuration and modification sets are displayed. You can edit the modification sets.

  3. Click Edit Edit in the row of the relevant modification set.

  4. Click Hierarchies on the Define modification set page.

    All hierarchies defined in this modification set for navigation are displayed. By default, these are the hierarchies from the template from which the user-defined modification set was derived, for example, Processes, Organizations, IT systems, or Groups. You can activate or deactivate these hierarchies marked with system, or change the order in which they are displayed in ARIS.

    Unused hierarchies are shown in strikethrough formatting and are not displayed in the portal.

  5. Click Create. The corresponding dialog opens.

  6. Specify the name for the hierarchy to be displayed in the portal in all languages. This name is shown in the portal as another navigation option. If the name is not specified in a language, it is displayed in English in the portal.

  7. Click Next. The Create hierarchy – Specify hierarchy structure page opens.

  8. Click Select item. All items that are defined in the modification set are displayed.

  9. Select the first item. The item is inserted.

  10. Move the mouse pointer over the item and click Add Add.

  11. Click Select item/property and select an entry. The second item must be of the same type as the first item. If it is not, a hierarchy cannot be created. The selected property or the item is made subordinate without space. The name of the property of the subordinate item is shown in parentheses.

  12. Add further items in the same manner. The hierarchy is symbolized by indents.

  13. Click Finish if you do not want to insert a root element. Otherwise, click Next to insert a root element.

    1. Click Add. The Specify root element dialog opens.

    2. Paste the GUID or item ID from the clipboard.

    3. Click OK. The GUID of the item is displayed in the list.

    4. Click Finish.

  14. Activate the hierarchy.

The navigation is available to users in the portal. To test the changed modification set, activate it.

Edit navigation hierarchy #ssc

Use hierarchies to define the navigation in Published content. These hierarchies map the relationships between superior and subordinate items.

You can define your own hierarchies for each user-defined modification set.

Prerequisite

  • You have created your own modification set.

  • You have the Portal administrator function privilege.

Procedure

  1. Click Application launcher Application launcher > Administration Administration. The Administration opens with the Configuration Configuration view.

  2. Click Publication settings > Manage configuration sets. All available configuration and modification sets are displayed. You can edit the modification sets.

  3. Click Edit Edit in the row of the relevant modification set.

  4. Click Hierarchies on the Define modification set page.

    All hierarchies defined in this modification set for navigation are displayed. By default, these are the hierarchies from the template from which the user-defined modification set was derived, for example, Processes, Organizations, IT systems, or Groups. You can activate or deactivate these hierarchies marked with system, or change the order in which they are displayed in ARIS.

    Unused hierarchies are shown in strikethrough formatting and are not displayed in ARIS.

  5. To edit a hierarchy, move the mouse pointer over the row for a deactivated hierarchy and click Edit Edit.

  6. Change the hierarchy.

  7. Click Finish.

The changed navigation is available to users in Published content. To test the changed modification set, activate it.

Enable navigation hierarchy #ssc

Use hierarchies to define the navigation in Published content. These hierarchies map the relationships between superior and subordinate items.

You can define your own hierarchies for each user-defined modification set.

Prerequisite

  • You have created your own modification set.

  • You have the Portal administrator function privilege.

Procedure

  1. Click Application launcher Application launcher > Administration Administration. The Administration opens with the Configuration Configuration view.

  2. Click Publication settings > Manage configuration sets. All available configuration and modification sets are displayed. You can edit the modification sets.

  3. Click Edit Edit in the row of the relevant modification set.

  4. Click Hierarchies on the Define modification set page.

    All hierarchies defined in this modification set for navigation are displayed. By default, these are the hierarchies from the template from which the user-defined modification set was derived, for example, Processes, Organizations, IT systems, or Groups. You can activate or deactivate these hierarchies marked with system, or change the order in which they are displayed in ARIS.

    Unused hierarchies are shown in strikethrough formatting and are not displayed in ARIS.

  5. To display a hierarchy, move the mouse pointer over the row for a deactivated hierarchy and click Activate Enable.

    The Groups hierarchy from the classic configuration set cannot be combined with any other hierarchy. If the Groups hierarchy is activated, all other hierarchies are automatically deactivated. If you activate another hierarchy, the Groups hierarchy is automatically hidden.

The changed navigation is available to users in Published content. To test the changed modification set, activate it.

Disable navigation hierarchy #ssc

Use hierarchies to define the navigation in Published content. These hierarchies map the relationships between superior and subordinate items.

You can define your own hierarchies for each user-defined modification set.

Prerequisite

  • You have created your own modification set.

  • You have the Portal administrator function privilege.

Procedure

  1. Click Application launcher Application launcher > Administration Administration. The Administration opens with the Configuration Configuration view.

  2. Click Publication settings > Manage configuration sets. All available configuration and modification sets are displayed. You can edit the modification sets.

  3. Click Edit Edit in the row of the relevant modification set.

  4. Click Hierarchies on the Define modification set page.

    All hierarchies defined in this modification set for navigation are displayed. By default, these are the hierarchies from the template from which the user-defined modification set was derived, for example, Processes, Organizations, IT systems, or Groups. You can activate or deactivate these hierarchies marked with system, or change the order in which they are displayed in ARIS.

    Unused hierarchies are shown in strikethrough formatting and are not displayed in ARIS.

  5. To disable a hierarchy, move the mouse pointer over the row for an activated hierarchy and click Remove Disable.

The navigation hierarchy is disabled.

For ARIS to be displayed with this modification set, you need to select the new modification set for display.

Delete navigation hierarchy #ssc

Use hierarchies to define the navigation in Published content. These hierarchies map the relationships between superior and subordinate items.

You can define your own hierarchies for each user-defined modification set.

Prerequisite

  • You have created your own modification set.

  • You have the Portal administrator function privilege.

Procedure

  1. Click Application launcher Application launcher > Administration Administration. The Administration opens with the Configuration Configuration view.

  2. Click Publication settings > Manage configuration sets. All available configuration and modification sets are displayed. You can edit the modification sets.

  3. Click Edit Edit in the row of the relevant modification set.

  4. Click Hierarchies on the Define modification set page.

    All hierarchies defined in this modification set for navigation are displayed. By default, these are the hierarchies from the template from which the user-defined modification set was derived, for example, Processes, Organizations, IT systems, or Groups. You can activate or deactivate these hierarchies marked with system, or change the order in which they are displayed in ARIS.

    Unused hierarchies are shown in strikethrough formatting and are not displayed in <_connectl.

  5. To delete a hierarchy, move the mouse pointer over the row for a deactivated hierarchy and click Delete Delete.

The navigation hierarchy is deleted.

For ARIS to be displayed with this modification set, you need to select the new modification set for display.

What does the navigation hierarchy define? #ssc

Using the navigation hierarchy, you define the navigation options for Published content. The example shows the configuration of the hierarchy for a group.

The second item must be of the same type as the first item. If it is not, a hierarchy cannot be created. Items of the same type are arranged without space.

Example

Subgroups and processes are configured for the group:

Configuration of a hierarchy

The result looks like this in Published content:

Configuration of a hierarchy - Result

What to remember regarding hierarchies? #ssc

Hierarchies define the way in which Published content users receive relevant information. Hierarchies that are based on the default template have only one level.

'default' hierarchy

Hierarchies that are based on the classic template have multiple levels, and you can expand and collapse groups.

'classic' hierarchy

From a technical perspective, a hierarchy always has a tree structure and is level-based. A level can be made up of models, objects, or groups. It may contain a superior item and multiple subordinate items. In contrast, a level can have multiple subordinate items.

You can use multiple hierarchy definitions in a hierarchy configuration. For example, you can specify the following hierarchy definitions in a configuration:

Navigation in process models (value-added chain diagrams, EPCs, and function allocation diagrams), navigation in the organization (organizational charts, organizational units, roles, and groups), and navigation in the IT systems within an organization.

Hierarchy root element #ssc

A root element is the model or object that is used as the top-level element in the hierarchy you have defined. This element is displayed when you open the hierarchy in the portal.

If you want to use a specific item from an ARIS database as the top-level hierarchy element, for example, a specific model or object, this must be defined as the root element. You require the GUID, which you can copy from the Properties dialog for the model or object in ARIS Architect, for example.