Page Details Version 2.0.0.0Print this Page
Navigating Record Sets Pattern Set
 
Description
Return to Top
The Record Navigation: Page Details pattern enables users with a repetitive task to navigate from one detail page to another without having to return to the main object list or table.  This pattern enables a more efficient means of navigating detail pages when users are working on lists of records because they are moved sequentially between detail pages to perform actions. This pattern can be applied at the page level or subheader level.
 
Pattern Set Decision Table
Return to Top
 
Drill-Down Details
Dialog Box Details
Page Details
Master Detail

Is there a lot of object information that needs to be viewed or updated?

Yes

No

Yes

Yes

Does the user need the context of other records while viewing the details of a specific record?

No

Yes

No

Yes

Is there a need to quickly scan through records?

No

Yes

Yes

Yes

Is there a need to compare certain attributes of these records against each other?

No

Yes

No

Yes

Is the user working on very large objects, spending considerable time focusing on only those details?

Yes

No

No

Maybe

Is the user working through a list of objects quickly?

No

Yes

No

Yes

Is there a need to update or take action on multiple objects as a group?

No

Maybe

Maybe

Yes

 
Record Relationship Decision Tool
Return to Top
  Linear Navigation Nonlinear Navigation
Does the user need to select a subset of records to edit (multiselect)?

No

Yes

Does the user need to edit any of the fetched records in the table? The selected record is a starting point to edit any fetched records.

Yes

No

 
Pattern Sample
Return to Top
Linear Navigation
The user navigates in a linear sequence from the detail page of the first record accessed to the detail page of the last record in the master object list.
Figure 1. Navigating in a linear sequence
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Page Title
  • Use this format (if the page contains fields that you cannot edit: <Object Type>: <Object Name>

    For example: Employee Information: Sandra Blake
  • Use this format (if page contains fields that you can edit): Edit <Object Type>: <Object Name>

    For example: Edit Employee Information: Sandra Blake
Product teams can apply this pattern to other headers regions on their pages.
Page Toolbar
  • Navigational component:
    Back button: Navigates the user to the previous record.
    Next button: Navigates the user to the next record.

  • If page contains editable fields:
    Save Model buttons: See Save Model guidelines for appropriate set of buttons.
    Cancel button: Cancels any unsaved changes and returns to the page prior to the record navigation.
Product teams can apply this pattern to other headers regions on their pages.

Nonlinear Navigation
Nonlinear navigation enables users to select a subset of contiguous or noncontiguous records from the master list to view or update. The users are presented with the full object details on a single page, and they can move to the next full page when they are finished.
Figure 2. Navigating in a nonlinear sequence
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Page Title
  • Use this format (if the page contains fields that you cannot edit): <Object Type>: <Object Name>

For example: Employee Information: Sandra Blake

  • Use this format (if the page contains fields that you can edit): Edit <Object Type>: <Object Name>

For example: Edit Employee Information: Sandra Blake

Product teams can apply this pattern to other headers regions on their pages.
Page Toolbar
  • Navigational component:
    Locator (choice list): Contains the object name of the current record.  Enables user to jump to individual records without navigating through each one. The hdden label on the choice list should use the string "Go to Record" for accessibility mode.
    Left arrow icon button: Navigates the user to the previous record. 
    Right arrow icon button: Navigates the user to the next record.

  • If page contains fields that you can edit:
    Save Model buttons: See Save Model guidelines for the appropriate set of buttons.
    Cancel button: Cancels any unsaved changes and returns to the page before the record navigation.
Product teams can apply this pattern to other headers regions on their pages.
 
Related Patterns
Return to Top

Information Entry Forms

This pattern is used when a user needs to provide varying amounts of preformatted information, usually short answers to questions.

Editing Objects

This pattern is used for editing content in a table.

 
Related Guidelines
Return to Top

Buttons

Guidelines for buttons in toolbars

Form Layout

Guidelines for form layout

Menus

Guidelines for the menu component

Page Actions Guidelines for page-level actions

Secondary Windows

Guidelines for secondary windows and dialog boxes

Tables

Guidelines for the table component

Toolbars

Guidelines for the toolbar component

 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights