Navigation Pages are a powerful tool that can be used to create complex navigation structures in applications. They can be used to display both static (images, text content, static lists) and dynamic content, and they can be directly added to the navigation hierarchy.
The underlying node type for a Navigation Page is List, which means that it can contain other Pages or Lists, as well as Screen Controls. This makes it a versatile and flexible tool that can be used to create a wide variety of navigation structures.
In addition to this, Navigation Pages also support the use of Lists, which are a powerful way to display dynamic content. Lists can be used to display data from a variety of sources, including entities, lists, and custom objects. They can also be customised to meet the specific needs of your application.
Here are some examples of how Navigation Pages can be used:
To create a hierarchical navigation structure with multiple levels of pages.
To create a navigation structure that is tailored to the specific needs of a particular application.
To display dynamic content using Lists.
Name This is the name you designated to your page during creation.
Title This property allows you to customise the title of your navigation page.
Icon This property allows you to select an icon which is used to prefix the Title.
For main menu items the Icon field is required otherwise broken icon images will be rendered before your menu items.
The screenshot below shows two menu items displayed as part of the Main Menu on a web application built using the ComUnity Development Toolkit. During navigation configuration the Icon for the Admin link was not selected during development, so it is displayed as a broken image before the link name, whereas for the Notifications menu item, a bell icon was selected.
Role Name This property allows you to specify the user role that has access to the navigation page.
If a Role Name is not specified a navigational component is visible to all authenticated users conversely when a Role Name is specified for a navigational component, that component is then conditionally displayed in the client. Authenticated users on the applications will see only the component which they have permission rights for, otherwise if they do not have the correct access rights the navigational elements will be hidden from their view. To learn more about how to configure user roles and permissions view Authorisation.
Image URL Coming Soon...
Once you have set the properties of your Navigation Page, you can start building your page content using screen controls. You can find a comprehensive guide on how to do this in the Screen Controls section. In the next section, we will discuss how to implement features specific to the Navigation Page, which can all be done using screen controls strategically.
