Page Stamps Usage Guideline Bookmark this Guideline Printable Page


RCUI Document Version 5.0.1 for Oracle® Fusion Middleware 11g Release 1 Patch Set 1 (11.1.1.2.0)
Last Updated 10-Feb-2011

A page stamp is a read-only field that provides user connection information or task-related information.

Guideline Contents

 

Note: Images in this guideline are provided as a general reference, and may not be exact representations of FusionFX pages.

Related Guidelines

Guideline Section For Information About
Page Layout Global Control Panel,
Page Layout and Component Order
Placement of user stamps.
Content Switchers Login Switcher Use of switcher with user stamp to change login credentials.
Headers Task Stamp Use of task stamp with a header.

Related ADF Elements

Refer to the ADF Faces Rich Client demos page to find demos and tag documentation for the ADF elements related to this component:

ADF Element Notes
af:panelHeader  
af:pageTemplate  
af:showDetailHeader  
af:showDetailItem  

General Principles Bookmark this Heading Return to Top

Purpose:

Page Stamps are used to provide read-only user connection and task-related information.

Usage:

  • Page stamps are used to display data that may persist from one page to another.
  • Page stamps consist of read-only data that is typically displayed in prompt and data pairs.
  • Page stamp prompts and text have no fixed character limit but should be kept succinct to avoid excessive use of space, especially in translation. Expect length to increase up to 100 percent after translation.
  • Prompts and text should be separated by eight pixels or two letter spaces.
  • Page stamps should not be hidden by user preferences or a Disclosure icon.
  • A page stamp may not be needed if the related data is concatenated into the page title. For example, if the page title includes a customer name, then there is no need for a page stamp with the customer name.
  • There are two main types of page stamps:
    • User Stamps: For showing user login and connection-related information
    • Task Stamps: For showing status or other task-related information
  • User stamps and task stamps are displayed in different locations on the page, as shown in the following sections.
Note: Page stamps are not provided as a separate ADF component. Product teams create page stamps using the components listed in the Related ADF Elements table above.

User Stamps Bookmark this Heading Return to Top

Purpose:

Provide user login and connection-related information.

Description:

  • User stamps that indicate login type (for example, user role) or connection to a network or remote system may be shown in the Global Control Panel.
  • The Login Stamp is a special user stamp that identifies the user that is currently signed in.
    • The Login Stamp should be shown only in the branding bar of the Global layer.

Examples:

  • Connected As SYS
  • Database Tools DB
  • mbriggs (Login Stamp)

Login stamp after global links in the branding bar,  and User stamps in the Global Control Panel.

Login Stamp and User Stamps

Usage:

  • User stamps should be end-aligned in the Global Control Panel region.
  • Login stamps should only be placed after the Global Links in the branding bar. If there is not enough width to accommodate both the global links and the Login stamp, then only the global links wrap. See the Page Layout guideline for details.
  • When more than one user stamp is present, vertical pipe symbols should be used to separate the user stamps.
  • When there is not enough space to display two user stamps on the same line, the second stamp should wrap to the next line, and should be end-aligned below the first stamp.
  • In addition to the Login stamp in the branding bar, it is recommended not to exceed two user stamps per page, to avoid cluttering the Global Control Panel.
  • Product teams may associate a switcher with a user stamp to change login credentials or login target. See Login Switcher in the Content Switchers guideline for usage information.
  • It is recommended to avoid concatenating user connection strings, such as "Connected As SYS/TOOLS DB", except where needed in administrator applications due to lack of space for separate user stamps.

Login Stamp Placement adjacent to Global Links in Branding Bar, and task stamps called out in their place beneath the header toolbar.

Login Stamp Adjacent to Global Links in Branding Bar

Login Stamp placement below the global links in the Branding Bar; also showing wrapped global links, wherein the link that has wrapped is end-aligned.

Login Stamp and Wrapped Global Links in Branding Bar

Task Stamps Bookmark this Heading Return to Top

Purpose:

Provide task-related and status information.

Examples:

  • 22-Oct-2009
    [Current date without prompt]
  • 22-Oct-2009 10:15 AM
    [Current date and time without prompt.]
  • 22-Oct-2009 10:15 AM (UTC-8:00) Pacific Time
    [Current date, time, and time zone without prompt.]
  • Time Zone (UTC-8:00) Pacific Time
  • Last Saved 22-Oct-2009 10:15:22 AM
  • Last Refreshed 08-Oct-2009 12:14:47 AM
  • Order Created 04-Oct-2009
  • Status Approved
  • Space Remaining 8 MB
  • Budget Remaining 12,750.00 USD
  • Days to Quarter End 25
  • Sales Target 65,000,000.00 USD
  • Customer Joseph Chao
  • USD = United States Dollar
  • Time information should be included in task stamps only when the user needs to know that the data changes very frequently. Include the seconds display in the stamp only if the data could change several times per minute.
  • The list above provides common examples only. Product divisions may specify their own product-specific task stamps.
Note: Date, time, currency, and numeric formats vary depending on locale settings, and should follow the standard formats described in the Common Formats guideline.

Task stamps and an abbreviation key below a header toolbar

Task Stamps and Abbreviation Key Below a Header Toolbar

Usage:

  • Task stamps can be placed below different levels of headers depending on context:
    • For page-level status or task information (applicable to the entire page), multiple page stamps may be placed under the page title.
    • For section-level status or task information (applicable only to the current section), multiple page stamps may be placed under a section header.
  • Key notation may be placed below task stamps to provide scaling, symbol, currency, or abbreviation definitions. See the Key Notation section of the Headers guideline for information regarding placement and usage.
  • In all cases, task stamps should be end-aligned with the header's content region. If a header toolbar exists, task stamps should be placed directly below the header toolbar.
  • Task stamps should consist of a prompt and text with the following CSS values:
    • Prompt: 11px, Tahoma, Plain, #247275
    • Text: 11px, Tahoma, Bold, #247275
  • Task stamps should be stacked when more than one task stamp is placed below a header.
  • To avoid cluttering the page, it is recommended to keep task stamps to a minimum:
    • Do not use more than four task stamps per page.
    • Do not place more than three task stamps below a header or subheader.

Page Stamps and Context Regions Bookmark this Heading Return to Top

Both page stamps and a Context Region can be used to display read-only data. As a general rule, consider using page stamps instead of a context region when the number of page stamps does not exceed three per page.

The following table shows key differences between page stamps and context regions:

Differences in... Page Stamps Context Region
Function Display read-only data that is not necessarily linked to any process or task Displays read-only data to remind users of selections made on one or more prior pages in a process
Scope Applicable to the entire page, or a section of the page Applicable only to the entire page
Location Multiple locations on the page, including below the page title Below the page title only
Text style Regular teal text for prompts and bold teal text for data (except for user stamp) Regular black text for prompts and data (standard prompt/data formatting)
Recommended number Up to three page stamps below a header or subheader, but no more than four per page Three to four prompt/data pairs within a single context region; only one context region permitted per page
Layout Single column end-aligned in the header region below the toolbar One- or two-column layout inside the Global layer, or inside the Primary or Secondary control panel below the page header