Explain Application Composer and Sandboxes in Oracle Applications

28 / 60

Fusionadvanced

Application Composer and Sandboxes

Explain Fusion's declarative extensibility model built on Application Composer and Sandbox-based change isolation

Application Composer is Fusion's primary tool for functional/technical consultants to extend the data model and business logic without writing traditional code — adding custom fields (similar in spirit to DFFs but configured through a much friendlier UI), custom objects, validation rules, and even simple workflow-triggered business logic, all through a browser-based designer. It's the spiritual successor to a mix of EBS's Flexfields, Personalization, and some custom PL/SQL use cases, unified into one tool.

Sandboxes are like a document's 'suggested edits' mode combined with a separate draft copy: multiple editors (developers) can work on their own draft version in isolation, and only when an edit is accepted (published) does it become part of the master document everyone sees.

Key Concepts

Sandboxes are Fusion's mechanism for isolating in-progress configuration and customization changes from the live production environment until they're tested and explicitly published. A developer or administrator creates a sandbox, makes all Application Composer, Page Composer, or security changes within it, and other users continue seeing the unmodified production experience until the sandbox is published — at which point changes become visible to everyone (or, with more granular control, to specific role-based visibility).

Sandboxes

This sandbox model solves a problem EBS never fully addressed: EBS Forms Personalization and CUSTOMd.pll changes were often difficult to test in true isolation without a fully separate environment, whereas Fusion sandboxes allow safe, git-branch-like parallel development directly within a single environment (though best practice still recommends testing in non-production pods before publishing to production).

Interviewers commonly ask candidates to explain the sandbox lifecycle (create, edit, test, publish or discard) and why publishing is a one-way, careful operation — since once published, changes affect all users and can only be undone by further changes, not a simple 'rollback' in the traditional sense.