Drill-Down Details Version 2.0.0.0Print this Page
Detail on Demand Pattern Set
 
Description
Return to Top
The Drill-Down Details pattern is the most common method of showing detailed information. The user clicks links to get to detailed information, and the contents of the page are replaced completely with the new page. Most users are used to the Web metaphor of clicking links and drilling into more detailed information. Because the page is replaced with the detail page, it is appropriate to use when details do not need to be seen in conjunction with the original page. This pattern is also suited when a user needs to display large amounts of detailed information.
 
Pattern Set Decision Table
Return to Top
  Hover
Details
Dialog Box
Details
Hide and
Show Details
Show More/
Show Less
Detail
Drill-Down
Details
Do the details become a primary resource for users and steps in their tasks? Do the users spend considerable time looking at the details? No No Yes Yes Yes
Do users need to quickly obtain details (glance and close)? Yes Yes Yes No No
Do these details need to be seen in conjunction with the other information? Yes Yes Yes Yes No
How much space do the details use? Small
read-only
form
or data
Does not exceed 512 x 384 pixels A few inches
of screen
real estate
A few inches
of screen
real estate
A page or
more of
detail
 
Pattern Sample
Return to Top

Table with Drill-Down Detail on Row Items

Users access detail information by clicking a link in the table.

Figure 1. Clicking row item to obtain detail information on that item
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Access point for details NA The access point to get to details can be a button, link, or icon button.

Drill-Down Detail on Another Page

Users can access the original page by navigating back through the breadcrumbs or by clicking the Done button.

Figure 2. Drilling-down to detail on another page
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Detail Page Button

Done: (If read-only) Returns user to the previous page.

If the page contains transactional fields:

  • Cancel: Cancels the transaction and returns the user to the previous page
  • Save (optional): Saves any changes and remains in the current page for the user to continue editing
  • Save and Close, Publish, Submit, or Finish: Commits the transaction, returns the user to the previous page, and displays a confirmation message

NA
Detail Page Title
  • If read-only, use this format: <Object Type>: <Object Name> (for example, Expense Report: WBJ3008D)
  • If editable, use this format for transactional information:
    <Action> <Object Type>: <Object Name> (for example, Approve Expense Report: WBJ3008D)
NA
 
Related Guidelines
Return to Top
Headers Guidelines for headers and subheaders including show/hide regions
Page Actions Guidelines for page actions for dialogs or pages
Secondary Windows Guidelines governing the use of secondary windows or dialog boxes
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights