Configuring a layout with advanced mobile features

Be ready for future developments in Pega Mobile, enhance navigation within your mobile app, and help users multitask by selecting and configuring a Mobile - Slide Up layout.

By default, when you build a mobile app that is based on the Pega Mobile Client, the app uses a layout with a navigation rule that defines the functionality of the bottom bar and can use multiple webviews that display different screens of the application. A mobile app with a bottom bar is easier to navigate and can be configured for work on multiple cases at the same time. The bottom bar provides instant navigation between application screens, which you can use to switch between multiple open cases without reloading the content or losing unsaved changes.

You can also instantly deploy an existing Pega Mobile Client 7-based mobile app that you have imported, for example, from a previous version of Pega Platform. For more information, see Configuring a layout for the reuse of a web portal.

Before you begin: Open the mobile channel configuration page.
  1. On the Layout tab, in the Layout section, in the Application layout area, select Mobile - Slide Up.
  2. Hover over the Mobile - Slide Up tile, and then click Configure.
  3. Select a navigation rule, and then click OK.
  4. Optional: To modify an existing navigation rule or create a new rule, click the Open icon.
    For more information, see Configuring the bottom bar.
    Note: If you created a new navigation rule, you must save, close, and reopen your mobile channel to be able to select the new navigation rule.
  5. In the Bottom menu style area, select the style of the bottom bar.
  6. Optional: To configure additional options for the bottom bar, in the Advanced layout settings section, select the settings that you want to enable.
    For example: You can specify whether users should be able to refresh the screen with a swipe down gesture or hide the top and bottom bar.
    Note: If you clear the Use iOS/Android native bottom menu check box, your mobile app will run in a single webview that does not support native navigation features. For example, you might want to use a single webview if the native features do not work in certain conditions or on specific devices.
  7. Click Save.