Configure the mobile application navigator Define which application menus and modules are available on the mobile application navigator. About this taskYou cannot hide the application navigator from users, however you can control the contents based on role. Use the Roles field for both the application menu and the modules as listed in the following tables to configure the application navigator specifically by role. Procedure On a desktop browser, navigate to System Mobile UI > Navigator Apps. Click New. Fill in the fields, as appropriate. Field Description Name Enter a name for the application menu. Order Enter a number to specify the order of the menu. For example, an entry of 100 would place this application menu before one with an Order entry of 200. Roles Click the lock icon to select the roles for this application menu. Only users with the designated roles can access the modules under this application menu. Active Select the check box to activate this application menu. Save the application menu. Note: Until you add at least one module, the new application menu does not appear on the mobile application navigator. Under Modules, click New. Fill in the fields, as appropriate. Field Description Name Enter a name for the module. Order Enter a number to specify the order of the module within the application menu. For example, an entry of 100 would place this module before one with an Order entry of 200. Application menu Displays the application menu from which you accessed this screen. Select a different application menu, if appropriate. Table Select the table for this module. Updated Displays the date and time when the module record is updated. Roles Click the lock icon and select the roles for this module. Only users with the designated roles can access this module. Active Select the check box to activate this module. Only active modules appear in the application menu. Filter Create a filter for identifying which fields this module uses from the selected Table. Path Enter a custom URL for the module in this format: <type_of_link>/table/parameters. type_of_link: determines what kind of page opens, for example, form, list, or view. table: Refers to the table being referenced. For example, incident. parameters: Any additional information you want to use to direct the user a specific URL. For example, you can include a query as part of the URL to direct users to a specific filtered list. You can also use the URL format, $__.do. Path Relative To Root Allows mobile navigator modules that link to desktop pages. Select this check box to use mobile URL in the Path field, such as $sp.do, $chat.do, or $vtb.do. When the Path Relative To Root is cleared, the path is considered a mobile specific path and is relative to $m.do.For example, a path like /form/incident/-1 would be a mobile specific path and would be considered relative to $m.do. This would ultimately result in navigating to a path of $m.do#/form/incident/-1.Use mobile specific paths when possible and only use Path Relative To Root when there is not a mobile specific path for the desired resource. Note: If you are creating a module for a map page, see the procedure specific to map pages. Save the module you just added.