When you create a new table in ServiceNow,best practices for the navigation paneensure that the table is properlyorganized, accessible, and followsrole-based visibility standards.
Modulesallow users tonavigate directly to the tablefrom the left navigation pane.
Settingrole-based accessensures that only authorized users can view or use the table.
Navigate toSystem Definition > Modules, and definewho can accessthe module usingroles.
This ensuresconsistencyin navigation and makes it easier for users to locate the table.
Example:If you create a table"Project Tasks", theApplication Menushould also be named"Project Tasks".
This followsServiceNow UI best practicesfor organization.
1. Specify which Roles can see the Module (Correct - C)2. Create an Application Menu with the Same Name as the Table Label (Correct - E)
A. Set the filter condition on the Application Menu →Incorrect
Application Menus do not requirefilter conditions; they are forgrouping related modulesunder a category.
B. Set the font style on both the Application Menu and the Module →Incorrect
Font stylesare not customizable in the navigation pane.
D. Specify which Roles can see the Application Menu →Incorrect
TheApplication Menuitself is usually visible to all users unless restricted bymodule-level roles.
The best practice is torestrict roles at the module level(Correct Answer: C).
F. Create a Module with the Plural of the Table Label →Incorrect
While it isa common practice, it isnot a strict best practice.
Example: If your table is"Incident", the module is typically named"Incidents", but it’s not a mandatory rule.
Why Other Options Are Incorrect?
Managing Application Menus and Modules
Creating Tables and Modules
Official ServiceNow Documentation Reference: