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. 

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 Category

where Singular-Object-Name is a noun and Category is one of the categories in the table below.

For example, Data Item Definitions. 

CategoryWhen to use
Setup

The application is used for:

  • One-time, not continuous, or generally administrative activities.
  • Provisioning a new tenant. 

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.


SettingsThe 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.

  • Examples of transactional applications: Sales Orders, Journal Entries
  • Examples of master data applications: Users, Jobs
  • Examples of non transactional, continuous update applications: Message Records, Record Notes
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:

  • Customer Defined Attribute Profile Catalog
  • Role Catalog

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:

  • Login History
  • Approval Request History
  • Audit Log

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 Report Version, or the menu entry refers to an interactive report.

For example, Data Transform Dependencies Report and AP Aging Report.

Use Inquiry when the Application Type is List Only, or the application is used primarily to review records, not create them.

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:

  • Tenant Management
  • Opt-in Platform Feature Management
  • Customer Defined Attribute Management

Process

Use for applications that run jobs or other background tasks that make bulk updates to other tables.

For example:

  • Work Order Variance Process
  • Work Order Close Process
Where UsedUse for applications that identify where assets are used in various tables or applications. 
For example: 
  • Work Center Where Used
  • Metadata Object Where Used
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.