Navigation Settings

In addition to the web application framework, the Business Process Center provides further core functions for designing, controlling, and monitoring your applications. One of the central functions is the management of application areas, page structures, and other navigation settings, such as the assignment of visibility permissions.

Function Description

The structure of the application can be configured via navigation settings. There, you can create application areas and their associated modules and links to external pages, which will be displayed in the navigation bar according to your settings.

Overview

Navigating to Navigation Settings

To navigate to the navigation settings, first select the “Core Services” tab in the settings panel, then “Navigation Settings”:

Navigation Settings

The most important components of the navigation settings:

Overview of the Components
  1. Application Area Selection: The list of application areas is displayed here when you hover over or click on it (only if the application contains at least two areas)

  2. Navigation Bar: The configured navigation elements in the current area are displayed here.

  3. Navigation Settings Panel: Overview of the navigation settings for application areas and navigation elements.

  4. Content Panel: Overview of the settings for a navigation element.

Creating an Application Area

Create Application Area
  1. Click “Application Area”
    The new application area is created, and the corresponding navigation element is displayed in the overview.

  2. Configuring the Navigation Element

Creating a Navigation Element

  1. Click on “Menu Element”
    The new navigation element is displayed in the overview

  2. Configuring the navigation element

A navigation element can be moved to different levels using drag & drop

Configuration options

Parameter Type Description

ID

Text

ID of a navigation element. This ID is usually assigned by the application. However, the ID can also be edited manually.

Duplicate IDs are not allowed.

Text

Text, Language Key

Label of a navigation element that is displayed in the navigation bar.

Multilingual support is available. To enable this, you can use a “Language Key” from the Language Key list.

Tooltip

Text, Language Key

Quick information about a navigation element. It is displayed when you move the mouse over a navigation element in the navigation bar.

Multilingual support is available. You can use a “Language Key” for this, which is included in the Language Key list.

Icon

Icon Picker

Icon for a navigation element. This icon is visible in the navigation bar alongside the name of the navigation element

Type

Drop-down list

Type of a navigation element.
There are three options: Module, URL, or Placeholder.

  • Module: The navigation element is linked to a module

  • URL: The navigation element is linked to a URL

  • Placeholder: See Spacer

Module

Module drop-down list

Module to which the navigation element is linked.
Only visible if “Module” is selected as the type

URL

Text

URL to which the navigation element is linked.
Only visible if “URL” is selected as the type. The URL is validated.

Target

_blank, _self. More information:

Specifies where the new page will open.
Only visible if “URL” is selected as the type.

Organization/Roles/Permissions

Drop-down list

Specifies which users are allowed to view the navigation element

ViewMode

Drop-down list: Tabbed, Vertical, Menu.
See View Mode

Display mode for the child elements of a navigation element.
Only visible if the element contains child elements.

Spacer

There is a maximum of one spacer per level. Depending on the level’s viewMode, the following should happen:

  • tabbed
    All elements after the spacer are created as right-aligned tabs (please check if this is even possible; if not, then don’t do it)

  • menu
    An Ext.menu.Separator is inserted*here*

  • vertical
    All elements after the spacer are arranged at the bottom (technically, you just add an invisible element with “flex: 1”)

View Mode

  • tabbed: The child elements are displayed in tabs

    Arrangement in tabs
  • vertical: The child elements are displayed vertically in the navigation bar

    Vertical arrangement
  • menu: The child elements are displayed in the menu

    Menu arrangement

Drag & Drop

In the navigation settings, elements can be moved via drag & drop to interactively adjust the structure, even after the navigation was originally created. Depending on the element type, different rules apply regarding where it can be placed.

General Behavior

Each navigation element has a specific type (e.g., application area, module, URL, placeholder, folder), which determines where that element may be located within the navigation structure. When moving an element, the user interface visually indicates whether a drop is permitted.

Application Areas

  • Application areas may only be located at the root level (top level of the navigation).

  • They can be or reordered —for example, before or after other application areas.

  • Dropping at deeper levels (e.g., within a folder or module) is not permitted.

Modules, URLs, placeholders, and folders

  • These types may not be placed at the root level

  • They must be be located under a parent element (e.g., application area or folder).

  • The interface prevents direct placement at the root level.

Note

The interface automatically prevents invalid moves. As soon as a drag-and-drop operation is not permitted, the drop indicator is deactivated accordingly.

JSON Configuration in Core Services

There is a separate configuration for the view and navigation structure with the key viewConfiguration. The configuration of the individual menu entries is injected directly into the ExtJS object. Therefore, all attributes listed under "configs" in the API documentation are supported.

It is not recommended to modify the JSON directly. Configuration should be performed using the interface described above.

This configuration is used to generate the navigation structure and determine which modules are linked to the navigation elements. The configuration is structured as follows:

Setting Data Type Description

defaultView

Number

View to be displayed initially. References a viewID.

views

Array

A list of view objects.

viewItemId

Number

ID of the view element. Is ignored if it is located under views.

viewItemId must be globally unique.

text

Text

Text of the menu entry

tooltip

Text

Tooltip content

targetModule

Text

Name of the module instance that is displayed after clicking the navigation element.

iconCls

Text

CSS classes for the icon

...

...

Any additional attributes can be added. These are passed directly to the ExtJS object. Therefore, all menu item attributes(see ExtJS API) can be used.

items

Array

List of child elements.
The child elements are also structured as described in this table.

right

Text / Array

Name of a user right.
If the element is specified, the system checks whether the user has this right. If not, the element is ignored and considered nonexistent.

role

Text / Array

Name of a user role.
If this element is specified, the system checks whether the user has this role. If not, the element is ignored and considered nonexistent.

Example:
"role":["role1","role2"]

organization

Text

Name of an organization.
If this element is specified, the system checks whether the user belongs to this organization. If this is not the case, the element is ignored and considered nonexistent.


Keywords: