FusionGPS: Design Patterns: Record Navigation Pattern Set: Secondary Window Details

Dialog Box Details

Version 2.0.0.0

Navigating Record Sets Pattern Set


Description

The Record Navigation: Dialog Box Details pattern enables users with a repetitive task to navigate from one set of object details to another. This pattern provides 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 in a dialog box. The dialog box is limited in size and therefore this is best suited for a small set of attributes.


Pattern Set Decision Table

	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	No	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

	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? A selected record is a starting point to edit any fetched records.	Yes	No


Pattern Sample

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. Record selection in the master table and the dialog box is synchronized. The record being viewed in the dialog box corresponds with the record selected in the underlying table.

Figure 1. A selected record in the master table

Figure 2. A dialog box displaying details of the record selected in the master table

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Secondary Window	If read-only, the window should be in a modeless state. If the window contains fields that you can edit, the window should be in a modal state.	NA
Secondary Window Title	If read-only, use this format: <Object Type> For example: Expense Report If the window contains fields that you can edit, use this format: <Action> <Object Type> For example: Approve Expense Report	NA
Secondary Window Header	If read-only, use this format: <Object Type> <Object Name> For example: Expense Report WBJ3008D If the window contains fields that you can edit, use this format: <Action> <Object Type>: <Object Name> For example: Approve Expense Report: WBJ3008D	NA
Secondary Window Buttons	If read-only: Previous: Navigates user to the previous record. Next: Navigates user to the next record. OK: Closes the dialog box. If the window contains fields that you can edit: Previous: Navigates the user to the previous record. Next: Navigates the user to the next record. OK: Caches changes, closes the dialog box, and returns control to the base page. Use Save and Close instead if the changes in the dialog box are permanent. Cancel: Cancels the transaction and returns to the previous page.	NA

Figure 3. Selecting to view the next record in sequence

Figure 4. Selected record in the master list

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Changed Items	If the window contains fields that you can edit, updated items should be identified using a changed item indicator.	NA

Nonlinear Navigation

Nonlinear navigation enables users to select a subset of contiguous or noncontiguous records from the master list to view or update. When using the drop-down list to navigate between records, there must be a single unique attribute (for example, name) associated with the record that can appear in the drop-down list. The user must also be able to identify the record with the attribute that appears in the drop-down list.

Figure 5. Selecting a subset of records from the master list

Figure 6. A dialog box displaying details of the record selected in the master list

Required Screen Elements
Component Type	Required Components	Customizable/Extendable Components
Secondary Window	If read-only: Window should be in a modeless state. If window contains fields that you can edit: Window should be in a modal state.	NA
Secondary Window Title	If read-only, use this format: <Object Type> For example: Expense Report If the window contains fields that you can edit, use this format: <Action> <Object Type> For example: Approve Expense Report	NA
Secondary Window Header	If read-only, use this format: <Object Type> <Object Name> For example: Expense Report WBJ3008D If the window contains fields you can edit, use this format: <Action> <Object Type>: <Object Name> For example: Approve Expense Report: WBJ3008D	NA
Secondary Window Buttons	If read-only: Previous: Navigates user to the previous record. Record Navigator (choice list): Enables the user to jump to another record without having to navigate through each one. Next: Navigates user to the next record. OK: Closes the dialog box. If the window contains fields that you can edit: Previous: Navigates the user to the previous record. Record Navigator (choice list): Enables the user to jump to another record without having to navigate through each one. Next: Navigates the user to the next record. OK: Caches changes, closes the dialog box, and returns control to the base page. Use Save and Close instead if the changes in the dialog box are permanent. Cancel: Cancels the transaction and returns to the previous page.

Figure 7. Jumping to other records without having to navigate through each record

Figure 8. Selected record in the master list

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Changed Items	If the window contains fields that you can edit, updated items should be identified using a changed item indicator.	NA


Related Patterns

Information Entry Forms	Use when a user has to provide varying amounts of preformatted information, usually short answers to questions.
Editing Objects	Use for editing content in a table.


Related Guidelines

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