Oracle Fusion provides the below tools to customize and extend Fusion Applications at design and runtime
- Page Composer
- CRM Application Composer
- Oracle SOA Composer
- Oracle JDeveloper
- Business Process Composer
Fusion Applications implements a sandbox framework, whereby all Composer changes can be first made and stored in a virtual sandbox environment of your choosing. This ring-fences them so they can be safely tested and verified, whilst invisible to other users on the live system. Once complete they can be published one at a time or all together into the system for general use.
All supported customizations and extensions are stored and applied in the context of a Meta Data Services (MDS)Layer. MDS defines the context for which the customization will be applied over the standard features at runtime. Some commonly used examples of MDS layers are a User, a Job Role, an Organization, or across a whole Site.
The composers are generally intended for Super User, Domain Manager, or Business Analysts type roles, with standard Personalization (with a few features from Page Composer) serving the needs of end users. For more extensive and invasive technical projects a connection between a local JDeveloper IDE (with the required setup) and a Fusion Applications instance is required. The tools to use for each type of activity are highlighted in the Fusion Applications Extensibility Guide.
1. Page Composer
End user / Business Analyst can personalize the UI at run time, they can rearrange certain objects on the page, changing the width of the field, saving search parameters are called composer based personalization.
All supported customizations and extensions are stored and applied in the context of a Meta Data Services (MDS)Layer. MDS defines the context for which the customization will be applied over the standard features at runtime. Some commonly used examples of MDS layers are a User, a Job Role, an Organization, or across a whole Site.
End user / Business Analyst can personalize the UI at run time, they can rearrange certain objects on the page, changing the width of the field, saving search parameters are called composer based personalization.
- Change a Page Layout for one or more users
- Discover, Implement, and Add Seed Data to Flexfields
- Add a new Field onto a page
2. CRM Application Composer
CRM Product Family has one additional composer, the CRM Application Composer, providing more advanced functionality for creating custom business objects and actions.
Where basic options like flexfields are not enough to support the additional data attributes required for your business operation, the Data Composer (Available only in CRM Application Composer) allows access to edit and create ADF Business Objects. Just to be clear, these are not new database fields or records, but the abstraction of them based on real-world entities, such as Purchase Orders or Customers. It is the ADF Business Objects that are used at runtime by the user interface.
