Menu entries are configured in the Menu Definitions application. Each menu entry is required to have a menu page and section defined, and optionally a menu category. Your menu entry should be placed in the same page, section, and category as related applications or reports. This ensures the correct users have access to your application or report, since security for menu entries is dependent on the location they are placed. Learn more in Menu security.
Menu entries also enable reuse of applications which have multiple versions created with application settings. Application settings can be used to change the composition of the application based on user roles. For example, in the Customer Invoices application, accounting staff use customer billing information, while account managers use payment information. Application settings open different versions of the application for each role, and each version has its own unique menu entry in the Navigation Menu. Accounting staff use the read-only Customer Invoices for Billing application, while account managers use the Customer Invoice Payment Information application. To create these unique menu entries, each application and application setting combination would need its own record in the Menu Definitions application. Learn more in Menu Definitions application.
Different configuration settings, such as application settings, field mappings, and logic blocks, determine how applications display when they are opened. When an application is opened from the menu, configuration settings are applied in the following sequence:
- Application configuration
- Field mappings
- Application settings
- Logic blocks
Menu Definitions application
Use the Menu Definitions application to create and manage menu entries. Menu entries are the options that display when you open the Navigation Menu.
Reports and applications must have a record in the Menu Definitions application to appear in the Navigation Menu. Each entry is configured with a:
- Menu Title—The name you want displayed in the Navigation Menu for the application or report. Application menu entries have naming conventions determined by their category or type. See the Menus best practices topic for more information.
- Location—The menu page, section, and category where the entry should be placed.
- Application Setting—The application setting for applications must be included in menu records. This allows for multiple versions of the same application to have their own unique menu entries based on application settings and user roles. Learn more in the Application settings topic.
Not all applications and reports need menu entries. For example, a mini app that is connected to a search action does not need its own menu entry since that application type is accessed from a search field.
Learn more in Menu entries.
Hide and disable menu entries
Hide and disable menu pages and their affiliated applications in the Disable Menu Page Utility application. This application is accessed by selecting the form action within the Menu Definitions application.
Open the application and select the Add button in the list form. Specify the menu page you want disabled. Once saved, that page and all of its affiliated applications are hidden on the Navigation Menu and can no longer be searched for.
Sort priority of menu entries
This topic reviews the sort order priority for menu entries in the Navigation Menu.
Menu entries are organized based on the following sort order:
| 1 | Menu Page |
|---|---|
| 2 | Menu Section |
| 3 | Menu Category |
| 4 | Sequence |
When multiple versions of the same application exist in the menu, such as customized, checked out, or copied applications in branch lifecycles, additional sorting criteria applies:
| 5 | nwTenantStripe—Owned entries are shown before base entries. |
|---|---|
| 6 | Translated title—In instances of the platform which have been translated to different languages. |
| 7 | Application lifecycle—Checked our or copied applications that are held in branch lifecycles. |
Menus best practices
These best practices and naming conventions ensure that menu definitions are consistently configured and applications are predictably named.
Menu records are configured in the Menu Definitions application, and result in an entry in the Navigation Menu. Users click the entries in the Navigation Menu to open applications.
When you create a menu definition, you should always associate the menu definition with an application setting, in addition to the required fields such as Page, Section, and Title. Adding an application setting to the menu record makes it easier to customize the application using the application setting, instead of the application itself. Learn more in Application settings best practices.
Mini apps, or applications that are Mini App style, should not be launched directly from the menu.
The Custom Icon field should not be delivered in production-ready menu entries. Leave this empty for customers.
Naming conventions for Menu Titles
Follow these guidelines when entering an application name in the Title field of the Menu Definitions application.
These conventions identify applications by category or type. The menu title for the application should follow the following standard:
Singular-Object-Name Categorywhere Singular-Object-Name is a noun and Category is one of the categories in the table below.
For example, Data Item Definitions.
| Category | When to use |
|---|---|
Setup | The application is used for:
For example, the Validation Setup application. This category can also be used for a composite application that includes multiple steps. For example, the Sales Setup application has module settings as well as other order settings. |
Settings | The Application Type is Module Settings.Use the Product Family or Product Module name in the menu title. For example, Payables Settings. |
| Plural Noun Only | Use for transactional applications, master data applications (which manage basic data that is needed to run an ERP system), and applications that require continuous updates, even in they are not transactional.
|
Ledger | Use for applications that list transactions supporting the general ledger. This category is primarily for Financials applications. For other applications, use Catalog. Don’t use Ledger and Inquiry together. For example, use Accounting Ledger, not Accounting Ledger Inquiry. |
Catalog | Use when the application provides a read-only list of records that can be selected from and used in another process. These records are often a subset of records from a larger application system. For example:
|
History | Use for applications that show details of previously run processes or time-based records. Do not use Log, unless referring to a well-known industry term. For example:
|
Quick Entry | Use for applications that allow an easier or more streamlined entry of a record. For every Quick Entry application, there should be another more substantial application with advanced settings or functionality. For example, User Quick Entry. |
Report or Inquiry | Use Report when the Application Type is For example, Data Transform Dependencies Report and AP Aging Report. Use Inquiry when the Application Type is For example, General Ledger Inquiry. |
Management | Use for applications that configure or make changes to objects that influence records in other applications. These require more continuous maintenance than Setup applications, and are not Module Settings applications. For example:
|
Process | Use for applications that run jobs or other background tasks that make bulk updates to other tables. For example:
|
| Where Used | Use for applications that identify where assets are used in various tables or applications. For example:
|
Utility | Use for applications that are used primarily for reference or troubleshooting, not creation. Utility applications can also allow bulk updates. For example, Application Monitoring Utility. |
Workbench | Use for applications that consolidate multiple activities in one place, or which work across multiple areas. Composite applications are a good candidate for this category. For example, Translation Workbench. |
Builder | Use for large applications that have multiple steps or components. This category is primarily used for platform applications. For example, Logic Block Builder and Workflow Builder. |
Definitions | Use for small, self-contained applications. Definition applications are generally used frequently, or for continuous development. For example Data Item Definitions. |
Integration | Use when the application is used to support integrations. The object name can be plural if the integration is to an application that falls into the Plural Noun Only category. For example, the Purchase Requisitions application has the related Purchase Requisitions Integration application. |