Create from Template Version 2.0.0.0Print this Page
Create Pattern Set
 
Description
Return to Top
Use the Create from Template pattern to enable users to create one or more objects from an existing template.

The examples on this page address creating in a table but can also be applied to the tree table component and tree component.
 
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 Sample
Return to Top

Create from Template

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

Figure 1. Starting the creation process by clicking the Create icon button
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Table Toolbar Create: Navigates the user into the create object form NA

 

A new page appears that provides a choice list or list of values (LOV) where users can select a template.

  • Users may also select a blank template that enables them to complete all fields. Templates may prepopulate certain fields.
  • Other fields may be read-only; users cannot modify these fields.
  • 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 and available
  • for users who are creating objects.Users can override data in editable fields.
  • When a user changes the template, the form of the page is regenerated using partial page refresh.
  • Different templates can have different detail fields.

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 without returning to the originating table.

Figure 2. Choose to add only one item or commit the new object to the database and create another
Required Screen Elements
Component Type Required Components Customizable or
Extendable Components
Page or Dialog Box Title

Use this format: Create <Object Type>

For example: Create Contact Group

NA
Single-Select LOV Choice List Use Choose Template for the prompt format. NA
Layout This pattern provides a container to insert the desired form elements of the transaction. See the Information Entry Form Basic Form (Dialog Box) or Basic Form (Page) pattern for details. NA
Page Buttons

Include these page buttons:

  • Save (optional): Saves any changes and remains on the current page for the user to continue editing.
  • Save and Close: Commits the transaction, returns the user to the previous page, and displays a confirmation message. A button drop-down can be used to provide multiple options, such as Save and Create Another, which commits the transaction and presents the user with a new blank form based on the same template.
  • Cancel: Cancels the transaction and returns the user to the previous page.

See Save Model guidelines to select the appropriate button label.

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 (on the originating page).

Figure 3. 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 for 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
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