Personalizations Vs Extensions in Oracle OAF

Personalizations do not involve the use of JDeveloper Tool Extensions involve the use of Jdeveloper  Personalizations are for simple modifications to the web pages. Example of common personalizations are rendering, read only, making required, and changing prompt. Personalizations can be accomplished by Functional Users also but for Extensions user should have knowledge on Basics of Java and MVC architecture. Extensions often involve the use of Personalizations. Steps for OAF Personalization: Click on Personalize page link --> find item --> click on Personalize icon for the item --> Select item property to modify --> Modify appropriate level with new setting. Personalizations can be used to create a Button or Link with a URL as a destination. Personalizations can be used to create an Export Button which allows exporting of table data. Personalizations can not create a Submit Button. An extension would be needed to create a Submit Button and the logic to handle the submit process.  Personalizations can be used to add FlexFields to a page. Personalizations can specify which segments of a flexfield to display (independent of the flexfield definition) Extensions are needed to default values in a flexfield. Extensions are needed to make specific segments of a flexfield conditionally mandatory, independent of the flexfield definition.