10 Configuring End-User Personalization

This chapter describes how you can make pages in your Oracle Fusion application personalizable by the end user. Note that mobile applications cannot be personalized by the end user.

This chapter contains the following sections:

10.1 About Configuring End-User Personalization

There are certain runtime changes that an end user can make that persist from session to session, such as changing the width of a column in a table, saving a search parameter, or redesigning an aspect of a page. This type of change is called personalization. Oracle Fusion applications allow end users to personalize certain pages using the Settings and Actions menu, which is accessed by clicking the user's name in the global area. End users can set preferences, edit the current page, and reset the page to the default.

You can control what pages in an application can be personalized, including any new pages you create.

Note:

For a list of pages that end users can personalize, see the product-specific documentation in Oracle Fusion Applications Help.

The following figure shows the Settings and Actions menu available in all Oracle Fusion applications.

Figure 10-1 Settings and Actions Menu in Oracle Fusion Applications

When end users choose the Edit Current Page menu item, Page Composer is opened. From here, they can change certain aspects of the page, such as moving or deleting a component. The following figure shows the a home page in Page Composer, ready for the end user to personalize.

Figure 10-2 Home Page Ready for Personalization

Along with using Page Composer to personalize pages, end users can change certain aspects of components, and then have those changes saved so that they remain each time the user logs in to the application. For example, end users can change the width of columns in many of the tables in Oracle Fusion applications. However, by default, when they change the width, that new width size is saved only for the current session. You can configure that column so that when the user changes the width size, it will remain at that size whenever the user logs back in to the application.

10.2 About Allowing Pages to Be Personalized by End Users in Page Composer

You use JDeveloper to set certain attributes that allow a page to be personalized.

Before you configure pages to be personalizable, you should be familiar with the Oracle Fusion application architecture that enables customization, as described in Customizing and Extending . You should also understand the typical workflows for working with customizations, as described in Understanding the Customization Development Life Cycle.

You will also need to do the following:

Install Oracle JDeveloper and set up your development environment. For more information, see About Installing Customization Tools.
Create a customization application workspace. For more information, see Using for Customizations .
Start JDeveloper in the Oracle Fusion Applications Administrator Customization role.
Select a layer value. When customizing application artifacts in JDeveloper, you first must select the layer and layer value to work in. You use the Customization Context window to make this selection. For more information about customization layers, see About Customization Layers.

10.2.1 About Enabling or Disabling Personalization on Existing Standard Pages

Many pages in Oracle Fusion applications allow personalization by default. You can either disable it or enable it using the isPersonalizableInComposer property on a page. Set the property to true to allow personalizations, set it to false to disallow personalizations.

10.2.2 Enabling Page Composer Personalization on Custom Pages

For end users to be able to use Page Composer to personalize custom pages, you will need to enable your pages to work with Page Composer by doing the following:

Set the isPersonalizableInComposer property to true.

Note:

If a page is currently available for personalization, and you do not want it to be, change the property value to false.
Create a corresponding page definition file, if one does not exist.
Use Oracle WebCenter Portal components that define areas that are customizable.

10.3 About Configuring End-User Personalization for Components

Certain attribute values that affect how an ADF Faces component is displayed can persist to an MDS repository. Application-wide component attribute persistence to an MDS repository is controlled by configuration in the adf-config.xml file. However, customizing this file is not allowed, because doing so is not upgrade-safe. Instead, you can override the application-wide persistence at the page level by setting the persist and dontPersist attributes for component instances.

For example, by default, table column attribute values do not persist. But you can configure a column in a table so that when the user changes the width, reorders columns, or selects a column, those changes will still be in effect when the user logs back in to the application, by adding those attributes to the value of the persist attribute on the column component.

Note:

You cannot change the settings in the adf-config.xml file, because these changes will be overwritten anytime you apply a patch or an upgrade. Therefore, you must change the values on the individual components on a page.

10.3.1 About Persisting Attribute Values on JSPX Pages

You need to add the attributes that you want to persist to the persist attribute on the component.