The Choose Personalization Context page is launched when you select the Choose Context button from any of the personalization launch pages.
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.
Additional Information: 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.
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.
Once you finish setting your personalization context, choose Apply. Choosing Cancel returns you to the previous page.
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.