Why personalization?
* Oracle Supports personalization unlike customization
* Personalizations are stored in tables rather than files
* Will not have a bigger impact when you upgrade or apply patches to the environment
* Can be moved easily through FNDLOAD from one instance to other
* Can be restricted at site/responsibility/user level
* Easy to disable/enable with click of a button.
* Personalization will store who columns with which we have the ability to track who created/modified it where as in CUSTOM.PLL we don’t have that ability.
* Can be applied to new responsibilities/users easily.
* Can be restricted to function or form.
What can be done through personalization?
* Zoom from one form to another
* Pass data from one form to another through global variables
* Change LOV values dynamically
* Enable/Disable/Hide fields dynamically
* Display user friendly messages when required
* Launch URL directly from oracle form
* Execute PL/SQL programs through FORM_DDL package
* Call custom libraries dynamically
What is Forms Personalization? Where it is used? What For?
Forms Personalization is a standard feature provided by oracle and supported by oracle to customize the forms. With Forms personalization you can hide fiedls, make fields mandatory, create zoom functionality, change lov dynamically e.t.c
What are different triggers that can be used in personalization?
WHEN-NEW-FORM-INSTANCE WHEN-NEW-BLOCK-INSTANCE WHEN-NEW-RECORD-INSTANCE WHEN-NEW-ITEM-INSTANCE WHEN-VALIDATE-RECORD MENUS SPECIAL EVENTS
Can you use global variables in forms personalization? If so How?
Yes.
Can you hide a text field using personalization? How?
Yes. In the actions set DISPLAYED property to false.
Can you transfer the data from one form to another form using personalization?
Yes. Using global Variables.
At what level you can restrict personalization code?
FORM level and FUNCTION level
* Oracle Supports personalization unlike customization
* Personalizations are stored in tables rather than files
* Will not have a bigger impact when you upgrade or apply patches to the environment
* Can be moved easily through FNDLOAD from one instance to other
* Can be restricted at site/responsibility/user level
* Easy to disable/enable with click of a button.
* Personalization will store who columns with which we have the ability to track who created/modified it where as in CUSTOM.PLL we don’t have that ability.
* Can be applied to new responsibilities/users easily.
* Can be restricted to function or form.
What can be done through personalization?
* Zoom from one form to another
* Pass data from one form to another through global variables
* Change LOV values dynamically
* Enable/Disable/Hide fields dynamically
* Display user friendly messages when required
* Launch URL directly from oracle form
* Execute PL/SQL programs through FORM_DDL package
* Call custom libraries dynamically
What is Forms Personalization? Where it is used? What For?
Forms Personalization is a standard feature provided by oracle and supported by oracle to customize the forms. With Forms personalization you can hide fiedls, make fields mandatory, create zoom functionality, change lov dynamically e.t.c
What are different triggers that can be used in personalization?
WHEN-NEW-FORM-INSTANCE WHEN-NEW-BLOCK-INSTANCE WHEN-NEW-RECORD-INSTANCE WHEN-NEW-ITEM-INSTANCE WHEN-VALIDATE-RECORD MENUS SPECIAL EVENTS
Can you use global variables in forms personalization? If so How?
Yes.
Can you hide a text field using personalization? How?
Yes. In the actions set DISPLAYED property to false.
Can you transfer the data from one form to another form using personalization?
Yes. Using global Variables.
At what level you can restrict personalization code?
FORM level and FUNCTION level
No comments:
Post a Comment