This appendix covers the following topics:
This appendix lists the personalization considerations, if any, for the various types of elements (regions or items) on a page.
Warning: This document does not list all personalizable properties for a page region or item. Instead, it lists key considerations that we hope will facilitate your personalization efforts. Please refer to the OA Extension Component Reference, My Oracle Support Knowledge Document 1315505.1, for a complete list of properties that may be personalized for a region or item.
The following properties of the accordion layout are personalizable:
Rendered
Height
Width
Disclose One
The following properties for the individual accordion component are personalizable:
Rendered
Disabled
Prompt
Border Width
Height
Disclosed
Please note the following restrictions on personalizing attachments-enabled pages:
Personalization of the actual Attachments table region that renders on a page is not supported, with the exception that administrators can reorder the columns within the table.
Administrators can personalize the children (columns) of the Attachments table, with the exception of the File Name, Update and Delete columns.
Administrators can also personalize all aspects of the Search region on an Attachments page, with the exception of its Go submit button.
Administrators may personalize the value of the Inline Attachment Enabled property of an Attachment region. The personalized value of this property takes precedence over the value of this property set at design time.
If inline attachment links are enabled (with a messageInlineAttachment item style), an administrator can also personalize the Links Displayed property of this item.
An administrator can create a new attachment link item for a region in the Create Item page of the Personalization UI by selecting the Create Item icon in the Page Hierarchy Personalization page.
Administrators can update, create or delete non-Oracle seeded entity, primary key and category maps for an attachment item using the Personalization UI. In the Page Hierarchy Personalization page, locate the attachment item you want to personalize in the page hierarchy, then expand the entityMappings to update, create or delete entity maps and primary keys. You can also expand the categoryMappings entity in the hierarchy to update, create or delete categoryMaps. Note that to create a new custom categoryMap, the new custom attachment category must first be defined in the FND_DOCUMENT_CATEGORIES table. When you create a new category, you will also be able to personalize the Secure property, to secure the category with your defined Application Security rules.
As of Release 12.2.6, administrators may personalize the values of the Default Attachment Type, Enable Text Attachment, Enable File Attachment, and Enable URL Attachment properties of an Attachment region. If the values of these properties are set programmatically, then the programmatic value takes precedence over the personalized value.
Warning: You are not allowed to restrict (disable) the attachment type that you previously set as the default attachment type. If you attempt to create such a faulty configuration, the default attachment type, which is considered enabled, will appear with a relevant developer mode exception that looks as follows: "Developer Mode Error : The type [attach_type] selected as Default Attachment Type for attachment bean [bean_name] is disabled. However, to show the Default Attachment Type, it has now been set as enabled."
Auto-repeating layout regions may be personalized at any administrative level, but not at the end-user level.
Web bean attributes implemented as bound values are not personalizable.
The Text property of the inContextBranding component is system administrator personalizable.
The User Function Name used for the basic (non-contextual) regular brand is personalizable; the corresponding image is not.
Action/Navigation buttons are personalizable at the Admin-level.
Global buttons cannot be personalized.
As an administrator, you can use the Personalize page in the OA Personalization Framework to personalize the following graphTable properties:
Aggregate Function
Allow Combination Graph
Data Axis Label
Data Axis scale
Display Data Markers
Display Secondary Y-Axis
Graph Type
Rendered
Secondary Data Axis Label
Size
Title
X-Axis Label
As an administrator, you can use the Personalize page in the OA Personalization Framework to personalize the following Graph data properties:
Prompt
Secondary Axis
As an administrator, you can use the Personalize page in the OA Personalization Framework to personalize the following Gantt chart properties:
Show Bubble Text
Show Dependency Lines
Axis Major Scale
Show Current Date
Auto Scale
Axis Minor Scale
Render Description Columns
Enable Interactive Gantt
This property is user personalizable.
If an interactive Gantt chart is enabled, the custom tooltip feature can be enabled as well. The Custom Tip Attribute List and Custom Tip Label List properties are user personalizable.
Firm View Attribute
Use Classic Chart
You can also personalize properties that are inherent to HGrids.
Concurrent Processing pages are personalizable at the Admin level.
You should not personalize a configurable page by accessing it from the Functional Administrator Responsibility. Your configurable page might contain controller code that is dependent on certain parameters that are available only when the page itself is launched from its intended flow, and the page might fail with unexpected errors.
You can tell that your page is a configurable page if you attempt to access it from the Functional Administrator home page and the Page Layout Personalization page appears. You should instead run the actual page in Oracle E-Business Suite and initiate the Personalization UI from the global Personalize Page link, on the rendered page. You can then personalize it using the Page Layout Personalization page.
Note: This restriction applies only to configurable pages whose flexibleLayout and flexibleContent regions are defined in their base metadata. This restriction does not apply to pages that start out as non-configurable, but are later personalized by administrators who add new flexibleLayout and flexibleContent regions using the Create Item page in the Personalization UI. The Functional Administrator Responsibility always displays the Page Hierarchy Personalization page when it launches personalizations for these pages that have been made configurable via prior personalizations.
If the controller of your configurable page depends on URL parameters and you select the Personalize Page link to personalize the configurable page, the Page Layout Personalization page will retain those URL parameters. As a result, when you select the Return to Application link to return to the configurable page, the URL parameters will be made available again to the configurable page's controller.
Custom HTML is not personalizable.
The Date Picker displayed in a secondary window cannot be personalized.
The inline Date Picker cannot be personalized.
The Destination Function can be personalized, but the event cannot be (since a fireAction event cannot be configured in the Personalization module).
Dialog pages cannot be personalized.
You can not personalize a table content Switcher, but you can personalize the items nested in the table content Switcher, if that item is shown when you personalize the region.
If you want to allow personalizations on a descriptive flexfield based on a specific localization, and you do not want to show the descriptive flexfield context poplist, then you need to explicitly call setContextListRendered(false) on the descriptive flex bean.
The key flexfield Search page does not support saving search criteria for flexfield segments in personalized saved searches.
Web beans that launch Oracle E-Business Suite forms from OA Framework pages are not personalizable.
When the Rendered property is set to True for a formValue item, the Rendered property for the formValue item will not be personalizable. That is, you cannot hide a formValue item on a page as it will cause problems in the page.
You can personalize a HGrid to a limited extent by hiding/showing columns, freezing the position of a set of columns, or renaming column labels.
Hide/Show web beans cannot be personalized.
You can personalize the SubTabLayout region under the Hide/Show subtab layout.
You can not create a Hide/Show subtab layout region using the Create Item page since it is a special named child of the page layout region.
For the Release 12.2.4 and above Simple Home page, the text in the Announcement section may be personalized.
For Release 12.2.6 and above, an infotile is admin-personalizable.
The Selected Layer ID and Layer Selection Event properties of a layered layout are admin-personalizable. The Title of a layer in a layered layout is also admin-personalizable.
"Personalize..." region links were not displayed prior to Release 12.0.4 on LOV modal windows. To personalize an LOV table prior to Release 12.0.4, use the "Personalize Page" link on the top of the page containing the LOV. Tables in internal LOVs (in-line LOVs) can be personalized directly from the Personalization Hierarchy page. To personalize a table in an external LOV, use the "Choose Context" page to select the shared LOV region.
The following components of the Query Bean are personalizable at the Admin-level.
Enable List Search:
This property along with the profile option FND_ENABLE_LIST_SEARCH controls the query bean rendering in List Search mode.
Enable Auto Reordering Of Criteria Items:
When the value of this attribute is null, if the query bean has simple and advanced panels and the default panel is customize or simple then in rendering the filters area in the List Search, the criteria will be automatically reordered. A value of False will be honored only if the query bean has simple and advanced panels, and the default panel is customize or simple.
Hide Match Condition
Enable Quick Search
Enable Keyword Search
Quick Search Field Identifier:
An administrator can use this attribute to change the quick search field's criteria item from the shipped default quick search criteria item to a new item.
Everything else is not personalizable.
Breadcrumbs are not directly personalizable. If the pageLayout Title property value is personalized, the breadcrumb link text will reflect this change (assuming the breadcrumb link text is not set programmatically).
The Masonry layout allows personalization of the Width, Height, Rows, and Columns properties. Masonry tiles allow personalization of Rendered, row span, and column span properties.
You may use the Create Item page or Update Item page to create a new or update an existing menu component, respectively.
Multiselect LOVs cannot be personalized.
Note: The Page Contents Bottom Line ("Ski") is obsolete as of Release 12.
If you wish to personalize the URL that points to the Privacy Statement for a page that displays a standard Copyright and Privacy (that is, its Auto Footer property is set to true), set the Scope to OA Footer, in the Choose Personalization Context page of the Personalization UI.
If you wish to personalize the URL that points to the Privacy Statement for a page that displays a custom Copyright and Privacy (that is, its Auto Footer property is set to false), set the Scope to Page in the Choose Personalization Context page of the Personalization UI. In the following Page Hierarchy Personalization page , identify and personalize the Privacy page element.
The Rendered, Splitter Bar Offset Position, Collapsed, Orientation, Collapsible Panel, First Panel Border, and Second Panel Border properties of the panel splitter are admin-personalizable.
Pop-ups are admin-personalizable.
Printable pages are not personalizable.
A processing page is not personalizable.
Query By Example and Query By Example Case Sensitive Search are not personalizable.
You may use the Create Item page or Update Item page to create a new or update an existing rating bar component, respectively.
The Record History Enabled property may be personalized at the Admin-level to enable record history on a header, classic table or advanced table region. After personalizing this property to true, be sure to set the profile option FND: Record History Enabled to Yes to enable record history on the region.
The Enable Column Reorder, Enable Column Resize, Enable Detach, Enable Horizontal Scroll, Enable Column Hide Show, Row Navigation Policy, and Enable Column Freeze properties may be personalized at the Admin-level to enable or disable rich interactions.
The Rich Text Editor properties, Read Only and Rendered, may be personalized.
The Warn About Changes property is not personalizable.
The properties of a shuttle region may be personalized at the Admin level but not at the end-user level.
If the Required property of a messageTextInput (text input) item is set to yes, its Read Only property does not appear on the Personalize page.
If the Required property of a messageChoice (poplist) item is set to yes, its Read Only property does not appear on the Personalize page.
There is no personalization support for a dynamic poplist because it can only be implemented programmatically.
As of Release 12.2.4, you may use the Create Item page or Update Item page to create a new or update an existing spin box component, respectively.
Limited properties of SubTabLayout, such as Rendered, Orientation and Display Type may be personalized at the Admin level but not at the end-user level.
You can not personalize Application Switchers.
You can not personalize Context Switchers.
You can not personalize a table content Switcher, but you can personalize the items nested in the table content Switcher, if that item is shown when you personalize the region.
For the columns in an advanced table to be user personalizable, the User Personalization property must be set to true for the following components in the Advanced Table: the advancedTable region itself, its column containers, its sortableHeaders, and its column leaf items.
As an administrator, you can use the Admin-level Personalization UI to hide or show a column in an advanced table (if it is not defined under a query region) by setting the column's Rendered property to false or true, respectively. This automatically hides or shows the column and its item. If the advanced table is defined under a query region, however, you must set both the column's and the item's Rendered properties to false or true.
Currently, end-users cannot reorder the columns in an advanced table, when creating a personalized saved search, as the arrow buttons in the shuttle, used to reorder the columns, do not render.
For Admin-level personalizations, columns and column groups can only be reordered within their region boundary. For example, the column or column group child of a given column group region may be reordered within that given column group region. However, the column or column group child from that given column group may not be moved to another column group region, as that would cross over the region boundaries.
If you set the profile FND: Enable Rich Table Interactions to True, OA Framework creates a user saved search of any rich table modifications you make. The user saved search always takes highest precedence when OA Framework displays the table. As a result, if you reorder a table using the admin Personalization Framework UI, the saved admin personalization will not take effect. If you wish to display the table columns as ordered according to your admin personalization, you must set the profile FND: Enable Rich Table Interactions to False.
Row headers are not personalizable.
As of Release 12.2, the Row Header Col property of an advanced table may be personalized to set a column as a Row Header for screen reader accessibility.
The prompt or label of a column or column group may be personalized. Modify the Prompt property of the Sortable Header component that resides under the columnHeader for that column or column group.
Column headers cannot be reordered at the user level but can be at the admin level.
When an end-user creates a personalized saved search of the advanced table region, the Available Columns/Columns Displayed shuttle in the Create/Update/Duplicate page appends the complete hierarchy of columnGroup names, if any are defined as the parent of the column, to the actual column name listed. This ensures that a user hides/shows the correct column, especially in the case where multiple columns of the same name may exist within different columnGroups.
When creating a personalized saved search of an advanced table, if you hide all the columns under a columnGroup, the columnGroup itself is automatically hidden.
An advanced table with row span is not personalizable.
Not applicable.
The label of the Select column cannot be changed in accordance with the BLAF guidelines on the Oracle Technology Network (OTN).
Reordering of the Select column is not supported, as the Select column should always be the first column, in accordance with the BLAF guidelines on OTN.
Selectors can be hidden or shown.
The Control bar button label may be updated.
A tableActions is a named child of the advanced table, and hence the actual table action components are regions or items. These children of table actions can be individually personalized at an admin level, but not at the user level.
In an end-user personalizable page, if you set sorting on an advanced table column that contains a nested region using the Create Saved Search page, but find that the change is not taking effect on the table, it is likely that the Sort By View Attribute property on that column was not set by the developer. If this is the case, the personalization administrator would have to set the Sort By View Attribute property on that column first, using the Admin Personalization UI.
If the table has Sort Allowed property set to ascending or descending through Personalizations for a certain column, then the Initial Sort Sequence needs to be set to first, second, third on that column.
The label or prompt of the Add Another Row button, and the number of rows to add, can be personalized at the Admin-level only.
You can not personalize the Total footer row (which displays the Recalculate button) of an advanced table using OA Personalization Framework. However, if you declaratively implement an advanced table region that contains a total named child, the advanced table can be personalized at the admin level or user level to calculate a total or disable totalling for any of its numeric data columns.
You can not enable totalling for the first column in a table. If you attempt to personalize the first column of an advanced table by setting the Total Value property to True in the Personalize page, it is simply ignored. To total the contents of that first column, you must use the OA Personalization Framework to reorder the column within the advanced table so that it is no longer the first column in the table, then set the Total Value property to True for that column.
An advanced table with Detail Disclosure can be personalized at the admin level but not at the user level.
Advanced Table-in-Advanced Table:
An Advanced Table-in-Advanced Table can be personalized at the admin level but not at the user level.
The full table formatting properties can be personalized at the admin level but not at the user level.
The column formatting properties can be personalized at the admin level but not at the user level.
The row formatting properties can be personalized at the admin level but not at the user level.
The column header formatting properties can be personalized at the admin level but not at the user level.
Reordering Columns:
If you reorder the columns in a table, such that a checkbox or radio button item results in the first column, the checkbox or radio button in that first column will assume the behavior of a Selection checkbox or radio button, respectively.
For more information about Selection checkboxes, refer to the Classic Tables > Table Features and Components > Selection and Control Bar section in the Implementing Specific UI Features chapter of the Oracle Application Framework Developer's Guide.
If you set the profile FND: Enable Rich Table Interactions to True, OA Framework creates a user saved search of any rich table modifications you make. The user saved search always takes highest precedence when OA Framework displays the table. As a result, if you reorder a table using the admin Personalization Framework UI, the saved admin personalization will not take effect. If you wish to display the table columns as ordered according to your admin personalization, you must set the profile FND: Enable Rich Table Interactions to False.
Row headers are not personalizable.
As of Release 12.2, the Row Header Col property of a Classic Table may be personalized to identify a column as the Row Header for screen reader accessibility.
The column header of a column that contains a nested region (such as a flowLayout region) cannot be personalized at the Admin or User level. The column itself, however, can still be hidden or reordered at any level.
Not applicable.
The label of the Select column cannot be changed in accordance with the BLAF guidelines on the Oracle Technology Network (OTN).
Reordering of the Select column is not supported, as the Select column should always be the first column, in accordance with the BLAF guidelines on OTN.
If you reorder the columns in a table, such that a checkbox or radio button item results in the first column, the checkbox or radio button in that first column will assume the behavior of a Selection checkbox or radio button, respectively.
Selectors can be hidden or shown.
The Control bar button label may be updated.
A tableActions is a named child of the table, and hence the actual table action components are regions or items. These children of table actions can be individually personalized at an admin level, but not at the user-level.
In an end-user personalizable page, if you set sorting on a nested region column in a table using the Create Saved Search page, but find that the change is not taking effect on the table, it is likely that the Sort By View Attribute property on that column was not set by the developer. If this is the case, the personalization administrator would have to set the Sort By View Attribute property on that column first, using the Personalize Page.
If the table has Sort Allowed property set to ascending or descending through Personalizations for a certain column, then the Initial Sort Sequence needs to be set to first, second, third on that column.
There is currently no support for personalizing the Add Another Row button in the table footer.
Users can calculate a total for a table column using OA Personalization Framework. See Personalize Page for additional information on how to personalize a table to calculate a total for a column with numeric content.
There are no restrictions for Admin-level personalizations of regions or items under a detail disclosure, however, there is no support for user-level personalizations of the same.
There are no restrictions for Admin-level personalizations of regions or items in the inner table, however, there is no support for user-level personalizations of the same.
There are no restrictions for personalizing full table formatting, column formatting, row formatting, or column header/row header formatting.
Tree components are not personalizable.
As the Oracle Workflow Worklist is a shared region, personalizing it at the site, location or organization level affects all pages/applications that contain the region. If you want to limit the scope of your changes you should create function or responsibility-level personalizations as appropriate. It is also possible to create a page-specific personalization for shared regions. See Per Instance versus Global Personalizations for additional information.