Master/Detail Templates provide a high density page that allows a user to easily
view and/or update objects and object details in one page. The templates are ideal
to use in "professional" applications where high density data screens and high
user productivity are required. The Master/Detail templates are based on other
core BLAF templates, namely Object List Templates and Object Templates. There
are several different valid Master/Detail Templates in BLAF to support the wide
variety of types of objects, object hierarchies, and object details in BLAF applications.
Below outlines the contents of this guideline:
Use of Master/Detail templates are good for "professional" applications where
a user is accustomed to high density screens and needs to easily navigate through
lists and/or hierarchies of information to see details.
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
(tabular), or a hierarchy of objects. Each object contains subordinate information
that is displayed in the details portion of the template.
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. 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.)
Most master/detail templates may be view only or updateable (unless noted
per specific option.)
If updateable, the proper save model must be implemented. See below for more
details.
For a Table
as a master or detail the following table elements may be used as needed
by the application:
a select column used to both select a master object for display of its details
AND other select/act functions
functional icons (in columns)
global table buttons
record navigation (for a Table ONLY)
selection controls (select all/select none) if multiple select
refresh action area of table (if necessary)
For a Table
as a master or detail the following table elements may NOT be used:
hide/show row or cell details
HGrids may only be used for details, and may NOT be used for master objects:
Most HGrids contain heterogeneous contents, which require different details
layout depending on the node selected in the master list. This is technically
feasible using a master tree, because it is rendered in a separate frame, but
this is not the case for HGrids, and would cause development problems.
HGrids, especially when expanded, typically constitute long lists that scroll
extensively. In this case, the Details section would not be visible without scrolling.
For a single object as a detail, section level buttons may be used to act
on the object.
For multiple properties/objects as details (SubTab Layout):
All subtabs should be peer information (no hierarchical information across
subtabs.)
Subtabs should independent (i.e., it should not be required to change one
property in a subtab before another.)
Properties within a subtab may be view only or updateable.
Within a subtab/object property:
The property may be displayed as a table with all valid table controls.
The property may be displayed in label/data layout.
The property may not contain an HGrid.
There may be multiple sections within a subtab/property, but should be limited
to no more than 3.
Contextual information may optionally be placed in a master/detail page. For
instance, if the page is used for updating employee information in a company,
then the contextual information of the company (e.g. company name, location, etc.)
may be shown along with the master and detail sections.
The updateable task (i.e. "Update", "Create" etc.) applies to the grandparent,
master and detail object sections, respectively.
Contextual information is placed beneath the page title (e.g. "Update Employees")
of the master/detail page.
The contextual information should be read-only.
Searching or Views
(Note: searching is not relevant for a single object detail.)
If searching is necessary, a "Focus on [ObjectType]" global table button should
be present with the Table or HGrid. When selected, it navigates the user to an
Object List Page with search and multiple select results. From this page, the
user can search and select specific detail objects to be displayed in the Details
Table of the Master/Details Page. Note:The results from each search are not saved. Each time
a user a performs search, the results from the previous search is discarded.
Views functionality is not allowed on the master or detail objects.
Object List Template , with only the detail
objects on the page. The user can navigate/toggle back to the master/detail template
with a "View with Details" or Master" page level button. If a search is performed
on the detail table (or HGrid for details), then user selects [...]" toggle button,
results are persistent layout (the criteria does not persist.)
If either the master and/or detail objects (single object, list of objects
or hierarchic of objects) are updateable, a page level "Apply" or "Finish" button
and "Cancel" must be present.
If the master object (Table, Label/Data) is updateable, and the user changes
values, then selects detailed information, the changed values of the master should
be cached.
If the user selects one master object, updates the detail information, then
selects another master object, and updates those details, the changes for all
detail level updates within the page should be cached.
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.
Once the user is done with the updateable page, he/she selects "Apply" and
all changes made (to the master table, and/or all the detail objects including
detail properties spanning the subtabs) should be saved. If he/she selects "Cancel"
all the changes will be disregarded.
If the user drills down to another page of details (via a linked object in
table, an action/navigation button or icon in table/HGrid, a section level button
relating to the single object details), the updated information from the entire
master/detail template should be cached.
If the user selects another tab, horizontal navigation, global button, footer
links or related link that may take the user to a completely separate content
area or task/transaction, a warning page should be shown that follows the model
described in the Save Model guideline.
Object List Page Template - If an application
has a deep hierarchy of content, it may be appropriate to first display an Object
List template, then once the user drills down on an object, he/she is presented
with the master/detail template (containing subordinate objects to the initial
object list.) This is the recommended launch point.
Home Page Template - There may be a link or icon on the home page (aggregate
content of the application) that takes the user directly to a master/detail template
within the application.
Oracle Application Portal - There may be a link or item in a portlet of the
portal referring to a specific group of objects in an application. When selected,
the master/detail template within the specific application is displayed.
NOT A VALID OPTION: For both usability reasons (expanded HGrids scroll
extensively, thus pushing details far down the page) and technical reasons (most
HGrids contain heterogeneous contents, which require different details layout
depending on the node selected in the master list).
When master or detail is updateable, follow the Save Model
information above.
Children objects is drawn on initial page load.
Page level navigation buttons include a "Cancel", "Back", "Next" and "Finish"
button to allow the user to navigate between single master objects. (Note: the
detail object list will be redrawn as the user navigates to a new master object.)
The page level button configuration is repeated at the top and bottom of the page.
There may be other page level action/navigation buttons depending on the context.
Additional buttons are located between the "Cancel" and "Back" buttons.
Single Master Page Level Navigation
Along with the next/back button configuration, there is also a choice list of
master objects. The choice list allows for 29 objects/items within it, and a "More...".
When the user selects the "More..." link, the page is redrawn to the 30th object,
and the 30th item is shown in the choice list. The choice list items now contain;
a "Previous..." item as the first item in the list, the next 29 items, and "More...".
If there are less than 29 items in the list, the "More..." item does not show
in the list.
There are three syntax options for the contents of
the choice list:
Syntax to use if object names are very long: "[X] of [TotalNumber]" (i.e.,
"2 of 134")
Syntax to use if object name can be displayed: "[ObjectName] ([X] of [TotalNumber])"
(i.e., "Legal (14 of 132)")
Syntax to use if no total number is available: "[ObjectName] ([X])" (i.e.,
"Legal (14)")
Master Object (Label/Data)
Master is represented as a single object (label/data layout).
Recommended to be updateable (with widgets). When a master object is updated,
and the user selects another master object (with page level navigation), the data
is cached until the user selects the page level "Finish".)
The master section should not be multiple sections/properties, only basic
and/or required attributes of the object.
An optional "Full Update" button can be used to access full object details.
When selected, the user will navigate (drill-down) to a full, updateable Object
Template. To return the master/detail layout, user selects the page level "Apply"
button on the Object Template page.
Full master object (when drilled down) may be represented in any valid Object
Template (1 page, 2 page, Step by Step/Train page, Side Nav page, SubTab page.)
Detail List of Objects Table
Detail is a table of objects that is displayed based on the single master
object. It is displayed on full page reload, as the user navigates through objects.
The detail section title should use the following syntax: "[MasterObjectName]:[DetailObjectType]"
(i.e., Accounting: Employees.)
An optional "Focus on [DetailObjectType]" global table button navigates the
user to an Object List Page with only the detail object list on the page. This
page may allow more functions and options like searching.
In the Object List Page, the user can select specific detail object(s) to
be displayed in the Details Table of the Master/Details Page. This page has page
level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details
Page.
The "Select" button returns selected object(s) from the Object List Page to
the Details Table in the Master/Details Page. If no objects are selected from
the table, then selecting the button will return the user to the Master/Details
Page without selecting any data.
A "Show All" global table button displays the full list of objects in the
Details Table. This button appears only if the Focus on [DetailObjectType] global
table button is present AND after it is used to focus on subsequent detail object(s)
from the initial list.
To access "full" child object:
Link on child's name - when selected will navigate the user to a view only
Object Template.
Either control bar button or icon in cell of table - when selected will navigate
the user to an updateable Object Template.
Detail object may be represented in any valid Object Template (1 page, 2 page,
Step by Step/Train page, Side Nav page, SubTab page.)
Single Object Details/List of Objects Example: Departments
Page Level Navigation - Choice List of Master Objects
Example Option when Master Object Names are too Long:
Example Option with Master Object Names:
Example Option with Master Object Names (no total number):
When master or multiple details are updateable, follow the Save Model information above.
First subtab/detail object properties is drawn on initial page load.
Page level navigation buttons include a "Cancel", "Back", "Next" and "Finish" button to allow the user to navigate between
single master objects. (Note: the detail subtab layout will be redrawn as the user navigates to a new master object.) The page
level button configuration is repeated at the top and bottom of the page. There may be other page level action/navigation
buttons depending on the context. Additional buttons are located between the "Cancel" and "Back" buttons.
The page level navigation follows the same principles as stated above under the Single Object Details/List of Objects
master/detail template. See Single Master Page Level Navigation above.
Master Object (Label/Data)
Master is represented as a single object (label/data layout).
Recommended to be updateable (with widgets). When a master object is updated, and the user selects another master object
(with page level navigation), the data is cached until the user selects the page level "Finish".)
The master section should not be multiple sections/properties, only basic and/or required attributes of the object.
An optional "Full Update" button can be used to access full object details. When selected, the user will navigate
(drill-down) to a full, updateable Object Template. To return the master/detail layout, user selects the page level "Apply"
button on the Object Template page.
"Full" object details (all object properties), are in the subtab detail section below the master.
Full master object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Details as Multiple Object Properties
Detail properties of objects are displayed in a subtab layout. Content under the SubTabs is based on the single master
object. The first subtab detail property is displayed as default when first navigate to the page.
Changing subtab property sections is a partial page redraw.
The subtab layout represents the "full" object details. Within each property of the object, there may be a:
Table
link on child object's name in table- when selected will navigate the user to a view only Object Template of that child
object.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object Template
of child object.
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific detail object(s) to
be displayed in the Details Table of the Master/Details Page.
This page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Details Table in the Master/Details Page.
If no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Details Table. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent detail object(s) from
the initial list.
Label/Data Layout
Note: HGrid within a property is not allowed.
Single Object Details/Multiple Object Properties: Customer and Customer Property with Table
Single Object Details/Multiple Object Properties: Customer and Customer Property as Label/Data
When master or detail is updateable, follow the Save Model information above.
Children hierarchy of objects are drawn on initial page load.
Page level navigation buttons include a "Cancel", "Back", "Next" and "Finish" button to allow the user to navigate between
single master objects. (Note: the detail object list will be redrawn as the user navigates to a new master object.) The page
level button configuration is repeated at the top and bottom of the page. There may be other page level action/navigation
buttons depending on the context. Additional buttons are located between the "Cancel" and "Back" buttons.
The page level navigation follows the same principles as stated above under the Single Object Details/List of Objects
master/detail template. See Single Master Page Level Navigation above.
Master Object (Label/Data)
Master is represented as a single object (label/data layout).
Recommended to be updateable (with widgets). When a master object is updated, and the user selects another master object
(with page level navigation), the data is cached until the user selects the page level "Finish".)
The master section should not be multiple sections/properties, only basic and/or required attributes of the object.
An optional "Full Update" button can be used to access full object details. When selected, the user will navigate
(drill-down) to a full, updateable Object Template. To return the master/detail layout, user selects the page level "Apply"
button on the Object Template page.
Full master object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Detail Hierarchy of Objects
Detail is a hierarchy of objects (HGrid) that is displayed based on the single master object.
It is displayed on full page reload, as the user navigates through master objects.
The detail section title should use the following syntax: "[DetailObjectType(s)]" (i.e., Banks and Branches.)
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific child object(s) to be
displayed in the Details Table of the Master/Details Page. It should
have a flat list table (i.e. no select/act functionality) with columns
listed in the following order:
[ObjectName] - used for showing the name of each detail object as read-only information.
[ChildObjectPath] - used for showing the hierarchical path of the child object as read-only information.
View Hierarchy (Icon) - used for viewing the hierarchy of the child object. When selected, it navigates the user
back to the Master/Details Page with the hierarchy of selected child object focused on the Detail Objects HGrid.
A "Show All" global table button displays the full list of child objects in the HGrid. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent child object(s) from the
initial list.
To access "full" child object:
Link on child's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object Template.
Full detail object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Single Object Details/Hierarchy of Objects Example: Bank and Branches/Accounts Hierarchy
When master or detail is updateable, follow the Save Model information above.
Master Objects Table:
Master is a table of objects.
When an object in the master table is selected from the single select column, the details section below draws with
subordinate objects (as a table.)
Multiple selection of objects is not allowed in the Master Objects Table. If multiple selection is functionally
required and there are drill down actions for the objects, then the actions will have to be performed in separate page, such as
an Object Template.
An optional "Focus on [MasterObjectType]" global table button navigates the user to an Object List Page with only the
master object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific master object(s) to
be displayed in the Master Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Master Table in the Master/Details Page. If
no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Master Table. This button appears only if the
Focus on [MasterObjectType] global table button is present AND after it is used to focus on subsequent master object(s) from
the initial list.
To access "full" master object:
Link on master object's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object
Template
Full master object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Children Objects Table
Details are a table of objects based on the selection of a master object.
The detail section title should use the following syntax: "[MasterObjectName]:[DetailObjectType]" (i.e., Accounting:
Departments, Paris Trip: Expense Line Items.)
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific detail object(s) to
be displayed in the Details Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Details Table in the Master/Details Page.
If no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Details Table. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent detail object(s) from
the initial list.
To access "full" child object:
Link on child's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object
Template.
Full detail object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
List of Objects/Children List of Objects Example: Organizations and Departments
Page represents list of objects; and a selected objects' details in hierarchical format.
Follow the Functionality standards above for options allowed in the master table and detail
HGrid
When master or detail is updateable, follow the Save Model information above.
Good for objects that have associated hierarchical details.
Master Objects Table:
Master is a table of objects.
When an object in the master table is selected from the single select column, the details section below draws with
subordinate hierarchical objects (as a HGrid)
Multiple selection of objects is not allowed in the Master Objects Table. If multiple selection is functionally
required and there are drill down actions for the objects, then the actions will have to be performed in separate page, such as
an Object Template.
An optional "Focus on [MasterObjectType]" global table button navigates the user to an Object List Page with only the
master object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific master object(s) to
be displayed in the Master Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Master Table in the Master/Details Page. If
no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Master Table. This button appears only if the
Focus on [MasterObjectType] global table button is present AND after it is used to focus on subsequent master object(s) from
the initial list.
To access "full" master object:
Link on master object's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object
Template
Full master object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Child Objects Hierarchy
Details are represented as a hierarchy of objects (HGrid) based on the selection of a master object.
The detail section title should use the following syntax: "[MasterObjectName]:[DetailObjectType]" (i.e., Hodges Remodel:
Tasks.)
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific child object(s) to be
displayed in the Details Table of the Master/Details Page. It should
have a flat list table (i.e. no select/act functionality) with columns
listed in the following order:
[ObjectName] - used for showing the name of each detail object as read-only information.
[ChildObjectPath] - used for showing the hierarchical path of the child object as read-only information.
View Hierarchy (Icon) - used for viewing the hierarchy of the child object. When selected, it navigates the user
back to the Master/Details Page with the hierarchy of selected child object focused on the Child Objects HGrid.
A "Show All" global table button displays the full list of child objects in the HGrid. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent child object(s) from the
initial list.
To access "full" child object:
Link on child's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object
Template.
Full detail object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
List of Objects/Hierarchy of Objects Example: Projects and Tasks (Hierarchical)
Page represents list of objects; and single object details (from list.)
Follow the Functionality standards above for options allowed in the master table and
label/data details.
When master or detail is updateable, follow the Save Model information above.
Good for list of objects that have associated object details (small set of details).
Master Objects Table:
Master is a table of objects.
When an object in the master table is selected from the single select column, the details section below draws with
label/data layout of object details.
Multiple selection of objects is not allowed in the Master Objects Table. If multiple selection is functionally
required and there are drill down actions for the objects, then the actions will have to be performed in separate page, such as
an Object Template.
An optional "Focus on [MasterObjectType]" global table button navigates the user to an Object List Page with only the
master object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific master object(s) to
be displayed in the Master Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Master Table in the Master/Details Page. If
no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Master Table. This button appears only if the
Focus on [MasterObjectType] global table button is present AND after it is used to focus on subsequent master object(s) from
the initial list.
If master is updateable (with widgets), updateable attributes in master table can NOT be repeated in object details
Control Bar MAY NOT include "Update" button, or there cannot be an update column with a functional icon. This functionality
is accessed by selecting the master object from the single select column to display updateable object details in the detail
section.
There should not be a link on the master object name. To access full object details, the user must select the master object
from the single select column, then select the "Advance Update" button in the detail section.
Single Object Details
Details are represented as a single object (label/data layout) based on the selection of a master object.
Recommended to be updateable (with widgets). When a detail object is updated, and the user selects another master object,
the previously selected master object row's contents may update when the detail is selected to reflect any changes that have
been made. (Note: the data is cached until the user selects the page level "Apply".)
The details should not be multiple sections/properties, only basic and/or required attributes for an object.
The detail section title should use the following syntax: "[MasterObjectType]:[DetailObjectName]" (i.e., Employee: John
Doe.)
Page represents list of objects; and a single object with multiple properties.
Follow the Functionality standards above for options allowed in the master table and details
in SubTabs.
When master or detail is updateable, follow the Save Model information above.
Good for list of objects that have associated object details (associated object has multiple properties).
Master Objects Table:
Master is a table of objects.
When an object in the master table is selected from the single select column, the details section below draws with SubTab
layout of an objects properties. Each object property details is within a subtab section.
Multiple selection of objects is not allowed in the Master Objects Table. If multiple selection is functionally
required and there are drill down actions for the objects, then the actions will have to be performed in separate page, such as
an Object Template.
An optional "Focus on [MasterObjectType]" global table button navigates the user to an Object List Page with only the
master object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific master object(s) to
be displayed in the Master Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Master Table in the Master/Details Page. If
no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Master Table. This button appears only if the
Focus on [MasterObjectType] global table button is present AND after it is used to focus on subsequent master object(s) from
the initial list.
If master is updateable (with widgets), updateable attributes in master table can NOT be repeat in object details.
Control Bar MAY NOT include "Update" button, or there cannot be an update column with a functional icon. This functionality
is accessed by selecting the master object from the single select column to display updateable object properties under the
SubTab.
There should not be a link on the master object name. To access full object details, the user must select the master object
from the single select column, then select the "Advance Update" button under the SubTab in the detail section.
Single Object with Multiple Properties
Each object property or detail is represented as a section under the SubTab bar. The first SubTab section is displayed as a
default when the master row is selected.
The detail section title should use the following syntax: "[MasterObjectType]:[DetailObjectName]" (i.e., Employee: John
Doe.)
Changing SubTab sections is a partial page redraw.
The subtab layout represents the "full" object details. Within each property of the object, there may be a:
Table
link on child object's name in table- when selected will navigate the user to a view only Object Template of that child
object.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object Template
of child object.
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific detail object(s) to
be displayed in the Details Table of the Master/Details Page.
This page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Details Table in the Master/Details Page.
If no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Details Table. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent detail object(s) from
the initial list.
Label/Data Layout
Note: An HGrid should not be used in a SubTab section.
Properties under the SubTab are recommended to be updateable (with widgets). When a detail object is updated, and the user
selects another master object, the previously selected master object row's contents may update when the detail is selected to
reflect any changes that have been made. (Note: the data is cached until the user selects the page level "Apply".)
List of Objects/Single Object with Multiple Properties Example: Employees and an Employee (Property as
Label/Data)
List of Objects/Single Object with Multiple Properties Example: Employees and an Employee (Property as
Label/Data)
Page represents list a hierarchy objects; and a selected objects' details in tabular format.
When master or detail is updateable, follow the Save Model information above.
Good for hierarchical objects that have associated detail objects.
Master Objects as Tree (in Side Nav):
Master is a hierarchy of objects.
When one of the objects in the tree is selected, the details section draws with subordinate list of objects.
Depending on the detail contents for each item in the Tree, it is possible to show a different master/detail template
depending on what object type is selected. For instance, if the master tree is a hierarchy of banks, branches and accounts, and
the user selects an account, the details section may redraw with single object details regarding that account (Hierarchy of Objects/Single Object Details). If the detail icon is selected for a branch, the details
section may redraw with a table of objects, or all accounts associated with the branch.
If the user selects expands a parent in the tree, selects children details, then collapses that same parent node, the
children details still remains on the page. The details are persistent until another object is selected in the tree.
Children Objects Hierarchy
Details are represented as a list of objects based on the selection in the master tree.
The page title should use the following syntax: "[ParentObjectName]:[DetailObjectType]" (i.e., Alameda Branch: Accounts.)
Note: the full hierarchical path is not represented in the section title, just the parent object name.
An optional "Focus on [DetailObjectType]" global table button navigates the user to an Object List Page with only the
detail object list on the page. This page may allow more functions and options like searching.
In the Object List Page, the user can select specific detail object(s) to
be displayed in the Details Table of the Master/Details Page. This
page has page level "Cancel" and "Select" buttons:
The "Cancel" button cancels out all actions and returns user to the Master/Details Page.
The "Select" button returns selected object(s) from the Object List Page to the Details Table in the Master/Details Page.
If no objects are selected from the table, then selecting the button will return the user to the Master/Details Page without
selecting any data.
A "Show All" global table button displays the full list of objects in the Details Table. This button appears only if the
Focus on [DetailObjectType] global table button is present AND after it is used to focus on subsequent detail object(s) from
the initial list.
To access "full" child object:
Link on child's name - when selected will navigate the user to a view only Object Template.
Either control bar button or icon in cell of table - when selected will navigate the user to an updateable Object
Template.
Full detail object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Hierarchy (as Tree) of Objects/List of Objects Example: Projects (Hierarchical) and Budgets
Page represents hierarchy of objects; and single object details (from list.)
When master or detail is updateable, follow the Save Model information above.
Good for hierarchies of objects that have associated object details.
Master Objects as Tree (in Side Nav):
Master is a hierarchic of objects.
When one of the objects in the tree is selected, the details section draws with selected objects details.
Depending on the detail contents for each item in the Tree, it is possible to show a different master/detail template
depending on what object type is selected. For instance, if the master tree is a hierarchy of banks, branches and accounts, and
the user selects an account, the details section may redraw with single object details regarding that account (Hierarchy of Objects/Single Object Details). If the detail icon is selected for a branch, the details
section may redraw with a table of objects, or all accounts associated with the branch (Hierarchy of
Objects/List of Objects).
If the user selects expands a parent in the tree, selects children details, then collapses that same parent node, the
children details still remains on the page. The details are persistent until another object is selected in the tree.
Single Object Details
Details are represented as a single object (label/data layout) based on the selection of a master object.
Recommended to be updateable (with widgets). When a detail object is updated, and the user selects another master object,
the previously selected master object row's contents may update when the detail is selected to reflect any changes that have
been made. (Note: the data is cached until the user selects the page level "Apply".)
If master is a hierarchy represented as a Tree, the details may have multiple sections on the detail portion of the page as
necessary.
The detail section title should use the following syntax: "[MasterObjectType]:[DetailObjectName]" (i.e., Employee: John
Doe.)
To access "full" object details, use a section level "Advanced Update" button. When selected, the user will navigate to the
full Object Template. (When the master is represented as a tree, the full detailed label/data object may be present on the same
page, and "Advanced Update" may not be necessary. If necessary, it should be an additional page level button to drill-down to
full object details.
Full detail object (when drilled down) may be represented in any valid Object Template (1 page, 2 page, Step by Step/Train
page, Side Nav page, SubTab page.)
Hierarchy of Objects (as Tree)/Single Object Details Example: Bank, Branch, Account Hierarchy and an
Account
See the individual specifications regarding each of the Master/Detail Template
options listed above. For visual specification of the Master/Detail flow, refer
to the Master/Details Flow Guideline.
Open/Closed Issues
Open Issues
06.04.02
Editorial Review
Review consistency of page titling for all master/detail options including
detail section.
"Focus on"/"View as" Toggle button: need editorial work
"Full Update" clearest button terminology?
Page level navigation for single master object - when no total, should record
# be displayed, or omitted? Usefulness?
05.09.02
"Revert" and "Save" page buttons being considered to be
added to Master/Details page.
Closed Issues
06.20.02
HGrid should not be used as master.
HGrid should not be used in SubTab section.
Selection mechanism to see details of master is finalized. Need explicit column to select details because of complexity and
states of select column. (i.e., active and selected, active only... usability issue if select column is disabled for a
row.)
images to add:
Flow examples (to be in Master/Detail Flows guideline) created.
Finalized detail icons (Update: Display Details Icons are no longer used based
on usability test results. It was found that users tend to use the single-select
radio buttons in the Master Table/HGrid to display details instead of
the using the icons.)
04.14.03
The ability to cache changed values of an updateable master object tested successfully in OA.
The ability to cache changes to all detail level updates within the page tested successfully in OA.
Bookmark
