It's All About the Platform.

Tailoring Fusion Applications in the Cloud Explained (updated)

Richard Bingham
Senior Development Manager
This is a reboot of our original post which was written some time ago (based on Release 5), and therefore adds in new capabilities and features. Due to the many comments and questions we've seen on this topic we hope this remains a useful reference. This version is based on Release 9.

The following is a short list of activities that are commonly part of tailoring an Enterprise Application and provides confirmation if this is possible for an Oracle Cloud SaaS deployment. Where Application Composer (App Composer) is explicitly mentioned then this is required to accomplish the task.

Category Task Available
Flexfields Use descriptive and extensible flexfields Y
  Import flexfield seed data Y
  Include flexfields in reports and analytics Y
  Migrate flexfields from test to production Y
Edit or add SOA Composite Applications N
  Edit existing Approval Rules Y
  Add new approval processes to existing BPEL processes N
  Edit BPM Processes for Approvals (App Composer) Y
  Use all standard AMX routing options (many but not every one) N
  Customize all workflow notification content N
BI & Reporting Add-to or edit the seeded BI Publisher reports Y
  Add-to or edit the seeded BI Analytics reports Y
  Edit the existing charts embedded in pages N
  Add new all reports content to the custom folder of the BI Catalog Y
  Expose new reports in dashboard and landing pages Y
  Customize the existing Subject Areas N
  Include custom fields in Subject Areas (App Composer) Y
  Custom schedule/deliver to email, webcenter content, and FTP folder Y
ESS Add a report to an new job definition Y
  Add code for a new job program N
  Schedule a new job definition Y
  Edit the input parameters for an existing job definition N
  Edit the application logic to use an alternative job definition N
  Call a web service to import data and execute associated jobs Y
General UI Change the look-and-feel (colors, fonts etc) across the application Y
  Customize all title texts, field labels and response messages Y
  Make an ADF component customizable or personalizable N
  Customize the Navigator Menu and Homepage Menu Y
  Translate your text values used in customization Y
  Add new objects and fields and expose them on a new page (App Composer) Y
  Add new buttons and links to existing pages (App Composer) Y
  Conditionally display/make-required/set-values for fields and components Y
  Add custom data validation to existing standard fields (App Composer) Y
  Pass context data to an iframe containing another application (App Composer) Y
  Get a direct URL (deep-link) to a specific page and transaction (App Composer) Y
  Change the seeded ADF task flows N
  Add an entirely new blank ADF page N
  Change and extend the User Assistance / Help content Y

SUI/ Mobile

Change the reports available in mobile apps (App Composer) Y
  Edit mobile-specific pages (App Composer) Y
  Add a new Simplified UI card (App Composer) Y
Coding Add expressions (EL) to page components to set their properties at run-time Y
  Run code (Groovy) based on record creation/update/delete events (App Composer) Y
  Add custom event points within existing process flows N
  Upload/deploy your custom code (or other libraries) to the SaaS environment N
  Access the Operating System or run direct database queries (DDL or DML) N
  Call the Fusion Applications web services from a remote application Y
  Add code to call any remote web service and use the response (App Composer) Y
  Add custom HTML and Javascript to a new dashboard/landing page region Y
  Add custom HTML and JavaScript to any page/region N




The table above is intended to answer some of the more common questions on what you can and cannot do in a SaaS-Cloud deployment of Fusion Applications. Of course there are many more options and features available than are listed here, and many of the items currently not possible are being developed for a future release. If you have business cases for any of these please let us know.

A more comprehensive list of what you can do with each of the Fusion Applications tools (Composers and JDeveloper) is provided in Tables 1-2 to 1-8 in Chapter 1 of the Fusion Applications Extensibility Guide.

Join the discussion

Comments ( 3 )
  • Sujoy Thursday, April 9, 2015

    Hi Richard,

    Thanks for the list. However, I have a slight confusion here.

    Under the General UI, you mention that the following task cannot be accomplished:

    Add custom data validation to existing standard fields

    But I think we can use Groovy scripts in the Application Composer to achieve this task. In fact the FA Dev Youtube channel even has a video on this https://youtu.be/mQd5ojEmy8E?list=PL1ZiAfFIniZf_Uu4qTcp5IZYdFOm9K5o3

    Is my understanding correct?



  • Richard Bingham Thursday, April 9, 2015

    Hi Sujoy

    You are right, when I put in that line I was thinking outside of Sales Cloud however appending "(App Composer)" means I can set this to "Y" due to the use of its Validation Rules.

    Thanks for pointing this out.


  • Sujoy Thursday, April 9, 2015

    Thanks for confirming Richard!

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.