OA Framework Personalization Caveats

This appendix covers the following topics:

Overview

This appendix lists the personalization caveats you should be aware of when modifying and patching pages.

All IDs must be unique. If an ID is already being used in the base definition of a page, do not use it again for new items or regions that you create. To reinforce this rule, you should add an intelligible prefix to your IDs to keep them in a separate namespace from any Oracle-seeded IDs.
A personalization that is inadvertently hidden due to an ID change of the base definition, may reappear if you create a new item with the same ID as that referenced by the personalization.
Certain types of personalizations may not appear "correctly" because of the nature of specific web beans in the page (particularly "default renderers").

Note: Default single column regions will not allow a button to be added at the top of the region even if the entities in the region are reordered to put the button at the top.