| Page Edit | Version 2.0.0.0 |
||
|
|||
| Description | |
| Use the Page Edit pattern when a user needs to edit a page or page section. |
| Pattern Set Decision Table | |
Page 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 |
No |
Yes |
No |
| Pattern Sample | |
| Page Section Edit |
| The user can update individual sections of a page by clicking the Edit button in the header of the section to be modified. The user will be navigated to an editable page for that section. This is appropriate to use when the initial page's sections contain some but not all of the details associated with each subsection of a page. |
![]() |
| Figure 1. Editing sections of the page |
| Required Screen Elements | ||
| Component Type | Required Components | Customizable or Extendable Components |
| Subheader Button | Edit: Launches a dialog box or navigates to a page where you can edit the selected object. |
NA |
| The user can now update the section information. Clicking the Cancel button discards all changes and returns the user to the previous page. Clicking Save commits all changes made up to that point. Clicking Save and Done commits all changes and returns the user to the previous page. |
![]() |
| Figure 2. Editing section information |
| Required Screen Elements | ||
| Component Type | Required Components | Customizable or Extendable Components |
| Page Title | Use this format: Edit <Section Name> For example: Edit Project Information |
NA |
| Page Buttons | Include these page buttons:
|
NA |
| Form Layout | This pattern provides a container to insert the desired form elements of the transaction. For details, see the Information Entry Form: Basic Form (Page) pattern. | NA |
![]() |
| Figure 3. Page-level Edit button |
| Required Screen Elements | ||
| Component Type | Required Components | Customizable or Extendable Components |
| Page Button | Edit: Navigates the user to a page to edit the selected object. |
NA |
| The user is now able to edit all applicable fields on the page. Clicking Cancel discards all changes and transfers the user to the read-only view of the page. Clicking Submit enters the page into workflow and transfers the user to the read-only view of the page. If the page is not intended for workflow, use a Save button in place of the Submit button. |
![]() |
| Figure 4. Editing the page |
| Required Screen Elements | ||
| Component Type | Required Components | Customizable or Extendable Components |
| Page Title | Use this format: Edit <Object Type>: <Object Name> For example: Edit Personal Information: Max Kelly |
NA |
| Page Buttons | Include these page buttons:
|
NA |
| Form Layout | This pattern provides a container to insert the desired form elements of the transaction. See the Information Entry Form: 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 |