Scope: managed applications.

You can navigate through a specific section using the "Current section functions panel" or a navigation and actions area in the Functions menu.

Current section functions panel

We recommend that you use the current section functions panel in configurations with a few commands in every section. We recommend that you hide this panel in complex configurations with numerous commands.

Navigation and actions area in the Functions menu

Navigation and actions area shows the section functionality. Unlike the current section functions panel, you can group commands in the Functions menu.

1. Commands

1.1. We recommend that you display in sections the commands to navigate to:

· Document lists and journals

· Source document (data) lists that start business processes

· Workstations

· Special data processors similar to ordinary lists

· Reports

All the commands must solve particular tasks in a specific area.

1.2. You do not need to display secondary and subordinate objects in the command interface.

These are catalogs and information registers, which you can access from documents and other objects.

For example:

The Counterparties and Contracts catalogs are displayed in the command interface:

The "Fixed asset write-off reasons" catalog is not displayed in the command interface:

- The catalogs can be accessed from various documents but can be used independently as well. For example, to view a counterparty contact details or contract terms.

- Access to catalog items might be required. For example, to search for contracts by status or period, or to delete counterparty duplicates.

- The catalog can be accessed from the "Fixed asset write-off" document.

- The catalog contains a few number of items and they are rarely changed. Users do not need to access its items separately.

2. Command names

2.1. To avoid a scroll bar for a standard screen resolution, command names must not exceed 38 characters. The recommended length is 30 characters.

3. Grouping commands

3.1. Command area includes sets of navigation and activity commands. The commands look the same for users. When grouping commands, make sure the commands are grouped according to user actions not by technical similarity (object kind, action initiated by the command).

3.2. Include maximum 5-6 commands in a group.

3.3. Do not create groups with a single command only.

Correct:

Incorrect:

Do not create groups with a single important command only.

Correct:

Incorrect:

3.4. Name groups. Group names must not match system group names (Create, Reports, Tools, Important, See also). Provide titles for groups that contain several commands and one important command only.

Correct:

Incorrect: