![](https://csdnimg.cn/release/download_crawler_static/1553192/bg12.jpg)
18
levels. They can author personalizations that affect all users, users of a particular locale, users of a particular
organization, users with a particular role and in the context of a particular function. Several levels can apply at
the same time with a predetermined precedence order that yields a very personalized user experience.
Using a combination of OA Extension wizards and built-in personalization screens, several user interface and
business logic extensions are made possible at a minimal cost to development with little-to-no maintenance
cost. In addition, Oracle E-Business Suite customers continue to enjoy the extensibility features offered by
Oracle Flexfields, Oracle Workflow and Business Events.
Consistent and Compelling User Interface
OA Framework offers developers a wide range of user interface components that make the building of
applications into a more assembly process, freeing developers from the repetitive composition of common user
interface constructs. Moreover, OA Framework's declarative approach to building application user interfaces
frees developers from the need to learn a vast array of changing technologies, while offering end users a
consistent application look and experience. OA Framework user interface components range from simple
widgets such as buttons and fields to compound components such as tables-in-tables and hierarchical grids.
User Interface Interactivity
OA Framework is always exploring the technology frontiers to enrich the interactivity of HTML-based user
interfaces. Along those lines, OA Framework provides several features:
1. Partial Page Rendering (PPR)
PPR is a means by which designated parts of a page, rather than the whole page, is refreshed when the
user performs certain actions. OA Framework supports PPR on actions such as: table record-set
navigation, table sorting, table column totaling, adding a row to a table, row-level and cell-level detail
disclosure, toggling the visibility of a Hide/Show component, populating a LOV, subtab navigation, Gantt
chart refreshing and descriptive Flexfields context switching. Moreover, developers can declaratively
enable PPR events on several components. For example, a developer can:
Configure the selection of a poplist to cause related fields to render, be updatable, be required or be
disabled based on the selected value.
Configure the value change of a text field to set related field values (for example, if you set a Supplier
value and tab to the next field, the dependent Supplier Site defaults automatically).
Configure the selection of a master table's record to automatically query and display related rows in a
detail table.
2. Accelerator (Hot) Keys
OA Framework supports mnemonic accelerator keys for selected buttons and enables developers to
assign numeric access keys to product specific user actions.
3. Enhanced Save Model
OA Framework provides a default implementation to warn users when they are about to lose changes such
as when they click on a link that takes them outside the context of the current transaction. Developers can
override the default behavior on a component-by-component basis.
4. Smart Poplist
OA Framework supports a personalizable hybrid between a static poplist and a searchable list of values.
The poplist includes the most popular values a user uses to populate a particular attribute. The user can
personalize the values that show up in the poplist by picking new values from a list of values. Moreover,
the user can personalize the order in which values are listed in the poplist as well as remove less popular
values. This feature is also referred to as a LOV Choicelist.
5. LOV Auto Completion
Lists of values (LOVs) are used when the list of possible values is long and the user may want to conduct
a search before picking a value. In some business scenarios, especially with clerical jobs, the user uses a
small set of values or may find it faster to type a partial value. If the user enters a partial value in a field
that is associated with an LOV, OA Framework conducts a search before bringing up the LOV window. If
the search leads to a unique record, OA Framework completes the rest of value for the unique record and
saves the user from having to use the LOV window.