Determining the Page Flow
Use
After creating the pages of your BSP application, you can determine the page flow, that is the transitions between the pages. To do this, you assign a navigation request to each page transition. Assigning the pages using a navigation request provides you with a purely formal ("static") description of the navigation scheme within the BSP application. The exact point at which a page is exited is defined through the navigation object:
navigation -> next_page('<Navigation request>')
However, this is not the only way to trigger a navigation step. For example, you do not need a navigation request if you determine the page transitions by specifying the URL.
Procedure
To determine the page transitions, select the respective BSP application and enter the First Page, the Target Page and the Navigation Request manually on the Navigation tab.
Alternatively, you can use a graphical tool available on the Navigation Modeler tab. The Navigation Modeler represents the pages of the BSP application as rectangles. You can easily define the page transitions by dragging the connection lines. Select and zoom functions are available for working with a comprehensive set of pages.
The following figure illustrates the navigation scheme using a small sample bookstore. All navigation requests are shown in upper case.
The navigation graph gives you a quick overview of the navigation scheme in a BSP application.
If you use external Web development tools for designing the BSP pages, you can use a template of this design tool to help you define the navigation scheme in the Web Application Builder.