Create in a Form Version 2.0.0.0Print this Page
Create Pattern Set
 
Description
Return to Top
The Create in a Form pattern enables the user to create one or more objects by using a form. Multiple objects may be created without going back to the parent page.

The examples on this page address creating in a table but can be applied to the tree table component and tree component as well.
 
Pattern Set Decision Table
Return to Top
  Quick Create Create Inline Create in LOV Create in a
Form
Create a
Duplicate
Create from
Template

Do users need to quickly create an object when they don’t find what they are looking for in a LOV choice list?

Yes

No

Yes

No

No

No

Do users usually create one object and define it completely?

No

Yes

No

Yes

Yes

Yes

What component is used to create the new object?

Regional
Accordion
Panel

Popup

Table

Tree Table
Dialog Box Dialog Box

Page or Train
Dialog Box

Page or Train

Table
Dialog Box

Page
Do users have an immediate need to create a new object without searching? Yes No No No Yes Yes

Do users need to create multiple objects at a time?

No

No

No

Yes

No

No

Do users need to create objects similar to previously created ones (for example, expense reports)?

No

No

No

No

Yes

No

Do users have to create an object from one of the provided templates?

No

No

No

No

No

Yes

Do users need to see the context (base page) when creating the object?

Yes

Yes

Yes

Yes or No
(see pattern
for more
information)
Yes or No
(see pattern
for more
information)

No

Do users need to create an object related to the primary transaction that they have started?

Yes

No

Yes

No

No

No

 
Pattern Subdecision Table
Return to Top

 

Dialog Box Page

Is the number of fields used to create an object suitable for a secondary window?

Yes

No

Are there a large number of fields or is a complex component (table, tabs, trees) needed to create an object?

No

Yes

Is it important for the user to see the context (base page) when creating the object?

Yes

No

 
Pattern Sample
Return to Top

Create in a Dialog Box

Small objects may be presented in the form of a dialog box so that a full page load can be avoided.  

To start the creation process, the user clicks the Create icon button in the toolbar.

Figure 1. The Create icon button
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Table toolbar

Create: Navigates the user to a create dialog box to create a new object

NA

A dialog box appears containing fields to be completed by the user. Users can click the Save and Close button if they want to add only one item, or click the Save and Create Another button to commit the new object to the database and then create another new object without returning to the originating table.

Never hide required fields in a hide or show region, a hidden tab, a drill-down page, and so on. Position all required fields up front so that they are available for users who are creating objects.

Figure 2. The Save and Close and the Save and Create Another buttons on the Create Objective dialog box
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Dialog Box Title

Use this format: Create <Object Type>

For example: Create Objective

NA
Dialog Box Layout

This pattern provides a container to insert the desired form elements of the transaction.

Use the Information Entry Forms decision table to determine whether a dialog box or a page should be used to create the new object.

Form fields may be any standard Web widget (for example, text field, choice list, LOV, radio button, and so on).
Dialog Box Buttons

Include these dialog box buttons:

  • Save and Close: Saves the changes and inserts the new record into the table on the base page. Includes the following actions in a drop-down menu:
    • Save and Create Another: Commits the transaction and inserts the new record into the table on the base page. Resets the form field values for the user to enter a new record.
      See Save Model guidelines to select the appropriate button label.
  • Cancel: Cancels the transaction and closes the window.
See Page Actions guidelines for button labels for different save scenarios (for example, create another).

The newly created object appears in the first row of the originating table on the page behind the dialog box.

Figure 3. Newly created object in the first row of the originating table
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Table

For newly added rows, include a changed item indicator on the row header.

The added row should always be visible on screen. Placement of the newly added rows is dependant on what (if any) row is selected. For specific information, see the Table Common Actions guideline.

NA

When users have finished creating one or more new objects, they can click the Save and Close button to close the dialog box and view all newly created objects in the originating table.

Figure 4. Viewing all newly created rows in the originiating table

Create in a Page

Present as forms in a page or guided process those objects that are too large to fit in a dialog box. The following examples demonstrate creating an object in a single form. See the Information Entry Form pattern decision table to determine if you should use a guided process or a single page form.

To start the creation process, the user clicks the Create icon button from the toolbar.

Figure 5. Clicking the Create icon button
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Table toolbar

Create (icon button): Navigates the user to a create dialog box or page to create a new object

NA

A new page appears containing fields to be completed by the user. Users can click the Save and Close button if they want to add only one item or click the Save and Create Another button to commit the new object to the database and then create another one.

Never hide required fields in a hide or show region, a hidden tab, a drill-down page, and so on. Position all required fields so they are visible to users who are creating objects.

Figure 6. Click Save and Close to add only one item or Save and Create Another to commit the new object to the database and create another
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Page Title

Use this format: Create <Object Type>

For example: Edit Personal Information

NA
Page Buttons

Include these page buttons:

  • Save and Close: Commits the transaction, returns the user to the appropriate destination page, and displays a confirmation message. You can use a button drop-down to provide multiple options. See Save Model guidelines to select the appropriate button label.
  • Cancel: Cancels the transaction and returns the user to the previous page.
  • See Save Model guidelines for button labels for different save scenarios (for example, create another).
  • See Confirmation Message design pattern for details about the use of inline or dialog box-based messages.
Form Layout This pattern provides a container to insert the desired form elements of the transaction. Product teams can use an Information Entry form (page) or a guided process to create the object. To determine which is appropriate, see the Information Entry Form pattern set decision table.

When users have finished creating one or more new objects, they can click the Save and Close button to close the dialog box and view all newly created objects in the originating table (on the originating page).

Figure 7. Viewing all newly created objects in the originating table (on the originating page)
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Table

Include a changed item indicator on the row header of newly added rows.

The added row should always be visible on screen. Placement of the newly added rows is dependant on what (if any) row is selected. For specific information, see the Table Common Actions guideline.

NA
 
Related Patterns
Return to Top

Information Entry Forms

Composition of various types of forms for information entry

Guided Processes

Method of guiding a user through a series of related transactional pages

 
Related Guidelines
Return to Top
Form Layout Usage information and design guidance on layout of forms
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 Usage information and design guidance on the toolbar component
Table Overview Overview of the table component and links to other table guidelines
Toolbar Usage information and design guidance on the toolbar component
Tree Table Usage information and design guidance on the tree table component
Tree Usage information and design guidance on the tree component
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights