Use the Personalize page to personalize the properties of a selected page element.

When you select the Personalize (pen) icon for a page element listed in the "complete" version or "focused" version of the Page Hierarchy Personalization page, the Personalize page appears. The Personalize page varies in appearance depending on the page element you are personalizing, for example, a non-table region versus a table region.

The personalization context is displayed at the top of the page. All the properties that you can personalize for the current page element are listed in the Personalization Properties table. This list of properties is dynamically determined by the page element you select. For example, the properties listed when you personalize a classic table region are different from the properties listed when you personalize a messageStyledText item. In addition, a special Query row appears in the Personalization Properties table when you personalize a table region.

For information on the properties that you can personalize for a particular page element, refer to the Personalization Considerations appendix. You may also refer to the OA Component Reference for a complete list and description of personalizable properties relevant for each region or item style.

Personalization Properties Table

Following is a description of the Personalization Properties table and how you can use the table to personalize your page element.

Global Table Actions

The Personalization Properties table provides the following controls for global table action, which you can select at any time:

• Clear Personalization - clears for a selected personalization level, all personalizations for all properties of the current page element. The poplist displays a list of the personalization levels for the current personalization context. Select a personalization level from the poplist and choose Go to perform this table action.

• Choose Levels Displayed - navigates to the Choose Levels Displayed page, where you can choose to hide or show specific personalization level columns in the Personalization Properties table using the shuttle region provided. Only the personalization levels for the current personalization context are displayed in this page. Use the arrows to move the desired personalization level between the Available Levels and Levels Displayed lists. Choose Apply to save your changes and return to the previous page. Note that personalization levels that are not displayed still affect the final cumulative results of your personalizations.

Original Definition column

The first column in the Personalization Properties table lists the name of each property that you can personalize for the current page element. The next column, Original Definition, lists the read-only base value of that property, as defined in the AK or current MDS repository.

The list of properties varies according to the page element you are personalizing. Refer to the OA Component Reference for a description of the personalizable properties for each region and item style.

Step 1: Update the personalization level columns

Following the Original Definition column, are columns for each of the personalization levels, shown in order of lowest to highest precedence, as defined by your personalization context. These columns are collectively referred to as the personalization level columns. For example, if you select the Site, Organization, and Responsibility levels as your personalization context in the Choose Personalization Context page, the table displays Site, Organization: <Organization Value>, and Responsibility: <Responsibility Value> personalization level columns, so that you can personalize the page element properties at each of these personalization levels.

The fields in these personalization level columns are updateable, so you can enter a personalized value for each property at each personalization level.

The fields in the personalization level columns are used as follows:

• If a field is not personalized, it displays a special value of Inherit, by default. This special value indicates that at that personalization level, the property inherits its value from the personalization level above it (the preceding column).

• You can update a value displayed in a field and if partial page rendering is enabled, the field refreshes to display the new result value. If partial page rendering is disabled, you must select the Go button that renders to refresh the field with this new value.

  Additional Information: The personalized value at that personalization level is not actually applied to the page element itself until you choose the Apply button on the Personalize page.

• If a field contains a personalized value, a Clear Personalization icon is enabled next to the updateable field. Selecting this icon sets the value back to Inherit, so that the property inherits its value from the level above it.

• Note that a blank value is not equivalent to a value of Inherit.

Personalizing EL-supporting Properties

OA Framework supports EL (Expression Language) personalizations on the following properties:

For the Prompt and Maximum Length properties, enter a valid value or EL expression directly into the personalization level column field. For all other EL-supporting properties, select one of the following values from the poplist in the personalization level column:

• Inherit

• Any of the valid values as listed in the table above.

• SPEL (Simplest Possible Expression Language)

If you select SPEL for any of these properties, an additional text box renders for you to enter an EL expression (string), such as ${oa.<viewObject>.<viewAttr>} or ${oa.function.<functionName>}.

If the value for any of the above properties is already an EL expression, the property displays the value SPEL in its poplist and a text box shows the EL expression.

If you select any value other than SPEL in the poplist, the text box is not rendered.

Note the caveats for the following EL-supporting properties:

• If the base value of Rendered is SPEL, the poplist choices for Rendered are false or SPEL.

• If the base value of Required is SPEL, the poplist choices for Required are true or SPEL.

• If the base value of Read Only is SPEL, the poplist choices for Read Only are true or SPEL.

These caveats maintain the integrity of the business logic and security criteria of the page.

When you personalize the value for an EL-supporting property, you may also see one of the following warnings:

• If the base value of Rendered is true or SPEL, and you personalize the value to false or SPEL with a different EL expression, the following warning appears:

  "Setting <property name> to <property value> may hide this item and its children. The application may be inoperable if this item or any of its children is required."

• If you personalize Required to a EL expression other than its original EL expression, the following warning appears:

  "Setting <property name> to <property value> may affect the components that depend on the original SPEL expression or value of this property."

• If you personalize Read Only to true or SPEL, the following warning appears:

  "Setting <property name> to <property value> may make this item read-only. A read-only item is not validated on the browser and is not included in the form submitted to the server."

For more information about EL support and syntax, refer to the EL (Expression Language) Support topic in the Implementing Specific UI Features chapter of the Oracle Application Framework Developer's Guide.

Setting Default Values

You may set a default value for a page element in the Personalization Properties table only if the page element is of one of the following region item styles:

• MessageTextInput (for Datatypes - VarChar, Date, Number)

• MessageLOVInput

• MessageCheckBox

• MessageChoice

• MessageRadioButton

• MessageRadioGroup

The above item styles all have a property called Initial Value that you may personalize. The value you specify for this property determines what an end-user sees as a default value in the page element when the page initially displays. When you set the Initial Value property, be sure the value matches the data type and field-level restrictions of that item page element, otherwise you get an exception. For example, you cannot specify a value of "True" on a date field or set the value to a length of 20 bytes if the field length is 10 bytes.

The default value is effective for both non-view object-mapped and view object-mapped page elements. If a page element is not mapped to a view object, the default value is applied immediately and reflected on the page. If a page element is mapped to a view object, the default value is set on the row and will appear when a user creates a new row. The default value also overrides any default value set in the page element's underlying business object.

In cases where the page element exists beneath a container page element in the Page Hierarchy, the following applies:

• If the item page element is contained beneath a table or Table-In-Table page element, the Initial Value property you set for the item page element becomes effective immediately.

• If the item page element is beneath an advanced table container page element, the Initial Value property you set for the item page element will not be effective.

• The Initial Value property is not supported for an item page element contained beneath an HGrid page element.

For Existing Page Elements Not Mapped to a View Object:

For Page Elements Not Mapped to a View Object, Created From Personalizations:

Step 2: Verify the Value Displayed in the Result/Source column

The last column in the Personalization Properties table is Result/Source. Although you cannot update a value in this column directly, a value in this column is refreshed whenever you update a value for a property at a specific personalization level. This column displays the resulting value of a property if all the personalized values for the current context of personalization levels are applied, as well as the source of that resulting value, which can either be from the personalization level that takes the highest precedence or the Original Definition, if the property has not been updated.

Verify that the value shown in this column is what you want to accomplish when you apply all the personalizations in the current context to the property. Otherwise, update the property value again for the appropriate personalization level, until you get the desired result.

Step 3: Personalize the Data Displayed in a Table Region using the Query Row

If the page element you personalize is a table region, a special row called Query appears at the end of the Personalization Properties table. The Query row displays a Query icon in each personalization level column. When you select the Query icon, you navigate to the Create Query page. You can specify sort information and search criteria on this page to sort and filter the data that displays in the rendered table region when your personalizations are applied. After you create a query and return to the Personalization page, the Query icon in the Query row for that personalization level, changes to a Personalize icon (a pen) to indicate that you can view or author personalize that existing query.

Step 4: Apply Personalizations

Once you finish making changes to the Personalize page, you can choose one of the following buttons:

• Apply - to save your personalizations and return to the Page Layout Personalization page.

• Apply and Personalize Another - to save your personalizations and return to the "focused" Page Hierarchy Personalization page.

• Cancel - to cancel any changes and return to the previous page.