Information Entry Forms Pattern Set Version 2.0.0.0Print this Page
 
 
Description
Return to Top
Information entry forms require the user to provide information into a preformatted presentation (form).
 
Patterns Contained in This Set
Return to Top
Basic Form (Dialog Box) A form presented as a dialog box
Basic Form (Page) A form presented as a single page
Complex Form A form presented as a single page using data entry tables in combination with other containers
Guided Process Pattern Set A form presented as multiple pages in the form of a train or guide
 
Pattern Set Decision Table
Return to Top
 
Basic Form
(Dialog Box)
Basic Form
(Page)
Complex Form
Guided Process Pattern Set

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
Return to Top
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.
 
Related Patterns
Return to Top
Guided Processes

This pattern set groups related functions or pages to guide users through complex or infrequently performed tasks and presents complex transactions and multipart processes in smaller and more manageable sequences of individual steps.

Editing Objects

This pattern is used to set one or more of the same attributes on multiple objects. Instead of needing to navigate to each object's details page to set the same attribute or to set the attribute for multiple rows within a table, the Editing Objects pattern enables users to select the desired objects from the object list and set one or more attributes in a single step.

 
Related Guidelines
Return to Top
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
Secondary Windows Guidelines for dialog boxes
Tabs The primary user interface (UI) method used to organize large amounts of content in a transaction
Train Used to group related functions across two or more pages; guided processes with three or more steps (commonly referred to as "wizards") have a distinctive look and a range of options
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights