Administrative-Level Personalization User Interface

This chapter covers the following topics:

Overview

This chapter provides detailed descriptions of all the individual pages in the user interface for Admin-level personalizations.

Focused Page Hierarchy Personalization Page

You may launch the "focused" version of the Page Hierarchy Personalization page by selecting the Personalize (pen) icon for a boxed region from the Page Layout Personalization page. The Personalization Structure on the focused page initially focuses on the structure of the selected region, from which you launch this page.

"Focused" version of the Page Hierarchy Personalization page for the Update Customer page.

the picture is described in the document text

The Personalization Context region at the top of the page lists the context for the top-level object, which in the case of the Oracle E-Business Suite, is the page layout. It identifies the scope of the personalizations you are about to make, as well as to what personalization level(s) and value(s) these personalizations apply.

The Simple View and Complete View radio buttons above the HGrid allow you to toggle between a Simple or Complete view of the page hierarchy in the HGrid.

The Shown column indicates whether the page element is rendered after applying all existing personalizations for the current context. The User Personalizable column indicates whether the page element is user personalizable.

You can launch a few tasks from this page, as described in the following table.

Task Launch Point from Focused Page Hierarchy Personalization page Flow Description
Personalize the properties (such as Prompt name, default value, and so on) of a specific page element

the picture is described in the document text

  1. Use the Page Hierarchy HGrid to locate the page element you wish to personalize.

  2. Select the pen icon from the Personalize column to navigate to the Personalize page for the element.

  3. In the Personalize page, you can edit the personalizable properties of the element at the different personalization levels specified for the current context.

  4. When you are done, select Apply to save your personalization.

Note: Although a region may be personalizable, not all region items in a region are personalizable. Each region item in a region has an ADMIN_CUSTOMIZABLE property associated with it. If the property is set to false by the developer of the region, the region item is not personalizable at the personalization level. For example, a developer would very likely set ADMIN_CUSTOMIZABLE to false for the vertical spacer item in a table layout region to prevent disruption of the spacing in a table.
Reorder the children of a boxed region

the picture is described in the document text

 Launches the Reorder Contents page, where you can reorder the children of the boxed region. Select "Apply" to save your changes when you are done.
Create a new item in a boxed region

the picture is described in the document text

 Launches the Create Item page, where you can create a new item for the content region. Select "Apply" to save your changes when you are done. The new item appears as the last item in the region. Use the Reorder Content icon to reorder the layout sequence of the new item. You can only create new items in boxed content regions or in the top page layout region.
Create, Duplicate, Update or Delete an "admin-seeded user-level" personalization

the picture is described in the document text

  1. Use the Hierarchy Page HGrid to identify the query region for which you wish to create an "admin-seeded user-level" personalization. (You can create seeded user-level personalizations only for a table or HGrid in a query region.)

  2. Select the Seeded User Views icon to launch the Personalize Views page.

  3. In the Personalize Views page, where you select different buttons or icons to create, duplicate or update a seeded view, you navigate to the respective Create/Duplicate/Update Views page.
Customize Look-and-Feel

the picture is described in the document text

 Launches the Customizing Look-and-Feel user interface.
Update an item created with the Create Item page

the picture is described in the document text

 Launches the Update Item page where you can update an item for the region. Note that you may only update an item that was previously created with the Create Item page.
Delete an item from a region

the picture is described in the document text

 Directs you to warning page that asks you to confirm whether you really want to delete the current item. Deleted items are non-recoverable.

Note: Delete Item is available only if the page element is an item that was created at the Site level using the Create Item page.

If you wish to exit from the focused Page Hierarchy Personalization page, select the "Return to Personalize Page" link at the bottom of the page to return to the Page Layout Personalization page.

Choose Personalization Context Page

The Choose Personalization Context page is launched when you select the Choose Context button from any of the personalization launch pages.

Choose Personalization Context page, with the Scope set to Page, and the personalization level set to "Site".

the picture is described in the document text

  1. In the Choose Personalization Context page, use the Scope poplist to specify whether you want to personalize the current page, or personalize a shared region, if any, that is extended by the current page. If there are no shared regions on the page, a single non-updateable radio button for the page itself is displayed for the scope.

    When you select the Page as the scope, the personalization you create applies only to the current instance of the page (saved as a per instance personalization). If there are shared regions on the page and you select a shared region as the scope, the personalization you create on that shared region is also saved as a per instance personalization of that shared region but will appear in all occurrences of that shared region in any page that extends it. Refer to Per Instance versus Global Personalization for further explanation.

    Note: If you wish to personalize the Standard Footer that appears in OA Framework-based pages, you can use the Standard Footer Personalization Shortcut that appears in the Application Catalog page under the Personalization tab of the Functional Administrator responsibility.

  2. Specify the personalization level at which you want to make your changes and specify a value for that level. The Site level does not require any value as the personalization applies to all users of the current site. To create a Site level personalization, check the Include checkbox. To create personalizations at any other level, enter a value for that specific level. Responsibility or Function levels, for example, require a specific responsibility or function name, respectively.

    You may specify more than one personalization level when you define a personalization. Simply specify values for each of the levels that you want this personalization to apply.

    You can specify a personalization value in one of the following ways:

    • Select a value from a specific level LOV (that is, from Function, Industry, Location, Organization, or Responsibility).

    • Choose the Set to My level button. The Set to My level button resets the personalization value to the default value for that personalization level. The default value, in turn, is derived from your current apps context. For example, if you are logged in as the System Administrator responsibility, then choosing Set to My Responsibility would set the Responsibility level to System Administrator. For the Localization level, the default value is determined by the profile option ICX: Territory (ICX_TERRITORY). For the Organization level, the default value is determined by the profile MO: Operating Unit, which can be set at the Site or Responsibility level.

      For more information about the ICX: Territory profile option, refer to the Internationalization section in the OA Framework Profile Options appendix of the Oracle Application Framework Developer's Guide.

  3. Once you finish setting your personalization context, choose Apply. Choosing Cancel returns you to the previous page.

Per Instance versus Global Personalizations

You can personalize a region that extends a shared region (that is, it contains a region that is defined elsewhere and the current region simply references or extends that base region). If you set the scope of your personalization context to the Page, the personalization is saved on the current instance of that page, as a per instance personalization, for the context specified. As a result, if another page extends the same shared region, you will not see your personalization in that other page.

If you want to save the personalization of a shared region so that it applies to all pages or regions that extend that shared region, set the scope of your personalization context to the Shared region. Note however, that the personalization you save on that Shared region is also technically saved as a per instance personalization, even though the personalization applies to all pages or regions that extend this Shared region.

This is because a shared region can itself extend another shared region. Suppose you have Page A that extends Shared region B and Shared region B extends Shared region C. Say you set your personalization context scope to Shared region B and create a personalization that alters Shared region C. The personalization that you save, although it appears to be saved as a global personalization because it now applies to all pages that extend Shared region B, is actually saved as a per instance personalization of Shared region B. The reason is because the change that was made in Shared region C was only saved to the instance where it was extended by Shared region B. In other words, the personalization you saved on Shared region B was not saved to the base of Shared region C, but only to that instance of Shared region C as it appeared in Shared region B.

Personalize Page

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.

Personalize page for the "Priority" Message Styled Text item in the Notifications table of the Workflow Notifications page.

the picture is described in the document text

Personalize page for a classic table region.

the picture is described in the document text

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:

Choose Levels Displayed page

the picture is described in the document text

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.

Note: If you are personalizing an item that has a CSS Class property, you can use the CSS Styles Lookup page to first preview your item with different CSS styles before setting the CSS Class name for the item. See the section on Style Sheets for additional information.

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:

Personalizing SPEL-supporting Properties

OA Framework supports SPEL (Simplest Possible Expression Language) personalizations on the following properties:

When you select the poplist icon for any of these properties in the personalization level columns, the poplist generally displays the choices Inherit, true, false, and SPEL, but with the following caveats:

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

For more information about SPEL personalizations, refer to the Implementing Partial Page Rendering Events > Changing UI Properties section in the Partial Page Rendering (Dynamic User Interface) chapter of the Oracle Application Framework Developer's Guide.

When you select SPEL from the poplist, an additional text box renders for you to enter a SPEL expression (string), such as ${oa.<viewObject>.<viewAttr>} or ${oa.function.<functionName>}.

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

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

When you personalize the values for any of these SPEL-supporting properties, you may see warnings.

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:

The above item styles all have a property called Initial Value that you may personalize. The value you specify for this property becomes the default value that an end-user sees 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 characters if the field length is 10 characters.

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:

Note: If a developer sets a default value on an item page element in their controller code, the developer-set default will override the default value you personalize in the Initial Value property.

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:

Note: If you navigate to the Personalize page by launching a flow from the "complete" Page Hierarchy Personalization page, the Apply and Personalize Another button does not render. The Apply button also has slightly different behavior in this case; it saves your personalizations and returns to the Page Hierarchy Personalization page.

Create Query Page

You can navigate to the Create Query page by selecting the Query row icon from the Personalization Properties table in the Personalize page when you personalize a table region. This page allows you to specify sort information and search criteria for a table region to filter the data that displays in that table.

Create Query page for a table region.

the picture is described in the document text

  1. In the Data Filter region, indicate how you want the filter to match your search conditions by selecting one of the following radio buttons: Show table data when all conditions are met or Show table data when any condition is met.

  2. first four columns of the table are listed for you to specify search criteria. Using the poplist following the column name, choose a search condition and enter a value to search for in that column.

  3. You can also select a column from the Add Another poplist and choose Add to add more search criteria to your filter.

    Note: Only columns whose Search Allowed property is set to True are displayed in the Add Another poplist. If this property is initially set to false and you want to be able to search on this column, you must first create an admin-level personalization of the table region that updates the Search Allowed property for the column (item) to True.

    If you leave the search criteria blank for a column, the filter does not search on that column.

  4. In the Sorting region, you can specify up to three levels of sorting for your data. Select a column from the Column Name poplist for each level of sorting you wish to perform.

    Note: Only columns whose Sort Allowed property is set to Yes are displayed in the Column Name poplist. If this property is initially set to no and you want to be able to sort on this column, you must first create an admin-level personalization of the table region that updates the Sort Allowed property for the column (item) to yes.

  5. For each sort column, you must specify whether to sort in ascending or descending direction.

  6. When you are done creating the data filter and specifying your sort settings, choose Apply to apply your changes and return to the Personalize page. The Query row of the Personalization Properties table should now display a Personalize icon (pen). The change in icon indicates that a data filter now exists at that personalization level and you can select the icon to view or update the existing data filter again.

Note: When you personalize a table region at various personalization levels and for each of those levels, specify search criteria for different columns in the table region, the search criteria are combined with a logical AND for the cumulative personalizations. The same is true if you personalize a table region at various personalizations levels, with search criteria for the same columns in the table region. The search criteria defined in all levels are AND-ed together.

Note: If the page metadata is shipped with the table containing first, second and third sort sequence columns already set, administrators may have to perform an additional step before changing the sort sequence of the table.

If any of the seeded first, second and third sort columns are not going to be used again as in personalized sort columns (either as first, second or third sort) each of these columns should be made non-sortable columns. This can be done by personalizing individual items and setting the "Sort Allowed" property to "no".

For Example, if the table is shipped with -

Column / Attribute Sort Sequence Sort Order
EmpNo First Ascending
Ename Second Ascending
Sal Third Descending

And an Administrator would like to personalize to

Column / Attribute Sort Sequence Sort Order
Mgr First Ascending
Sal Second Ascending
Desg Third Descending

Then the EmpNo and Ename columns should be personalized to "Sort Allowed - no".

Page Hierarchy Personalization Page: Expanded Search Region

When you choose the expand icon (+) for Search in the Page Hierarchy Personalize page, the Search region expands as shown in the following illustration. You can use this region to specify criteria that searches for a specific subset of page elements.

Note: You can perform a search only on pages, regions and their personalizations that reside in the database repository. Search is not able to locate elements on pages that reside on the local file system.

  1. Specify in the Style field whether to search for elements of a specific item style. If Style is set to null, then elements of all styles are searched. Note that the Style field displays only the styles used on the page elements of the current page.

  2. Specify in the Title/Prompt/Text field whether to search for elements that contain a specific title, prompt, or text. You may specify a wild card character (%) in the search string.

  3. Check Include Personalized Items Only if you want the search to return only matching results that have been personalized.

    Search region for the Page Hierarchy Personalize page.

    the picture is described in the document text

  4. Select Go to perform the search.

    The results are returned in a flat table, where the names of the matching page elements are sorted by style. This flat table has the same columns as the prior Page Hierarchy HGrid, so that you can launch the same personalization tasks from this presentation. However, it also includes a column called View in Hierarchy, from which you can select the Hierarchy icon for a page element to focus on the page element as displayed within the page hierarchy.

    Search Results in the Page Hierarchy Personalization page, showing all personalized page objects.

    the picture is described in the document text

  5. Select the Return to Personalization Structure link below the Search Results table if you want to return to the original Page Hierarchy Personalization page regardless of the focus you had before you selected Go to search for specific page elements.

Update Layout Page

The Update Layout page lets you alter the layout of a boxed region. You may lay out the content horizontally or vertically. Alternatively, you may split the boxed region into multiple peer layout regions. If you split the boxed region, you must select the Add Content icon from the Page Layout Personalization page to add content to the new peer region.

This page is launched from the Update Layout icon on the Page Layout Personalization page. You can only alter the layout of a page if the page you are personalizing is a configurable page.

Update Layout page

the picture is described in the document text

  1. Choose to layout the content vertically or horizontally. Alternatively, you may choose to split the current region into multiple peer regions.

  2. If you select Split Region, specify the number of row and columns to split the region.

  3. Choose Apply when you are done. You may also choose to Cancel your changes and return to the previous page.

