|Oracle® Fusion Applications Extensibility Guide
11g Release 5 (11.1.5)
Part Number E16691-07
|PDF · Mobi · ePub|
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:
Oracle Fusion applications allow end users to personalize certain pages using the Personalization menu. 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.
If you created a page using CRM Application Composer, then that page is personalizable by default.
For a list of pages that end users can personalize, see the product-specific documentation in Oracle Fusion Applications Help.
Figure 17-1 shows the Personalization menu available in all 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 components. Figure 17-2 shows the Partner Profile application home page in Page Composer, ready for the end user to personalize.
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. For more information about configuring persistence, see the "Allowing User Customizations at Runtime" chapter in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
Before you configure pages to be personalizable, you should be familiar with the Oracle Fusion application architecture that enables customization, as described in Chapter 1, "Customizing and Extending Oracle Fusion Applications." You should also understand the typical workflows for working with customizations, as described in Chapter 2, "Understanding the Customization Development Lifecycle."
You will also need to do the following:
Install Oracle JDeveloper and set up your development environment. For more information, see the "Setting Up Your Development Environment" chapter in the Oracle Fusion Applications Developer's Guide.
Create a customization application workspace. For more information, see Chapter 10, "Using Oracle JDeveloper 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 Section 1.2, "Understanding Customization Layers."
You use JDeveloper to set certain attributes that allow a page to be personalized.
Task: Enable or Disable 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. For instructions, see the "How to Enable End-User Personalizations for a Page" section in the Oracle Fusion Applications Developer's Guide.
Task: Enable 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:
isPersonalizableInComposer property to
For instructions, see the "How to Enable End-User Personalizations for a Page" section in the Oracle Fusion Applications Developer's Guide.
If a page is currently available for personalization, and you do not want it to be, change the property value to
Create a corresponding page definition file, if one does not exist.
For instructions, see the "Ensuring Customizable Pages Have Page Definitions" section in the Oracle Fusion Applications Developer's Guide.
Use Oracle WebCenter Portal components that define areas that are customizable.
For instructions, see the "Making a JSPX Document Editable at Runtime" section in the Oracle Fusion Applications Developer's Guide.
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
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. For more information about what attribute values can persist, see the "Introduction to Allowing User Customizations" section in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
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.
Task: Persist Attribute Values on JSPX Pages
You need to add the attributes you want to persist to the
persist attribute on the component. For more information, see the "Controlling User Customizations in Individual JSF Pages" section in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition). You can set this attribute using Page Composer. For more information about setting attributes on components, see Section 3.3, "Editing Component Properties in Page Composer."