| Create in LOV | Version 2.0.0.0 |
||
|
|||
| Description | |
| The Create in LOV pattern enables users to quickly create an object when they don’t find what they are looking for in a list of values (LOV) choice list. The user enters only minimum requirements. 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 | |
| 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 |
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 | |
This example shows the interaction when using the LOV choice list component.
A dialog box appears for the user to enter minimal information for the new object being created. 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 the users who are creating objects.
The new object is saved and added into the originating cell. Because the user clicked the Save and Close button on the previous screen, the created object is saved in the database even if the user cancels the original transaction. Once saved, it can be accessed through the LOV for other rows.
|
|||||||||||||||||||||
| Related Patterns |
Composition of various types of forms for information entry |
| Related Guidelines | |
| Form Layout | Usage information and design guidance on layout of forms |
| LOV (List of Values) | Usage information and design guidance on the LOV component |
| LOV Considerations | Guideline detailing when to use a choicelist or an LOV choicelist, and information on why LOV input should not be used |
| Page Actions | Usage information and design guidance for buttons at the page level and on secondary windows |
| Save Model | Save Model information/design guidance for Oracle Fusion applications |
| Secondary Windows | Usage information and design guidance on dialog boxes |