FusionGPS: Design Patterns: Editing Objects Pattern Set: Master Detail Edit

Master Detail Edit

Version 2.0.0.1

Editing Objects Pattern Set


Description

Use the Master Detail Edit pattern when users need to edit the details of a master object. The user can navigate between master objects and make changes to details without leaving the page.


Pattern Set Decision Table

	Table Row Edit (Choice List)	Table Row Edit (Dialog Box)	Table Row Edit (Page)	Editable Table	Page Edit	Master Detail Edit
Is the editable content limited to one to two attributes?	Yes	No	No	No	No	No
Is the amount of editable content attributes suitable for a dialog box?	No	Yes	No	No	No	No
Does the amount of editable content require a large amount of space or a complex component?	No	No	Yes	Yes	Yes	Yes
Does the user need to see the object attributes being edited in the context of other objects?	Yes	Yes	No	Yes	No	Yes
Do the editable attributes for groups of objects need to be set to the same value?	Yes	Yes	Yes	No	No	No
Is the level of editing suitable for a self-service or novice user?	Yes	Yes	Yes for a single row, No for multiple rows	No	Yes	No


Pattern Sample

When a master object is selected in a table or a tree table, the corresponding details are refreshed in the area below. No attributes in the detail section should be reflected in the master table.

If users have permission to do so, they can edit these details in the area below the table. If master object attributes need to be edited, use one of the other editing patterns in conjunction with the Master Detail Edit pattern, such as the Table Row Edit (Dialog Box) pattern.

The changes are committed when users click the Save button.

Figure 1. Selecting a master object in a table reveals the corresponding details in the section below

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Page Title	Use this format: Edit <Object Type>: <Object Name> For example: Edit Employee Information: Sandra Blake If the Master page is empty, the header format for the detail section should be: <Detail Type>: <Object Name> Use this format (if the page contains fields that you can edit): Edit <Object Type>: <Object Name> For example: Edit Employees : J & J Electronics See the Header usage guidelines for master/detail header syntax.	NA
Page Buttons	Save Model Buttons: See the Save Model Guidelines for the appropriate set of buttons. Cancel: Cancels any unsaved changes and returns the user to the page before the record navigation.	NA
Master/Detail Layout	To find the appropriate master/detail layout for your data, see the Record Navigation:Master/Detail pattern. If the master table is empty, the details section should only contain the instruction text "No data to display."	Master and Detail should be in the same level unless the Master is the header section then the Detail should appear in the sub-header section.
Disclosure Icon	Hide or collapse either the master or detail section. The location of the Disclosure icon affects interaction style: Disclosure icon present at the Master section: Master and Detail should be in the same level unless the Master is the header section then the Detail should appear in the sub-header section; hence, on collapsing the Master section, the Detail section is also collapsed. Disclosure icon present at the Detail section: Because the Detail section contains the Disclosure icon, only the detail section is collapsed, not the Master section as seen in figure 1. Disclosure icon present at both Master section and Detail section: In this Layout, Master and Detail should be in the same level unless the Master is the header section then the Detail should appear in the sub-header section. If the Detail section is expanded, then on collapsing the Master section, the entire section is collapsed. When expanding the Master section, the Detail section remains expanded, as it was prior to collapsing. If the Detail section is collapsed, then on collapsing the Master section, the entire section is collapsed. On expanding the Master section, the Detail section remains collapsed as it was prior to collapsing.	Note: The expand/collapse state of the details section should not depend on the content of the master table.


Related Guidelines

Buttons	Guidelines for buttons in toolbars
Form Layout	Guidelines for form layout
Page Actions	Usage information and design guidance for buttons at the page level and on secondary windows
Save Model	Save Model information and design guidance for Oracle Fusion applications
Tree Table	Guidelines for the Tree Table component
Tables	Guidelines for the table component
Toolbar	Guidelines for the toolbar component

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