Global Toolbar Menu

The global toolbar is the top-level toolbar to which the 3DS menu (previously named the My Desk menu), Actions, Back, Forward, and Tools menus, and other commands are connected.

The global toolbar menu is constructed as shown here.

The AEFGlobalToolbar menu looks like this in the ENOVIA products:

The AEFSeparator command simply displays a pipe symbol to visually organize the toolbar. Once a menu is expanded (by the user clicking the menu command from a toolbar), only commands can be clicked. The menus organize related sub-menus and commands.

The My Desk menu contains commands for features shared by all applications, such as issues, collections and routes, plus each application has its own submenu within this menu. When the user clicks , the entire menu structure, expanded to all sub-levels, opens. The user needs only one more click to select the needed command.

The 3DS menu shows as )on the toolbar.

The menus do not use a fixed width to display the contents. Instead, ENOVIA Business Process Services sizes the window based on the available space with a maximum number of 4 columns. If needed, a horizontal scroll bar is included to access additional columns.

The My Enovia menu includes commands and submenus that are part of ENOVIA Business Process Services and that can be used by all ENOVIA products.

The (Dassault Systemes) button is defined by the value for the image setting:

Image=${COMMON_DIR}/images/3dsButton.gif

You can remove the image (delete the value in Business Modeler) and replace it with a label. The Actions ( and Tools ()menus work the same way.

The "My Desk" metaphor dictates that the commands included in this menu should display existing information, as if users are looking through information on their desk. These menu items typically represent commands that present table pages. These table pages list objects that the user owns and/or needs to work on. When selected, these menu items display in the main frame and not in a new popup window.

The My Enovia menu includes commands and submenus that are part of ENOVIA Business Process Services and that can be used by all ENOVIA products.

ENOVIA Business Process Services includes components that are used by multiple ENOVIA products, and can be used by custom applications. For example, any application can define Tasks, and then a user's task can be accessed from the My Enovia menu.

This diagram shows the structure of the My Enovia menu:

Ovals represent commands; rectangles represent submenus. APPMyRoutes contains a submenu for Route objects; My Workflows contains a submenu for Workflows objects.

Commands in the Actions menu perform an action, such as creating a part, ECR, or product. Each application has a submenu with commands relevant to that application. When selected, Actions menu commands display in a popup window.

Actions menu commands perform actions that are not dependent on a selected item or the current context. Because users usually work within the context of a particular business item (a task, meeting, document, part, ECR, and so on), the commands for most actions appear on pages that pertain to a particular item or set of items and not on the global Actions menu. For example, one action a part owner can perform is to delete a part but the owner must first select the part to delete. Therefore, the command for deleting a part is on the Parts page.

The Tools menu contains commands typically required by all applications and installed by ENOVIA Business Process Services.

For example, commands for changing the current user's password or preferences, managing profiles (People and Organizations), running reports (Metrics), and Utilities are in the Tools menu. The context user must have access to the tools for them to display in the menu.

The Back and Forward commands are disabled when a user logs in. As the user moves from page to page, the buttons are activated.

When the user clicks the Back or Forward commands, the ENOVIA system moves to the appropriate page. Full-Text Search