Complex Form Version this Page
Information Entry Forms Pattern Set
Return to Top
The Complex Form pattern combines many comonents on a page, such as forms, tables and arranges them into sections of page represented by tabs and subheaders. It allows for more information density than a basic form.
Pattern Set Decision Table
Return to Top
Basic Form
(Dialog Box)
Basic Form
Complex Form
Guided Process Pattern Set

What is the user type?





How many steps does it take to complete the transaction including a review page?





How many editable fields does the page contain?

~10 or less

~ 30 or less

~ 40 or less


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


Does the user-entered data need to be persistently shown (that is, for comparison, context, or sense of completion)?





Is the object being created or edited large, complex, or hierarchical (requires tabs, tree tables, master/detail)?





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.
Pattern Sample
Return to Top
Figure 1. Example of a complex form
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Page Title

Use this format: <Action> <Object Type>

For example: Edit Employee Information

Create, Edit, and other pages actions can be used in the page title.

Page Buttons
  • Save: Saves changes and keeps user in the same page so that they can continue editing
  • Save and Close, Publish, Submit, or Finish: Commits the transaction, returns the user to the previous 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
  • 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.
  • Headers: Organize fields into logical groupings within the page.

Use multidimensional components and layouts, such as subtabs, master/detail pages, tables, and tree tables, to organize complex data.

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 guidelines Save Model information and design guidance for Oracle Fusion applications
Tabs The primary user interface (UI) method to organize large amounts of content in a transaction
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights