Prerequisite Setup

Before you can follow the step-by-step instructions in Preparing Your Views For Adding Navigation Controls, Building Application Navigation Files For Each Role, and Building the Navigation Controls for the Application Views, the following is required:

Define the roles in the application server that you want to use.

For example, if the application runs on Apache Tomcat server, define roles on the Tomcat server by adding the roles to the tomcat-users.xml file. For the sample, add two roles named “admin” and “tomcat”.

Create a Web Application Project in Designer using the Starter Web Application template.

Add two or more Web Application Views to the project.

You might add views that:

All users can access

Only users in a specific role can access

For example, in the sample that illustrates this use case, the application contains the following views:

 

View	Description
Default view	This is the home page of the application. It is the initial view for all users when they access the application. However, the navigation options in this view are different based on the logged in user. Users in the admin role can view screens for both administrators and users. Users in the tomcat role (general users) can view only screens for users. The step-by-step instructions will describe how to set up application so it displays different navigation based on the logged in user’s role.
userNav view userNav1 view	Two user views, which the application displays for all users. If the logged in user is not a member of the admin role, these are the only views the user can access.
adminNav view adminNav1 view	Two administrator views, which the application displays only for users in the admin role.

Related Topics 

Role-Based Navigation

Preparing Your Views For Adding Navigation Controls

Building Application Navigation Files For Each Role

Building the Navigation Controls for the Application Views

Viewing the Live Sample