Oracle Applications Framework (OAF) technology (which includes the Personalization Framework) enables you to configure web pages for distinct audiences. For example, you can create one set of personalizations for a line manager and one set for an employee. Alternatively, you may personalize a self-service page differently for localizations, organizations, and sites. To enable this flexibility, the OA Framework provides two levels of personalization privileges: administrator level and end-user level. Administrators can choose to create personalizations at a number of different levels, for example, at the responsibility, site, or function level. These levels are arranged in a hierarchy where lower level personalizations take precedence over higher level personalizations.
See: Personalization Framework Hierarchy
Users can create personalizations for specific regions and items, for example, a user can hide or display particular columns in a table. A user can also personalize a portlet to hide or display particular information. User personalizations are only seen by the creating user.
Configure web pages for different audiences by creating personalizations at different levels. This list shows the available personalization levels (with an example of a typical personalization):
Administrator Level Personalizations
| Personalization Level | Example |
|---|---|
| Function | Make certain fields read-only for particular functions. |
| Localization | Rename or hide fields for a particular localization. |
| Site | Define a table format for your site. |
| Organization | Add a corporate logo to all web pages used by your organization. |
| Responsibility | Add display or hide a flexfield for a responsibility. |
| Admin-seeded end user | Create default views for your users. |
User Level Personalizations
| Personalization Level | Example |
|---|---|
| Portlet | Personalize the portlet to display news headlines. |
| User | Create personalized views for tables. |
Note: The lower level personalizations, for example, user-level personalizations, take precedence over the higher level personalizations, for example, site-level personalizations.
Not all personalization levels may be available for your self-service application. For example, for iRecruitment, use only site and responsibility levels.
To enable administration-level personalizations, the system administrator sets the personalization profile options for the user in question. The user then logs on to the self-service application and selects a responsibility. If the profile options are set correctly, the user sees the Personalize Region and Personalize Page links on the web page. By clicking on these links, the user can customize the page to the level required.
See: Oracle Application Framework Documentation Resources(My Oracle Support Note # 391554.1)
To enable user-level and portlet personalizations, the system administrator defines region items as user-configurable by using the User Personizable attribute in the Personalization Framework. For user and portlet-level personalizations, this attribute generally applies to tables. If a table can be personalized, you can define views for the table. For example, you can hide or display columns, filter data, select the number of rows to display, and define searches. You can then select the required view from a drop-down list. You can also define a default view.
Enhanced extensibility functionality enables you to add new functionality and override or extend the delivered business logic. For example, you can add new pages to a functional flow or add new items, such as a field, to a delivered page.
See: Oracle Application Framework Documentation Resources(My Oracle Support Note # 391554.1)
Some delivered SSHR functions include function-level customizations which you cannot update or delete. Currently, the following functions include function-level personalizations:
Change Cost Center, Location and Manager
Change Cost Center, Terms and Manager
Change Job
Change Job and Terms
Worker Status Change
Change Worker Status and Terms
Hire/Applicant Hire/Contingent Worker Placement
Termination
Termination with Compensation
Transfer
See: Oracle Application Framework Documentation Resources(My Oracle Support Note # 391554.1)
To personalize one of the above functions, you can either make the personalizations at the site or responsibility level (and override the delivered function-level personalizations) or you can create a copy of the function and make your own personalizations accordingly. However, if you prefer to work with your own custom functions rather than the delivered functions, you should be aware that you will lose any delivered function-level personalizations.
See: Defining Functions for SSHR
See: Function-level Personalizations
The following table lists the configurable profile options used with the Personalization Framework.
| Profile | Configurable Levels | Values | Default |
|---|---|---|---|
| Personalize Self-Service Defn (FND_CUSTOM_OA_DEFINITION) | Site, Responsibility, User | Yes/No | No |
| FND: Personalization Region Link Enabled (FND_PERSONALIZATION_REGION_LINK_ENABLED) | Site, Application, Responsibility, User | Yes/No | No |
| Disable Self-Service Personal (FND_DISABLE_OA_CUSTOMIZATIONS) | Site, Application, User | Yes/No | No |
This profile option enables or disables the global Personalize Page link that appears on each self-service web application page. This profile option must be set to enable personalization at the administrator level. When an administrator displays the Page Hierarchy personalization page from the Personalize Page link, the administrator must navigate to the region or item to be personalized by expanding the hierarchy.
This profile option enables the Personalize Region link above each region in a SSHR web page. You can set this profile option in addition to the Personalize Self-Service Defn profile option. The advantage of setting this profile option is that the Page Hierarchy personalization page focusses on the specific region and the administrator does not have to expand the branches of the hierarchy.
If this system profile option is set to Yes, the configurations you make will not be applied, regardless of the level at which you make the configurations. Only the original definition of each self-service page will be displayed.