Master/Detail Flows

Last Updated 20-Jan-2004

General Description

A Master/Detail Flow is used to enable a user to easily view and/or update objects and object details in a single, high density page. It is ideally used in "professional" applications where high density data screens and high user productivity are required. The flows shown in this guideline are flows using typical Master/Detail options.

Guideline Attributes

Spec Version # - 3.1
Spec Contributors - Lisa Serface, Raymond Wong
UI Models - all models
Example Products - all products
Related Guidelines - BLAF Users: Self Service vs. Professional Applications, Object List Templates, Object Templates, Table Navigation/Action Methods, Table Flows, HGrid Flows, Tables, HGrid. Master/Detail Templates

Interaction and Usage Specifications

A Master/Detail flow generally uses the following templates:

A Master/Detail Template can be described as follows:

Master/Detail templates are object centric. The information/content on the entire page displays master objects or object and detailed object/object based on selection of a master.
Master Object - A master object(s) is either a single object, a list of objects, or a tree hierarchy of objects. Each object contains subordinate information that is displayed in the details portion of the template. Note that the HGrid component may not be used for master objects -- see the Master/Detail Templates guideline for details.
Detail Object - A detail object(s) is either a single object, a list of objects (tabular), multiple object properties (subtab) or a hierarchy of objects (HGrid). The objects are displayed based on selection within the master objects. The detail object(s) may have subordinate information or further details. This is displayed on another "drill down" page and follows one of the standard BLAF Object Template options (i.e., single page, 2 page, 3+ pages, page with side nav, page with subtabs.)
Selection of Master Record - A master record is selected when user chooses the "Select" radio button for a master record within a list of objects or tree hierarchy of objects. The details are displayed in the details section of the same page.

Note: If the user removes a row in a master table, the page refreshes with the next master row selected by default, and the details of this newly selected row appear in the details section.

Examples of different types of Master/Detail flows are provided below:

Visual Specifications

See template guidelines for details about the individual page templates. From that guideline, see the individual components for detailed visual specifications.

Open Issues

03.17.03 "Full Update" Flow to be added.

Closed Issues

20-Jan-2004: Specified that HGrid may not be used for master objects, and added note about behavior when user deletes a row in a master object list.