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
No comments:
Post a Comment