Tailor, Customize, Extend, Personalize, Localize, and Integrate – All Explained

To improve the management and support of solutions developed on top of the Fusion Applications platform we have found it sensible to use some upfront definitions, especially as it’s common to have many stakeholders involved in such projects. So here are our recommended definitions:

  • Tailoring was defined by the Oracle Applications User Experience team as a parent term under which all the different types of modifications occur. This is logical and the Fusion Applications Developer Relations will use the same umbrella term.
  • Customizing was traditionally based on making changes to the standard code artifacts. In Fusion Applications however many of the artifacts support both design-time and run-time changes, such as editing a BPEL processes to support your own business tasks, or using Page Composer to add new visual components for the users of one Business Unit. As such making a hard distinction between a customization or an extension project is just not very practical anyone, as most will contain elements of both. Obviously what you can actually change does vary as well, since uncompiled source code is not provided and some access may be restricted by your deployment model.
  • Extending in theory is focused on adding new code artifacts to create new features, than changing what currently exists. As mention above however, in practice some tasks involve adding new objects to change existing features, and changing attributes to add new features. As such both customization and extension may be used interchangeably.
  • Personalizing is the process of making simple system changes, normally to the look-and-feel, and that apply only to one specific user. This is usually done by the user themselves within the embedded preferences and settings. Fusion Applications leverages features from Oracle WebCenter to support a wide range of personalization options.
  • Localizing is the process of changing the functionality based on a specific regional context. It is used to include special language translations. There are many examples of different countries and regions requiring adjustments or extensions to the standard functionality, such as the varied tax legislation’s that govern the way to correctly process payroll. Oracle provides many localization solutions already (see the product implementation guides), however niche requirements or smaller regions may need the support of additional modifications.
  • Integrating is the process of sharing data from one application with another application. Oracle Enterprise Repository (public instance) contains a complete library of Fusion Applications integration assets with which to build solutions. Integration may be configured within the application itself such as for Oracle B2B integration of business transactions, or built out as an extension such as calling a third party tax calculation webservice.

Post a Comment:
  • HTML Syntax: NOT allowed

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.


« November 2015