Note: If you split the boxed region, you must select the Add Content icon from the Page Layout Personalization page to add content to the new peer region.

Reorder Contents Page

When you choose the Reorder Contents icon from the Page Layout Personalization page, the complete Page Hierarchy Personalization page, or the focused Page Hierarchy Personalization page, you navigate to the Reorder Contents page. You can reorder the contents of a page layout only if the page is configurable, otherwise you can reorder the contents of a region.

Reorder Contents page

the picture is described in the document text

The Reorder Contents page displays a reorder region for each personalization level set in the current personalization context and also displays a read-only region that shows the order of the content in the base definition.

  1. Use a reorder region to reorder the contents of a region by personalization level. The usage of a reorder region is as follows:

    • If the contents of a region have not been reordered at a given personalization level, the reorder region displays Inherit Order, by default. This indicates that at that personalization level, the boxed region inherits its order from the personalization level above it (lower levels take precedence ).

    • If you want to reorder the contents for a given personalization level, check the Personalize checkbox for that personalization level. If partial page rendering is enabled, the region refreshes to display the content that can be reordered. If partial page rendering is disabled, you must select the Go button to refresh the region so it displays the content to reorder.

      Note: The personalized order for any given personalization level is not actually applied until you choose Apply on the page.

    • The Personalize checkbox may also be checked for a personalization level if the region has previously been reordered (personalized).

    • Use the arrows on the side of the reorder region to reorder its contents.

  2. Choose Apply to apply the new order for each personalization-level that was personalized and return to your previous page.

Note: For configurable pages, you can reorder content only within the content's assigned layout region. You cannot reorder content across different layout regions.

Add Content Page

When you choose the Add Content icon from the Page Layout Personalization page or the complete Page Hierarchy Personalization page, you navigate to the Add Content page. You can add content to a page only if the page is configurable and if the region you are adding content to is a boxed layout region that contains only content regions and not other layout regions.

Add Content page

the picture is described in the document text

The Add Content page displays a catalog of predefined content regions that you can add to the selected region. The Content catalog lists the title of the predefined content and its description.

Note: This page initially displays only the predefined content regions that were delivered with your Oracle application. If you have defined additional independent content regions that you want to include on this list, select the Create Content button to access the Create Content page.

Note: The Create Content button is available only at the Site, Function, and Localization levels.

If a content contains a user-personalizable region and one or more personalized views of that region exists, the Content catalog will list each defined view by its view name and the content with which it is associated. Once you add a content (or a personalized view of a content) to a boxed layout region, the next time you display the Add Content page, the content or other personalized views of the content will no longer be available for selection from the Content catalog. You must remove the content from the current layout region, using the Remove Boxed Region icon , before you can choose a different personalized view of that content to add.

  1. Enter a title or description in the Search region and choose Go to search for the content you wish to add.

  2. Check Select for the content you wish to add.

  3. Choose Apply to save your personalization and return to your previous page.

    The new content is added as the last content region of the selected boxed layout region.

Important: Since you can personalize a configurable page at only one level at any given time, any personalizations you make to the page, such as adding new content, are not available at any other level. For example, if you create and add content to a flexibleContent region on a configurable page at the Site personalization level, that content will not be available to users at the Responsibility level. You can work around this restriction as follows:

  1. Use the Functional Administrator responsibility to launch OA Personalization Framework.

  2. In the Application Catalog, search for the specific region that you want to personalize, then select the Personalize icon to navigate to the Page Hierarchy Personalization page.

  3. Select Choose Context to specify the level(s) at which you want your personalization to apply.

  4. Personalize the region. Note that the personalization you create from the Functional Administrator tool is applied to all instances of the region.

  5. Navigate back to the configurable page and launch OA Personalization Framework. Set the personalization level to the level specified in step 3. In the Content mode of the Page Layout Personalization page, use the Add Content page and Create Content button to add the region personalized in the previous step to a desired flexibleContent region.

  6. If you specify more than one personalization level in step 3, repeat step 5 for each of the other personalization levels.

Create Content Page

When you click the Create Content button on the Add Content page, you navigate to the Create Content page.

Create Content page

the picture is described in the document text

Use the Create Content page to select a custom content region that you have already defined in JDeveloper, and want to include on the list of predefined content regions on the Add Content page. Be sure to enter the region's ID and title, and the full name (for example, /com/mine/ext/MyTableRN). It is a good idea to add a description, which will provide useful selection information. When you select Apply, the Add Content page will appear, with this region added to the list of available content regions.

Important: The region you specify must be displayable without the use of any other resources.

Create Item Page

When you choose the Create Item icon from the Page Layout Personalization page, the complete Page Hierarchy Personalization page, or the focused Page Hierarchy Personalization page, you navigate to the Create Item page. Use the Create Item page to declaratively add a new item to a region using the OA Personalization Framework.

Important: You can add a new item to a region using OA Personalization Framework only if:

Important: You may add a new item to a table or HGrid; however, all items in the table or HGrid must be set to the same BC4J view usage name.

Create Item page listing the properties you can specify for a Tip item.

