Form Personalization
This document describes the use of the Form Personalization feature, which allows you to
declaratively alter the behavior of Forms-based screens.
The following topics are covered:
Overview
Using the Personalization form
Limitations
Examples and Tips
Administration Window
Moving Personalizations between instances
Relationship to CUSTOM library
Relationship to Folder
Troubleshooting, Support, and Upgrade considerations
Changes to Form Personalization in 11.5.10 CU1
Changes to Form Personalization in 11i.ATG_PF.H Rollup 3 (Patch 4334965)
Changes to Form Personalization in 11i.ATG_PF.H Rollup 4 (Patch 4676589)
Overview
The Form Personalization feature allows you to declaratively alter the behavior of Forms-based
screens, including changing properties, executing builtins, displaying messages, and adding
menu entries.
For each function (a form running in a particular context based on parameters passed to it), you
can specify one or more Rules. Each Rule consists of an Event, an optional Condition, the Scope
for which it applies, and one or more Actions to perform.
An Event is a trigger point within a form, such as startup (WHEN-NEW-FORM-INSTANCE), or
when focus moves to a new record (WHEN-NEW-RECORD-INSTANCE). There are standard
events that almost every form sends, and certain forms send additional product-specific events.
The Scope is evaluated based on the current runtime context to determine if a Rule should be
processed or not. The Scope can be at the Site, Responsibility, User, or Industry level. Each Rule
can have one or more Scopes associated with it.
NOTE: the scope of 'Industry' is reserved for future use.
The Condition is an optional SQL code fragment that is evaluated when the Event occurs; if it
evaluates to TRUE then the Actions are processed.
Each Action consists of one of the following:
setting a Property, such as making a field Required or hiding a Tab page
executing a Builtin, such as GO_BLOCK, DO_KEY or FND_FUNCTION.EXECUTE
displaying a Message
enabling a Special menu entry
Once Rules are defined, when the target function is run then the Rules are automatically applied
as events occur within that form.
Although the Form Personalization feature is declarative, the intended audience is a person
familiar with Oracle Forms including the PL/SQL programming language, and the Oracle
Applications Development Guide. Additionally, any change made could interfere with the base
code of a form (the code that Oracle ships), thus the Support statements discussed later in this
chapter must be followed diligently.
