Explain Page Composer and Visual Personalization in Oracle Applications

29 / 60

Fusionintermediate

Page Composer and Visual Personalization

Explain how Fusion allows UI-level personalization of standard pages without custom code

Page Composer is Fusion's browser-based tool for visually modifying the layout and behavior of standard application pages — showing/hiding fields, rearranging regions, adding custom text or links, and adjusting basic UI properties — all without touching the underlying ADF page source code. It operates at different scopes: Site level (affects all users), or scoped to a specific role, allowing different personas to see tailored layouts of the same underlying page.

Page Composer is like rearranging furniture in a rented apartment using only movable pieces the landlord allows — you can rearrange, hide, or relabel things within the room's given walls, but you can't knock down a wall (that requires true structural renovation, i.e., JDeveloper customization).

Key Concepts

Unlike Application Composer (which changes data model and business logic), Page Composer is purely about presentation — reordering fields, changing labels, hiding irrelevant sections for a particular role, or embedding a custom URL/iframe region. It's the conceptual descendant of EBS Forms Personalization, but operating on Fusion's ADF-based, browser-native UI rather than Java Forms applets.

A key nuance is the distinction between page-level personalization (through Page Composer, generally end-user or administrator-driven, reversible, layered) and true page customization via JDeveloper/MDS (used for deeper structural changes beyond what Page Composer's declarative tools support), which requires actual development skills and a more formal deployment process similar to traditional custom code.

page-level personalizationpage customization

Interviewers often ask candidates to distinguish between Page Composer personalization (safe, declarative, role-scoped) and full ADF page customization via JDeveloper (more powerful but requires developer involvement and structured deployment) — mirroring the EBS distinction between Forms Personalization and CUSTOM.pll/form modification.