FusionGPS: Design Patterns: Editing Objects Pattern Set: Table Row Edit (Page)

Table Row Edit (Page)

Version 2.0.0.0

Editing Objects Pattern Set


Description

Use the Table Row Edit (Page) pattern when a user needs to edit rows of a table or tree table, and the information to be edited will not fit within a dialog box.


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

Single Selection Table Edit

The user selects a record (table or tree table row) and either clicks the Edit button in the table or tree table toolbar or right-clicks the row to select Edit from the context menu.

Figure 1. Selecting a single record to edit

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Table or Tree Table	A table or tree table is used to display the list of objects.	NA
Toolbar	Edit: Icon button navigates the user into the edit object form.	NA
Contextual Menu	Edit: Menu option navigates the user into the edit object form.	NA

Users navigate to a form where they can edit the record data. Clicking the Cancel button closes all changes and returns users to the previous page. Clicking the Save button commits the changes, and clicking the Save and Return button commits the changes and returns users to the previous page.

Figure 2. Editing data for the selected record

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Page Title	Use this format: Edit <Object Type>: <Object Name> For example: Edit Appraisal: Joe Smith Note that if the object name itself is an editable attribute, the change will not be reflected in the page title; it is applied once the page is saved.	NA
Page Buttons	Include these page buttons: Save (optional): Saves any changes and remains on the current page for the user to continue editing. Save and Close, Publish, Submit, or Finish: Commits the transaction, returns the user to the appropriate destination page, and displays a confirmation message. (see Save Model guidelines to select the appropriate button label). Cancel: Cancels the transaction and returns the user to the previous page.	See the Confirmation Message design pattern for details about the use of inline or dialog box-based messages.
Layout	This pattern provides a container to insert the desired form elements of the transaction. See the Information Entry Form: Basic Form (Dialog Box) or Basic Form (Page) pattern for details.	NA

Multiselect Table Edit (Page)

Users first select objects, such as rows of a table, then click the Edit icon button (or right-click and select Edit from the contextual menu).

Figure 3. Selecting multiple objects to edit

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Table or Tree Table	A table or tree table is used to display the list of objects.	NA
Toolbar	Edit: This icon button navigates the user into the edit object form.	NA
Contextual Menu	Edit: This menu option navigates the user into the edit object form.	NA

Users are presented with a page where they can choose values to apply to the selected records. Clicking the Save button commits the changes, and clicking the Save and Return button commits the changes and returns users to the previous page.

Figure 4. Choosing values to apply to the selected records

Required Screen Elements
Component Type	Required Components	Customizable or Extendable Components
Page Title	Use this format: Edit <Object Type> For example: Edit Employee Information Note that specific object names are not listed in the page title because there are multiple objects in this scenario.	NA
Page Buttons	Include these page buttons: Save (optional): Saves any changes and remains in the current page for the user to continue editing. Save and Close, Publish, Submit, or Finish: Commits the transaction, returns the user to the appropriate destination page, and displays a confirmation message. (see Save Model guidelines to select the appropriate button label). Cancel: Cancels the transaction and returns the user to the previous page.	See Confirmation Message design pattern for details about the use of inline or dialog box-based messages.
Sub header Title	Show selected objects in a region at the top of the page. Use this format: Selected <Object Names> For example: Selected Employees	NA
Table	Show selected objects in a table.	NA
Table Toolbar	Remove (button): Clicking this button enables users to remove the selected object from the table.	NA
Layout	This pattern provides a container to insert the desired form elements of the transaction. See the Information Entry Form: Basic Form (Dialog Box) or Basic Form (Page) pattern for details.	NA


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