5.7 Managing User Interface Defaults (UI Defaults)
Managing user interface (UI) defaults enables you to assign default UI properties, create default wizard, modify the table UI defaults, add new attributes, and export the UI defaults.
- About UI Defaults
UI Defaults enable you to assign default UI properties for regions and items. - Creating UI Defaults for a Table
If no defaults have been created for a table, use the Table Dictionary Create Defaults wizard to automatically generate defaults based on the database table and column definitions. After the initial defaults are created, you can modify the individual default values. - Modifying Table UI Defaults
Learn how to modify existing table UI defaults. - Creating UI Attributes
Use the Attribute Dictionary to define and add new attributes. - Modifying UI Attributes
Modify existing UI attributes on the Grid Edit page or by selecting a specific column. - Exporting and Importing UI Defaults
Export UI defaults in the same way you export any related application file.
Parent topic: Using SQL Workshop Utilities
5.7.1 About UI Defaults
UI Defaults enable you to assign default UI properties for regions and items.
This wizard enables you to specify whether you want to use UI Defaults if they exist. When you create a form or report using a wizard, the wizard uses this information to create default values for region and item properties. Utilizing UI defaults can save valuable development time and has the added benefit of providing consistency across multiple pages in an application. UI Defaults are divided into two categories: the Table Dictionary and the Attribute Dictionary.
-
The Table Dictionary enables you to specify defaults for tables and columns that are initialized from the database definition.
-
The Attribute Dictionary enables you to create defaults based on attribute or column names, thus being usable across all tables. Attribute definitions can also have synonyms, enabling more than one attribute to share a common definition.
When you use UI Defaults during creation of pages and regions, the Table Dictionary takes priority over the Attribute Dictionary. If a table and column combination exists, that is used rather than an attribute definition of the same name. This can be useful, for example, when you want to have a specific label or Help text for the CREATED_BY
column in the emp
table but then use more generic defaults for CREATED_BY
in another table.
Parent topic: Managing User Interface Defaults (UI Defaults)
5.7.2 Creating UI Defaults for a Table
If no defaults have been created for a table, use the Table Dictionary Create Defaults wizard to automatically generate defaults based on the database table and column definitions. After the initial defaults are created, you can modify the individual default values.
To create the initial UI defaults for tables:
Parent topic: Managing User Interface Defaults (UI Defaults)
5.7.3 Modifying Table UI Defaults
Learn how to modify existing table UI defaults.
To modify existing table defaults:
Parent topic: Managing User Interface Defaults (UI Defaults)
5.7.4 Creating UI Attributes
Use the Attribute Dictionary to define and add new attributes.
To create an attribute:
Parent topic: Managing User Interface Defaults (UI Defaults)
5.7.5 Modifying UI Attributes
Modify existing UI attributes on the Grid Edit page or by selecting a specific column.
To modify an existing attribute:
Parent topic: Managing User Interface Defaults (UI Defaults)
5.7.6 Exporting and Importing UI Defaults
Export UI defaults in the same way you export any related application file.
To export UI defaults from one development instance to another:
- Export the UI defaults using the Export User Interface Defaults utility.
- Import the exported file into the target Oracle APEX instance.
- Install the exported file from Export Repository.
When you export UI defaults, all UI defaults for the selected schema are exported to a single script. The file contains an API call to create table hints by making calls to the application PL/SQL API. You can use this file to import UI defaults to another database and Oracle APEX instance.
See Also:
In Oracle APEX App Builder User’s GuideParent topic: Managing User Interface Defaults (UI Defaults)