the picture is described in the document text

  1. Use the Level poplist to specify whether to create the new item at the Site or Function level. Use the Item Style poplist to select the item style to create. Currently, you can create an item of any of the following styles:

    Item Style Description Usage Notes
    Attachment Image An Attachment column in a table region that renders the following icons:

    • Attachment icon - navigates to the Attachment page, where users may view the attachments for a current record.

    • Add icon - navigates to the Add Attachment page, where users can add an attachment to a record

    Note: This item style is only available for creation under a table or advanced table region.

    1. You must enter the name of the View Instance for the entity you are attachment-enabling.

    2. After creating Attachment Table item, select the Create Item icon again for categoryMappings in the Page Hierarchy Personalization page to create a Category Map.

    3. Select the Create Item icon for entityMappings under the Attachment Table item in the Page Hierarchy Personalization page to create an Entity Map.

    4. Finally, select the Create Item icon for primaryKeys under the Attachment Table item in the Page Hierarchy Personalization page to create a Primary Key if none has yet been defined for the entity map.

    Refer to the OA Component Reference for information about other properties to set.
    Attachment Link A View link that navigates to the Attachments page where users can view existing attachments for the entity record. This item style also renders an Add button that users can select to add new attachments to the current entity record.

    1. You must enter the name of the View Instance for the entity you are attachment-enabling.

    2. After creating Attachment Link item, select the Create Item icon again for categoryMappings in the Page Hierarchy Personalization page to create a Category Map.

    3. Select the Create Item icon for entityMappings under the Attachment Link item in the Page Hierarchy Personalization page to create an Entity Map.

    4. Finally, select the Create Item icon for primaryKeys under the Attachment Link item in the Page Hierarchy Personalization page to create a Primary Key if none has yet been defined for the entity map.

    Refer to the OA Component Reference for information about other properties to set.
    Attachment Table An Attachments table that users can use to view existing attachments for the entity record.

    1. You must enter the name of the View Instance for the entity you are attachment-enabling.

    2. After creating Attachment Table item, select the Create Item icon again for categoryMappings in the Page Hierarchy Personalization page to create a Category Map.

    3. Select the Create Item icon for entityMappings under the Attachment Table item in the Page Hierarchy Personalization page to create an Entity Map.

    4. Finally, select the Create Item icon for primaryKeys under the Attachment Table item in the Page Hierarchy Personalization page to create a Primary Key if none has yet been defined for the entity map.

    Refer to the OA Component Reference for information about other properties to set.
    Button A button that represents an action that you can perform on a region. OA Framework generates buttons as images that represent the underlying function. You must enter a value for Prompt with this item style.
    If you want your Button to navigate to another page, you can specify a Destination URI value that navigates to that page.
    Refer to the OA Component Reference for information about other properties to set.
    Category Map A custom category to associate with an Attachment item.

    Note: This item style appears in the Item Style poplist only when you choose the Create Item icon for categoryMappings under an Attachment entity hierarchy in the Page Hierarchy Personalization page.

    		 You must enter a value for the Category property. This value should be identical to the predefined internal name of the category in the FND_DOCUMENT_CATEGORIES table.
    You may specify whether to secure the categoryMap with Application Security rules. The default value for the Secure property is False.
    Refer to the OA Component Reference for information about other properties to set.
    Column A new column in an advanced table or a column group.

    Note: This item style appears in the Item Style poplist only when you choose the Create Item icon for an advancedTable or a columnGroup in the Page Hierarchy Personalization page.

    		 Every new column is accompanied by a Create Item icon, as well as a columnHeader child item with its own Create Item icon, on the HGrid of the Page Hierarchy Personalization page.
    The only style of item you can insert under the columnHeader is a sortableHeader.

    Caution: If you create a sortableHeader item under the columnHeader, you must also create at least one more child item for the column (by clicking the column's Create Item icon); otherwise a run-time exception will occur when you choose Return to Application. The Prompt property of the sortableHeader will provide the column's "header," and the immediate children of the column will constitute its "body."
    Entity Map An entity to associate with an Attachment item.

    Note: This item style appears in the Item Style poplist only when you choose the Create Item icon for entityMappings under an Attachment entity hierarchy in the Page Hierarchy Personalization page.

    		 You must enter a value for the Entity property:

    • If you defined an entity in the AK Entity form to share between the Oracle Forms and OA Framework interfaces, specify the Entity ID you defined in the AK Entity form.

    • If you are enabling attachments only to be viewed from the OA Framework interface, enter a unique arbitrary value for Entity and be sure to create a primaryKeyMap for the entity map.


    Refer to the OA Component Reference for information about other properties to set.
    Export Button An Export button that when selected, exports the data displayed in a region. Create this item at the desired position within the region whose data you want to export.
    You must set the View Instance name to the same view object associated with the region for which you want to enable export.
    Flex A key or descriptive flexfield. A key flexfield represents an object defined by the values a user enters in each of its segments. A descriptive flexfield is customizable "expansion space" on a page. You must specify values for the following properties of this item style:

    • Appl Short Name

    • Name - set to the name of the flexfield as it was registered

    • View Instance

    • Type - key or descriptive


    If you want only specific segments of the flexfield to render, specify a value for the Segment List property. If this property is left blank, then all segments are rendered. Segments within a certain context are listed, separated by "|", a single pipe, while data from different context is separated by "||", a double pipe.
    Additionally you can click on the create item icon to create a flexMap under the flex item. When the user clicks on the icon, the Create Item page will be displayed with the Item Style as Flex Map. A user can enter the required parameters for the item and click on Apply. The flex map item created will be added under the flex item .
    Refer to the OA Component Reference for information about other properties to set.
    Flexible Layout A flexible layout region.

    Important: This item type can only be created at the Site level and is intended to be used for inserting another region into a page by adding one flexible content that extends that region. It does not allow the construction of complex flexible layout regions. To construct a fully configurable page, use OA Extension, as described in the Oracle Application Framework Developer's Guide.

    Note: If a page contains flexible layout and flexible content created from the personalization Create Item page, you get the Page Hierarchy Personalization page UI when you personalize the page. If a page's base definition contains flexible layouts and flexible contents, you get the Page Layout Personalization page UI.

    1. Specify whether the Rendered property is true or false.

    2. Specify an optional Comment.

    3. Select the Create Item icon for the newly created flexible layout region in the Page Hierarchy Personalization page to create a flexible content element.
    Flexible Content Flexible content that extends another region and renders within a flexible layout region.

    Note: This item style appears in the Item Style poplist only when you choose the Create Item icon in the Page Hierarchy Personalization page for a newly created Flexible Layout region defined in the Create Item page.

    		 Specify the full package name of the region that the flexible content extends.

    Important: Flexible content can only be inserted into a flexible layout at the site level and the current personalization scope must be a page.

    Flexible contents can be deleted, but not updated.

    Tip: Creating only one flexible content per flexible layout is recommended. If you create more than one flexible content for a single flexible layout, the flexible contents will be vertically aligned and you will not have the option of changing their order or alignment.
    Form Value A value submitted with a form but that is not displayed on the page. Specify a View Instance and View Attribute from which this item derives its value.
    Refer to the OA Component Reference for information about other properties to set.
    Formatted Text Formatted text using generic HTML formatting tags. You must enter an ID and Text for this item style.
    Refer to the OA Component Reference for information about other properties to set.
    Image An image can be a plain image that simply appears on the page, or can have a URL associated with it so that the user can click on it to navigate elsewhere. Although icon images are generally used as global buttons in the Oracle E-Business Suite, an icon image may also be used next to text to visually quantify its content, as in the case of tips, or in line messages. You must specify a value for Image URI with this item style.
    If you want to optionally associate a URL with the image, specify a value for the Destination URI property.
    Refer to the OA Component Reference for information about other properties to set.
    Link A link represents an action that you can perform on a region. A link can be used to navigate to another page or region. You must enter a value for Text with this item style. For navigation, the Destination URI value must be a valid destination.
    Refer to the OA Component Reference for information about other properties to set.
    Message Check Box A checkbox, that when checked, specifies a value. You must enter a value for Prompt with this item style.
    Refer to the OA Component Reference for information about other properties to set.
    Message Choice A poplist where users can select any value displayed in the poplist. You must specify values for the following properties of this item style:

    • Prompt

    • Picklist View Instance

    • Picklist View Definition

    • Picklist Display Attribute

    • Picklist Value Attribute


    Refer to the OA Component Reference for information about other properties to set.
    Message Download A file download link, which when selected opens a small Browser window that allows the user to either open the file and display its content or save the file to a client machine. You must specify values for the following properties:

    • View Instance - view object instance of the underlying data source.

    • View Attribute - view attribute that maps to a column in the underlying data source.

    • File View Attribute - view attribute that maps to the column that stores the file content.


    Refer to the OA Component Reference for information about other properties to set.
    Message File Upload An Upload File prompt, input field and Browse button that allows users to upload a file from a client machine to the middle tier.

    Note: If this item is associated with a view object instance and view attribute that returns a non-null value, that is, a file is already uploaded, OA Framework renders a Upload File prompt, View link and Clear button, so the user can view the already uploaded file, or clear it to upload another file.

    		 You must specify values for the following properties:

    • View Instance - view object instance of the underlying data source.

    • View Attribute - view attribute in the specified view object instance that maps to the column for storing the file content.


    Refer to the OA Component Reference for information about other properties to set.
    Message Inline Attachment A list of inline attachment links that users can select to view a specific attachment. Also renders the “More…” link, which allows users to navigate to the Attachments user interface to perform further operations on attachments.

    1. You must enter the name of the View Instance for the entity you are attachment-enabling.

    2. After creating Message Inline Attachment item, select the Create Item icon again for categoryMappings in the Page Hierarchy Personalization page to create a Category Map.

    3. Select the Create Item icon for entityMappings under the Message Inline Attachment item in the Page Hierarchy Personalization page to create an Entity Map.

    4. Finally, select the Create Item icon for primaryKeys under the Message Inline Attachment item in the Page Hierarchy Personalization page to create a Primary Key if none has yet been defined for the entity map.

    Refer to the OA Component Reference for information about other properties to set.
    Message LOV Input A LOV that allows users to select a value from a Search and Select List of Values window. Follow the instructions outlined in Creating a Message LOV Input Item.
    Refer to the OA Component Reference for information about other properties to set.
    Message Radio Group A radio group that allows a user to select one of several distinct values. You must specify values for the following properties of this item style:

    • Prompt

    • Picklist View Instance

    • Picklist View Definition

    • Picklist Display Attribute

    • Picklist Value Attribute


    Refer to the OA Component Reference for information about other properties to set.
    Message Styled Text A text field that can be updated and have a default value. You can optionally enter a value for the Prompt, or View Instance and View Attribute properties.
    If you wish to change the style of the text or associate a URL with the text, you can specify values for the CSS Class or Destination URI properties, respectively.
    Refer to the OA Component Reference for information about other properties to set.
    Message Text Input A text input field. You must enter a value in the Prompt field for this item style.
    You may also optionally enter a value for the View Instance and View Attribute properties.
    Refer to the OA Component Reference for information about other properties to set.
    Primary Key A primary key associated with the Entity Map of an attachment entity.

    Note: This item style appears in the Item Style poplist only when no other primary key has been defined yet for the entity map and you choose the Create Item icon for primaryKeys under an Attachment entity hierarchy in the Page Hierarchy Personalization page.

    		 You must enter a View Attribute name for the primary key.
    Refer to the OA Component Reference for information about other properties to set.
    Raw Text Any type of text. For example, the raw text style allows you to enter HTML tags to display text in bold. You can optionally enter a value for the following properties: Additional Text, or View Instance and View Attribute.
    Refer to the OA Component Reference for information about other properties to set.

    Caution: In general, you should avoid using custom HTML as it does not meet the NLS, accessibility, security, and Oracle Browser Look-and-Feel (BLAF) UI guidelines and standards.
    Separator A line to separate portions of a region. By default, the separator is rendered as a blue dotted line. Refer to the OA Component Reference for information about other properties to set.
    Servlet Include Includes HTML content loaded from a local Servlet or JSP under the parent region. You must enter a value for Source URI to indicate the Servlet or JSP source.
    Refer to the OA Component Reference for information about other properties to set.
    Spacer A space that you can include in a region to improve the appearance of its layout. You must specify values for spacer Width and spacer Height with this item style.
    Refer to the OA Component Reference for information about other properties to set.
    Stack Layout A stack layout region that renders its children regions and items in a vertical stack without any indentation. Stack layouts may be created in any region, but only at the Site level.
    Refer to the OA Component Reference for information about other properties to set.
    Static Styled Text Text that is for display only and not for editing purposes. For example, if you wish to create a URL link, you would define its item style as static text. You must enter a value for Prompt with this item style.
    If you wish to change the style of the text, you can specify the CSS Class whose style you want the text to inherit.
    Refer to the OA Component Reference for information about other properties to set.
    Tip Text that provides a tip about the contents of the region. You must specify a Tip Message Name for this item style.
    Refer to the OA Component Reference for information about other properties to set.
    URL Include Includes HTML content loaded from an external source under the parent region. You must enter a value for Source URI to indicate the source of this HTML content. No post-processing on the HTML is performed, so the included HTML should not include HTML tags like <html> or <body>.
    Refer to the OA Component Reference for information about other properties to set.

  2. Enter a required ID for the new region item. Region item IDs should not exceed 30 characters, and they should be as short as possible. Abbreviations (which would be understood by consultants and customers) are encouraged. Item IDs must be unique within a single page regardless of its placement within the page hierarchy.

  3. The properties that you can set for your new item are dynamically determined based on the item style that you select in Step 1. Check the Usage Notes column in the table shown in Step 1 for information about the specific properties you need to set for a specific item style. Note that the properties that you can set when you create an item in the Create Item page may not be personalizable. Thus, for a specific item style, you may see more properties listed in the Create Item page, than what is shown for the same item style in the Personalize page.

    If you must update some non-personalizable property of an item you created in the Create Item page, use the Update Item page.

    Tip: If an item style allows you to specify a value for its CSS Class, you can use the CSS Styles Lookupelement to first preview your item with different CSS styles before setting the CSS Class name for the item. See the section on Style Sheets for additional information.

    Note: If you want to create an item that allows you to specify a Destination URI, you should specify the URI syntax as:<protocol>://<machine>:<port>/... For example, http://www.abcompany.com/home/page1.htm. If you want to call an Oracle E-Business Suite function, specify the function name for the Destination Function property. For example, to call the PL/SQL General Preferences page from an item, you would enter the following value for the Destination Function property: ICX_USER_PREFERENCES. Make sure that the page specified as the Destination URI has a link that navigates you back to the original page. See Examples: Creating New Items Using the Personalization UI for additional information.

  4. Choose Apply to create the new item and return to the previous page. The new item is created as the last item in the region. You can use the Reorder Content control from the complete Page Hierarchy Personalization page or the Page Layout Personalization page to reorder the position of the new item.

Note: For configurable pages, you can only create a new item in a boxed content region or to the top pageLayout region. You cannot create a new item in a boxed layout region that contains only boxed layout regions as children.

Tip: If you make a mistake when you create a new item, such that it causes the base page to display an error, you can sign on to the Oracle E-Business Suite as the Functional Administrator responsibility and remove the personalization using the Manage Personalization Levels page.

Creating a Message LOV Input Item

Follow these steps if you wish to create a Message LOV Input item using the Create Item page:

  1. Use the Item Style poplist to select Message LOV Input.

  2. Enter a required ID for the new region item. Region item IDs should not exceed 30 characters, and they should be as short as possible. Abbreviations (which would be understood by consultants and customers) are encouraged. Item IDs must be unique within a single page regardless of its placement within the page hierarchy.

  3. Enter values for the External LOV and Prompt properties.

  4. Set the Data Type property to match the data type of the attribute returned from the LOV.

  5. Choose Apply to create the new item and return to the Page Hierarchy. You should see a new grouping called lovMappings created under this new item. LOV Mappings define the data communication between the base page and the and LOV window.

  6. Select the Create Item icon for lovMappings in the Page Hierarchy. In the Create Item page, create a related LOV Map for the Message LOV Input item. Specify a value for the required ID property and these other required properties:

    • Criteria Item - the base page item whose value is to be used as LOV search criteria

    • LOV Region Item - the item in the LOV for which the mapping is defined.

    • Return Item - the base page item whose value is to be populated by the LOV selection

  7. Choose Apply to create the new item and return to the previous page. Repeat Step 6 to create additional LOV Maps.

  8. When you finish creating your related LOV Maps, select Return to Application from the Page Hierarchy to view the new Message LOV Input item on your application page.

Update Item Page

When you choose the Update Item icon from the Page Layout Personalization page or the complete Page Hierarchy Personalization page, you navigate to the Update Item page. Use the Update Item page to update the properties of an item that you created declaratively in the Create Item page of OA Personalization Framework.

Important: You can only add a new item to a region if you are personalizing a region at the Site, Function, or Localization level. Any new item that you create while personalizing a region at the Function or Localization level may only be further personalized or updated at the same Function or Localization level at which it was created. New items that you create while personalizing a region at the Site level may later be personalized at any level. For example, you may personalize at the Responsibility level, an item that you create at the Site level.

Update Item page for a Tip item that was created.

the picture is described in the document text

The Update Item page displays the current personalization level, which can only be Site.

  1. The properties that you can update for your item are dynamically determined by the item's style. Check the Usage Notes column in the table shown in Step 1 of the Create Item page for information about the specific properties that you can update for a specific item style. Note that the properties that you can set in the Update Item page may not be personalizable. Thus, for a specific item style, you may see more properties listed in the Update Item page, than what is shown for the same item style in the Personalize page.

    Note: If an item style allows you to specify a value for its CSS Class, you can use the CSS Styles Lookup page to first preview your item with different CSS styles before setting the CSS Class name for the item. See the section on Style Sheets for additional information.

    Note: If you want to update an item that allows you to specify a Destination URI, you should specify the URI syntax as:

     <protocol>://<machine>:<port>/...

    For example:

    http://www.abcompany.com/home/page1.htm

    If you want to call an Oracle E-Business Suite function, omit the protocol://machine:port specification in the URI, and only enter OA.jsp? with the following syntax: OA.jsp?OAFunc=<Apps function you want to call>. OA Framework automatically prepends the correct syntax for the OA_HTML directory path so that your function runs properly. For example, to call the PL/SQL General Preferences page from an item, you would enter the following value for the Destination URI property:

    OA.jsp?OAFunc=ICX_USER_PREFERENCES

    Make sure that the page specified as the Destination URI has a link that navigates you back to the original page.

  2. Choose Apply to update the new item and return to the previous page.

    Tip: If you make a mistake when you update a new item, such that it causes the base page to display an error, you can sign on to Oracle E-Business Suite as the Functional Administrator responsibility and remove the personalization using the Manage Personalization Levels page.

Manage Personalization Levels Page

The Manage Personalization Levels page is launched when you choose the Manage Levels button from the complete Page Hierarchy Personalization page or the Page Layout Personalization page. You can use the Manage Personalization Levels page to select existing personalizations to activate, inactive or delete. You can also launch from this page, tasks to manage the translation of your personalizations.

Manage Personalization Levels page

the picture is described in the document text

The Manage Personalization Levels page displays a table for each scope of the original page. For example, the original page might have three possible scopes: the Page itself, the OA Footer shared region, and the Notifications Worklist Function shared region. Shared regions are regions that can be shared among different pages. If you select a shared region as your scope when you set your personalization context, any personalizations you create get propagated to all occurrences of that shared region for the personalization level specified. If you select the page as your scope, then any personalizations you make are applied to just that local page. Refer to Per Instance versus Global Personalization for more details.

  1. Each table lists all the existing personalizations and identifies the personalization levels at which they were created (function, localization, site, organization, responsibility, "Oracle-seeded user-level" and "admin-seeded user-level"). The table identifies when the personalization was last updated and whether the personalization is active. You may select a personalization and use the Activate or Deactivate buttons to activate or deactivate the personalization.

  2. If you wish to delete one or more personalizations, select the personalization(s) and choose Delete Personalization. Deleted personalizations are not recoverable.

    Note: "Oracle-seeded" and "admin-seeded" user-level personalizations cannot be deleted from this page. If you wish to delete seeded user-level personalizations, you can do so from the Personal Views page.

  3. Select the Translate icon for a personalization if you want to translate the personalization to another language. The Translate icon launches the Translate page where you can translation your personalization inline. The Translate Column appears only if you have a language other than the base language installed on your system.

    Note: "Oracle-seeded" and "admin-seeded" user-level personalizations cannot be translated. The Translate icon is disabled for these personalizations.

  4. If you wish to extract translation files for one or more personalizations, select the personalization(s) and choose Extract Translation File. This button navigates to the Extract Translation Files page, where you can specify the languages to extract.

  5. Select a personalization and choose Upload Translations if you want to upload the translations of a personalization from XLIFF files. This button launches the Upload Translations page.

  6. Once you are done making changes to the Manage Personalization Levels page, select Apply to save your changes and return to the previous page.

Extract Translation Files Page

The Extract Translation Files page is launched from the Extract Translation File button on the Manage Personalization Levels page. Use this page to select the languages for which you want to extract translation files.

Note: You must set the Fnd Xliff Export Root Path (FND_XLIFF_EXPORT_ROOT_PATH) profile option before you can extract translation files. The directory that you specify for this profile option should have permissions set to read, write, create for all users, using chmod 777 <dir_path>.

Extract Translation Files page

the picture is described in the document text

  1. Use the arrow buttons between the Available Languages and Selected Languages lists to shuttle selected languages between the two lists.

  2. Choose Apply to extract the personalization translations for these languages to an oraXLIFF file and return to the Manage Personalization Levels page. Language-specific subdirectories are created for each selected language in the package structure generated from the setting of the Fnd Xliff Export Root Path profile option.

For more information about the Fnd Xliff Export Root Path profile option, refer to the Personalization section in the OA Framework Profile Options appendix of the Oracle Application Framework Developer's Guide.

Upload Translations Page

The Upload Translations page is launched from the Upload Translations button on the Manage Personalization Levels page. Use this page to upload available personalization translations from oraXLIFF files located in the language subdirectory of the package structure generated from the setting of the Xliff Import Root Path (FND_XLIFF_IMPORT_ROOT_PATH) profile option.

For more information about the Xliff Import Root Path profile option, refer to the Personalization section in the OA Framework Profile Options appendix of the Oracle Application Framework Developer's Guide.

Upload Translations page

the picture is described in the document text

The table lists the personalization translations that are available for upload. The table also identifies source language of the file and the language of the translation.

  1. Select one or more personalization translation(s).

  2. Choose Apply to upload the translations to the MDS repository and return to the Manage Personalization Levels page. The uploaded translations now also appear in the Translate page.

Translate Page

The Translate page is launched from the Translate icon on the Manage Personalization Levels page. Use this page to perform inline translations of your personalizations.

Translate page

the picture is described in the document text

The Translate page displays a table that lists all the page elements (Style column) and their translatable properties (Attribute column) that were modified in the selected personalization. It provides a read-only column that lists the personalized value for each property in the base language.

The table also shows columns for up to four languages. Any existing translations that have been previously uploaded are displayed in these language columns. If a field in a language column is empty, the translation for that field is defaulted from the base language.

  1. Select Choose Languages to navigate to the Choose Languages page, where you can select the languages (up to four) that display in the Translate page. When you are done choosing translation languages, return to the Translate page.

  2. In the column for the language to which you want to translate the personalization, enter a translation value for the translatable property.

  3. Repeat Step 2 for the other languages to which you want to translate the personalization.

  4. Choose Apply to save your translations to the MDS repository and return to the Manage Personalization Levels page.

Choose Languages Page

The Choose Languages page is displayed when you select the Choose Languages button from the Translate page.

Choose Languages page

the picture is described in the document text

The languages that are currently installed are displayed in the Available Columns list.

  1. Use the shuttle controls to select up to four languages to display in the Columns Displayed list.

  2. Choose Apply to display the selected languages in the Translate page.

Personalize Views Page

The Personalize Views page is displayed when you select the Seeded User Views icon from the complete Page Hierarchy Personalization page or the focused Page Hierarchy Personalization page. From this page, you can seed new end user views or duplicate, update, or delete pre-seeded end-user views.

Note: You can find more information about using this page in the User-Level Personalization User Interface chapter.

Important: "Oracle-seeded" or "Admin-seeded" end user views can be created only for tables (including HGrids) in a query region.

Personalize Views page

the picture is described in the document text

If you are an Oracle in-house E-Business Suite developer, only "Oracle-seeded" end user views are displayed in the Personalize Views table. If you are an Administrator, "Oracle-seeded" and "Admin-seeded" end user views are displayed and the only action you can perform on an "Oracle-seeded" view is to duplicate it.

Note: As an Administrator, you cannot update or delete an "Oracle-seeded" end user view. Instead, if you want to personalize the view, you should duplicate the view and personalize the duplicate. This ensures that if Oracle ever ships changes to an "Oracle-seeded" end user view, it will never override your personalizations, because you will have personalized not the "Oracle-seeded" view, but a duplicate of the "Oracle-seeded" view.

Note: When an end-user chooses to personalize a table in a Query region, the user sees all "Oracle-seeded" and "Admin-seeded" end user views, in addition to the personalized views he or she creates, in the Personalize Views page. Although users can select any "Oracle-seeded" or "Admin-seeded" user view as their default view, they cannot update or delete the seeded view. Instead they can duplicate the seeded view and personalize the duplicate to ensure that their personalizations are preserved when there is an upgrade. See Default Views for additional information.

The Personalize Views page displays the name of each view, along with a description.

Create View, Update View, and Duplicate View Pages

The Create View page is identical to the Duplicate View and Update View pages, except that the fields in the latter pages are pre-populated with settings from the selected personalization.

Note: You can find more information about using these pages in the User-Level Personalization User Interface chapter.

Create View page

the picture is described in the document text

Important: Although a region may be personalizable, not all region items in a region are personalizable. Each region item in a region has an ADMIN_CUSTOMIZABLE property associated with it. If the property is set to false by the developer of the region, the region item is not personalizable at the Admin level. For example, a developer would very likely set ADMIN_CUSTOMIZABLE to false for the vertical spacer item in a table layout region to prevent disruption of the spacing in a table.

  1. Edit the following General Properties for your table or HGrid region:

    • View Name - the name of the personalized end user view as it appears in the Personalize Views page or the Personal Table Views page for end-users.

    • Number of Rows Displayed - the number of rows of data you wish to display in the table.

    • Set View as Default - check if you want to make this personalized view the default view. As an Administrator, you can only set an "Admin-seeded" end user view as a default.

      Note: If an "Oracle-seeded" end user view and an "Admin-seeded" end user view of the same region are both marked as defaults, the "Admin-seeded" end user view takes precedence and is displayed as the default for the end user. However, if an end user also has a personalized view of the same region that he or she marks as the default, then the end user's personalized view takes precedence over both seeded views and is the default for that end user. See Default Views for additional information.

    • Securing Function - the function for which this view is available. Specifying a securing function allows you to restrict the use of this view to only users who have been granted access to that function. Refer to the section on Securing Views for complete information.

    • Description - an optional description for this personalized view.

  2. Use the Columns Shown and Column Order shuttle to specify the columns to display in the table or HGrid region. Select an item from the Available Columns or Columns Displayed list and use the arrows between these lists to either move the selected item to or remove the selected item from the Columns Displayed list.

    Note: Columns that are required fields table appear with an asterisk (*) and cannot be removed from the Columns/Attributes Displayed list.

    Example

    Following is an example of an advanced table with two levels of column spans.

    the picture is described in the document text

    Each of the columns in the top row (labeled "Group X" and "Group Y") spans two columns in the second row (labeled "Group A" and "Group B" in both cases). Each "Group A" column in turn spans "Column 1" and "Column 2" below it, while each "Group B" column spans "Column 3" and "Column 4."

    If the region you are personalizing is an Advanced Table that displays column spans, as shown in the example, the columns listed in the Available Columns and Columns Displayed shuttle will have the entire hierarchy of column group names appended to each column name. This ensures that you hide/show the correct column, especially in the case where multiple columns of the same name may exist within different column groups. For the example shown, the columns shown in the Available Columns and Columns Displayed lists would be:

    Group X: Group A: Column 1
Group X: Group A: Column 2
Group X: Group B: Column 3
Group X: Group B: Column 4
Group Y: Group A: Column 1
Group Y: Group A: Column 2
Group Y: Group C: Column 3
Group Y: Group C: Column 4

  3. Once you are satisfied with the columns to display, use the arrows to the right of the Columns Displayed list to reorder their sequence.

  4. Choose Rename Columns / Totaling to rename or show a total for a column.

  5. You can specify up to three levels of sorting for your data in the Sort Settings region. Select a column from the Column Name poplist for each level of sorting you wish to perform.

    Note: Only columns whose Sort Allowed property is set to Yes are displayed in the Column Name poplist. If this property is initially set to no and you want to be able to sort on this column, you must first create an admin-level personalization of the table region that updates the Sort Allowed property for the column to yes.

  6. For each sort column, specify whether to sort in ascending or descending order.

  7. You can filter the data that is displayed in the table based on criteria that you specify in the Search Query to Filter Data in Table region:

    1. Indicate how you want the filter to match your search conditions by selecting one of the following radio buttons: Show table data when all conditions are met or Show table data when any condition is met.

    2. The first four columns of the table are listed for you to specify search criteria. Using the poplist following the column name, choose a search condition and enter a value to search for in that column.

    3. Select a column from the Add Another poplist and choose Add to add more search criteria to your filter.

    Note: Only columns whose Search Allowed property is set to True are displayed in the Add Another poplist. If this property is initially set to False and you want to be able to search on this column, you must first create an admin-level personalization of the table region that updates the Search Allowed property for the column to True.

    Tip: If you leave the search criteria blank for a column, the filter will not search on that column.

  8. When you are done personalizing your view of the table or HGrid region, you can choose Apply to save the personalized view and return to the Personalize Views page. If you choose Revert to revert to default settings, the following occurs depending on the page you are using:

    • Create View page - the page defaults to the pre-seeded display settings, where no query options are set.

    • Duplicate View or Update View page - the page defaults to the display settings and query options of the saved existing view.

    Note: How you set the Scope of your personalization context in the Choose Personalization Context page affects how your personalized view is saved. The view may be saved to the current instance of the page as a per instance personalization if you set the Scope to Page. If there is a shared region on the page and you select the Shared region as the Scope, the personalization you create on that shared region is also saved as a per instance personalization of that shared region but will appear in all occurrences of that shared region in any page that extends it. Refer to Per Instance versus Global Personalization for further details.

Securing Views

OA Personalization Framework secures views through the Securing Function property in the Create/Update/Duplicate View pages.

If an "Oracle-seeded" or "Admin-seeded" end user view has a securing function associated with it, only end users who are granted access to that securing function are able to see that view in the Views poplist of the Views panel of their Search page. The securing function, in addition to restricting visibility of a secured view in the Views poplist of the Views panel, also restricts visibility of a secured view in the Personalize Views page.

As an administrator, you are not able to update or delete "Oracle-seeded" end user views. As a result, seeded views are always visible to all end users. For example, you cannot update "Oracle-seeded" views to restrict them to a specific set of end users or delete some of these views for all end users. However, if you want to turn off an "Oracle-seeded" view, you can duplicate the seeded view and set the securing function on the duplicated view to a function to which a user or group of users does not have access.

If you want to simply control the visibility of a view for an end user in the Views poplist of the Views panel, first duplicate the view and set a securing function on the duplicate, granting the user access to that function. Then in the Personalize View page, set Display View to Yes or No for that duplicated view.

The following table identifies the accessibility of views to administrators as well as end users, when a securing function is specified for "Oracle -seeded" and "Admin-seeded" end user views.

Created By Active Effect on an Administrator's Personalize Views Page Effect on an End User's Personalize Views Page Effect on the Views Poplist in the Views Panel
Oracle Yes Securing function: Yes
Shown: Yes
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Shown: Only if user has access to the securing function.
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Shown only if user has access to the securing function.
Oracle No Securing function: Yes
Shown: Yes
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Shown: Only if user has access to the securing function.
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Not shown, since the Active property is set to No.
Administrator Yes Securing Function: Yes
Shown: Yes
Can be deleted: Yes
Can be modified: Yes
Can be duplicated: Yes		 Shown: Only if user has access to the securing function.
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Shown only if user has access to the securing function.
Administrator No Securing Function: Yes
Shown: Yes
Can be deleted: Yes
Can be modified: Yes
Can be duplicated: Yes		 Shown: Only if user has access to the securing function.
Can be deleted: No
Can be modified: No
Can be duplicated: Yes		 Not shown, since the Active property is set to No.
End User Yes Not applicable Shown: Yes
Can be deleted: Yes
Can be modified: Yes
Can be duplicated: Yes		 Shown: Yes
End User No Not applicable Shown: Yes
Can be deleted: Yes
Can be modified: Yes
Can be duplicated: Yes		 Not shown

Rename Columns / Totaling Page

Use the Rename Columns / Totaling page to rename the table or HGrid columns that are displayed in your personalized view, to display a total for a column.

Note: You can find more information about using this page in the User-Level Personalization User Interface chapter.

Rename Columns / Totaling page

the picture is described in the document text

  1. You can change the Column Names for the columns you chose to display.

  2. You may check Show Total to turn on totaling for a specific column in your table, if it is applicable to the underlying data.

    Tip: If you choose to display a column with totaling capabilities, you may want to display this column as the last column of the table. You can reorder the columns in the Columns Displayed list located on the previous page.

  3. If after you make changes to your columns, you decide you want to revert back to the default values, choose Reset to Defaults.

  4. Choose Apply when you are done to save your changes and return to the previous page.

Setting the Record Set Size for nodeDefinition under a HGrid

Setting the Record Set Size property for each nodeDefinition item defined under an HGrid.

An administrator can set the value for the Record Set Size property of each nodeDefinition to control the Record Set Size at each level.

To set the Record Set Size value:

  1. Navigate to the Personalize Page Hierarchy - Administrator Personalization page for the HGrid page to be personalized

  2. In the Personalization Structure HGrid, locate the HGrid to be personalized in the Name column

  3. For the HGrid, click on the Personalize icon for the nodeDefinition item for which the Record Set Size value needs to be set.

  4. In the Personalize Node Definition - Administrator Personalization page set the desired value for the Record Set Size property

  5. Select Apply.

Note the following:

Hiding the Save Search and Personalize Buttons

The Save Search button on the Search panel and the Personalize button can be shown/hidden through personalization.

Change Display Size for Various TextInput fields

The Administrator is able to change the display size of the following TextInput fields;

Personalization is done by setting the value for the Length property.

  1. Click on the personalize page link on a page containing the TextInput.

  2. Click on the personalize icon next to the TextInput in the Personalization structure HGrid.

  3. In the Personalize page set a new value for the Length property in the Personalization Properties table and click on the Apply button.

  4. Navigate back to the Application Page.

  5. The display length of the personalized TextInput should reflect the new value set through personalization

Adding Search Mappings

Search Mappings can be added through personalizations. A user can add a search mapping using personalization to a query region defined in the Auto Customization Criteria (ACC). The search mapping can be defined between fields already present in the simple search panel of the query region or added using personalization with fields present in the result table for the query region. The following two corollary requirements have also been added to enhance the user experience while adding a search mapping using personalization.

While defining the search mapping, the ids of the columns in the result table of the query region are displayed in a poplist.

If using an id of the column to be used in the mapping and entering the same in a text input field, a search mapping can be created between fields (one from the search panel and one from the result table), however, a validation message will be displayed if there are incompatible datatypes.

Add a field to the simple search panel using personalization using the following steps

  1. Click on “Personalize Page” link.

  2. Click on “Create item” icon in the Message Component Layout present in the Simple Search panel.

  3. In the Create Item page, select the Item and set the id and prompt.

  4. Click on Apply button

Create search mapping using the Admin Personalization UI

  1. Click “Create Item” icon for Simple Search mappings

  2. Enter id, Result Item id and Search Item id

  3. Click on “Apply” button

  4. Click on “Return to Application” link

  5. Perform the search.