1] User can only change what Oracle Forms allows at run time. For example, the following cannot be changed:
- User cannot create new items
- User cannot move items between canvases
- User cannot display an item, which is not on a canvas (thus, individual flexfield segments cannot be displayed)
- User cannot set certain properties such as the Data type of an Item.
- User cannot change frames, graphics, or boilerplate
- User cannot hide the item that currently has focus
[2] Form Personalization can only respond to events that are centrally processed and dispatched by APPCORE. These are limited to:
- WHEN-NEW-FORM-INSTANCE, WHEN-NEW-BLOCK-INSTANCE, WHEN-NEW-RECORD-INSTANCE, WHEN-NEW-ITEM-INSTANCE. These events occur as the user moves focus within the form.
- WHEN-VALIDATE-RECORD (in many but not all forms). This event occurs whenever changes have been made to the current record in the current block.
- SPECIAL1 through SPECIAL45. These occur when the user selects entries from the Tools, Reports and Actions drop down menus.
- Product-specific events. These are typically documented in implementation manuals, such as 'Configuring, Reporting and System Administration in Oracle HRMS'.
- Form Personalization can only respond to events that are centrally processed and dispatched by APPCORE. These are limited to:
WHENNEW-RECORD-INSTANCE
should read
WHEN-NEW-RECORD-INSTANCE
[3] User can see only the events that are being passed by enabling the 'Show Events' option in the Custom Code menu.
[4] Certain personalization must be performed at specific events:
[4] Certain personalization must be performed at specific events:
- To specify the Initial Value of an Item, user must perform that action in the WHEN-NEW-RECORD-INSTANCE event of the block that contains the item.
- Special menu entries can only be created at form start up (WHEN-NEW-FORM INSTANCE)
