| Information Entry Forms Pattern Set |
| Basic Form (Page) | |||
|
|||
| Description | |
| Use the Basic Form (Page) pattern to present a simple data entry form where all fields are contained on a single page. This pattern is appropriate when the number of fields is too large to display within a table without horizontal scrolling. |
| Pattern Set Decision Table | |
Basic Form (Page) |
||||
What is the user type? |
Casual |
Casual |
Experienced |
Any |
How many steps does it take to complete the transaction including a review page? |
1 |
1-2 |
1-2 |
2+ |
How many editable fields does the page contain? |
~10 or less |
~ 30 or less |
~ 40 or less |
40+ |
How many sections are needed to logically group the fields in the form? |
Usually 1 to 2 |
Usually 1 to 4 |
Usually 3 to 7 |
7+ |
Does the user-entered data need to be persistently shown (that is, for comparison, context, or sense of completion)? |
Yes |
Yes |
No |
No |
Is the object being created or edited large, complex, or hierarchical (requires tabs, tree tables, master/detail)? |
No |
No |
Yes |
Maybe |
Note: The number of fields and sections are recommendations only for optimum usability and are not a coding restriction. |
| Key Considerations | |
| The same look and feel for information entry forms can be used to show read-only details if a user does not have privileges to perform updates to the form. Guided processes are an exception to this because they are used exclusively for entering data. The review step of a guided process is commonly displayed as a single form in read-only format. |
| Pattern Sample | |
| In page view, all form fields are contained within a single page. The pages can be divided into groups of related fields, which makes the page easier to read. |
 |
| Figure 1. Basic page divided into groups of related fields |
| Required Screen Elements | ||
| Component Type | Required Components | Customizable or Extendable Components |
| Page Title | Use this format: <Action> <Object Type> |
NA |
| Page Buttons |
|
NA |
| Layout | Use one-, two-, or three-column layouts for label or data pairs. The column layout selection is based on the number of form fields in the section. Align columns across sections. |
NA |
| Related Guidelines | |
| Form Layout | Guidelines for organizing content in a form |
| 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 |
| Tabs | The primary user interface (UI) method used to organize large amounts of content in a transaction |
