The global context area allows users to see and access a variety of information quickly. The items that are displayed on the global context area depend on the modules and applications that have been installed in your environment.
The global context area is comprised of three separate navigation containers, the PrimaryNavContainer, the SecondaryNavContainer and the OptionsNavContainer. Each navigation container is a component of type NavContainer, which defines the navigational item components of type NavItem that will be displayed in the UI. The following individual navigation classes make up the entire global context area architecture:
NavItem– ANavItemcomponent encapsulates the components that make up a single navigational element within the UI. ANavItemis comprised ofNavSearch,NavContentandNavActionelementsNavSearch– ANavSearchcomponent provides the display and control elements that are displayed and executed when a user clicks the search option on theNavItemNavContent– This component provides the display and control elements that are displayed and executed when a use clicks on the context area of theNavItemNavAction– ANavActiondefines the display and control elements for a single action.NavActionscan be referenced by aNavActionFactoryusing static component references or, in some cases can be dynamically generated by aNavActionFactory. DynamicNavActionsare those that can change in availability, appearance or execution, depending on the current state of the agent’s environmentNavActionContainer– This component defines one or moreNavActionsavailable to theNavItemNavActionFactory– ANavActionFactorycomponent provides one or moreNavActions. These components are referenced by theNavActionContainerto provide the availableNavActions
Anatomy of a NavItem
Each NavItem has a property file that contains commonly used attributes and sub-components, which can be found in:
ATG Product | Location |
|---|---|
Commerce Service Center |
|
Service Center Framework |
|
The NavAction component contains properties for a resource bundle and a label, as well as a JavaScript function call. These properties can be modified to customize the NavAction. The labels for the components are all localized in a resource bundle, which is typically FrameworkResources. Note: There are separate bundles for the Service Center Framework and Commerce Service Center
