Global Page Templates

Last Updated 07.31.03

General Description

Global Page Templates are used to construct application or suite areas that contain settings or other content that applies to the whole application or suite/portal. They are accessed from the Global Button component in the UI.

Contents of this BLAF Guideline document:

Guideline Attributes

Spec Version # - 3.1
Spec Contributors - Betsy Beier, Craig Louis
UI Models - all models
Example Products - all products
Related Guidelines -
Global Page Flow Guidelines: Contact Us, Help System, Login/Logout, Preferences, Return to Portal.
Other Guidelines: Tabs, Page Footer, Buttons (Global), Switchers: Application and Context Switchers

Interaction and Usage Specifications

General Principles

Switching to Global Areas When Work Is Incomplete

When a Global Button is selected, it may be necessary to display a Warning message to the user. If so, an error checking flow should be used. See the Save Model and Messaging Templates guidelines for details on Warning messages and saving work. The error checking flow would be called for if:

Common Components in a Global Page Template

Global Page Templates are comprised of the following common components. This guideline illustrates where the different components are positioned in the UI for Global Page templates. All components may be configured with options offered by the individual separate BLAF Guideline documents for each, and the application-specific content. (Links in following list lead to related BLAF Guideline document.)

Common Global Page Templates

The following sections describe the common Global Page templates assembled from the common components listed above.

Return to Portal

The following describes Global Return to Portal Page interaction and usage.

See the Global Button Flow: Return to Portal guideline for details of page flow.

Login and Logout

Login and logout can take place from an internet portal for hosted applications, or from the starting page of a hosted application on an intranet. See Login/Logout Flow for details on Login/Logout Page flow.

The following describes interaction and usage for both starting points.

Global Page Template - Login

Login Global Page Details

The Login Global Page should conform to the following interaction and content points:

Error & Ancillary Login Flow Pages

The following graphic show schematic representations of page templates that would appear if user input and submission on the Login page results in an error condtion. For flow detail, see the Global Button Flow: Login/Logout guideline.

Login Error & Ancillary Page Templates

Login/Logout for Internet or Hosted Applications

Login/Logout for Intranet Applications

Logout Interaction

Logout interaction is the same for the portal, intranet or internet/hosted applications.

Global Page Template - Logout

Advanced User Scenario for Logout

See Login/Logout Flow for details of page flow.

Generic Global Page Template

The following figure shows a basic Generic Global Page template to be used for global areas that are modules specific to an application as well as the other common Global Button templates described in this guideline.

Generic Global Page Template

The basic Global Page template follows these guidelines:


Suite versus Application Preferences

Preference settings, accessible from the global Preferences icon, allow users to adjust certain display and interaction options to their liking. Preferences fall into two main categories, Suite Preferences, and Application Specific Preferences.

See General Preference Settings for BLAF Applications, an ancillary document that lists many of the desired global settings, divided between suite-wide and application-specific global preference page content. Generally speaking, suite and application preference options are mutually exclusive; ie, a particular preference setting does not appear both in an application specific preferences page, and in the suite preferences page.

General Principles

Preferences Valid Content

Preferences should be presented in groups defined by page content section headings, as shown in the graphic samples below. As appropriate, an inline Tip and/or Page Title should indicate whether the visible settings apply to the current application or to all applications hosted through the portal or suite.

Preference settings commonly fall into the following areas:

The following figure shows a sample global Preferences Page template as used for Suite Preferences.

Global Page - Suite Preferences sample
Global Page - Suite Preferences sample

Global Page - Application General Preferences sample
Global Page - Application General Preferences sample

Contact Us

The following is a generic example of a Contact Us page. It may contain other content as required by the application.

Global Page - Contact Us

The following describes Global Contact Us Page interaction and usage:

See Global Button Flow: Contact Us guideline for details of page flow.


The following figure shows sample Contents and Topic pages in the Global Help Page template.

Global Page - Example of Oracle Help for Web (OHW) Contents and Specific Topic Page

The following describes Global Help Page interaction and usage.

If the application is designed in compliance with BLAF guidelines, the Help system should not be focused primarily on specific UI how-to information. The Help system should contain business processes, policies, and extra contextual information to enhance the application and users domain knowledge.

For example, Help may contain:

BLAF provides many inline user guidance methods (Instruction Text, Messaging, Tips, Hints, etc.) that should be used in the context of the application page. The inline help should be the most reliable user guidance mechanism, not the Help system. However, if a topic is of necessity verbose, consider a contextual Help link.

Simple Help Global Area

If documentation sufficient for a full Help System is not available, a Simple Help Global Area in the primary window may be used.

A Simple Help Global Area should contain at maximum only a few BLAF compliant pages. See the Preferences Global Page Template section of this guideline for a similar template.

Context Sensitive Help

When inline messaging is not sufficient, links to specific topics in the Help system may be placed in context on the application page.

Direct links to topics in the Help system may be appropriate to expand on inline user guidance. "For more details, use the Help System." (Help System would be link text.) might be placed within:

Contextual Help links are not recommended for:

See the Messaging Templates and related guidelines and for complete details on inline user guidance. See the Context Sensitive Help section of the Help Methods guideline for a more complete discussion of context sensitive Help.

For More Information

Visual Specifications

Global Button Layout

For detailed Global Button layout and Enabled, Active, and Disabled state graphics, see the Visual Specifications section of the Buttons (Global) BLAF Guideline.

Global Area Name

See the Global Level section of the Tabs/Navigation guideline for an explanation of how the Global Area Name is displayed. Also see Visual Specifications: Global Level in the same guideline.

Active, Enabled (But Not Active), And Disabled Tabs

See the Tabs/Navigation guideline for details on display, layout, and interaction of active, enabled (but not active), and disabled tabs.

Open/Closed Issues