All topics
29 / 60
Fusionintermediate

Page Composer and Visual Personalization

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

Page Composer changes how a delivered page looks. It is presentation only — no data model, no logic.

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

1
    hide a field that this team never uses
    reorder the fields into the order they are entered
    change a prompt to the business's own wording
    add a link or an embedded region
2
The division of labour with Application Composer.
    Application Composer   the data and the logic: fields, objects,
                           validation, triggers
    Page Composer          the layout: what appears, where, for whom
3
Adding a field is Application Composer. Deciding where it sits on the page is Page Composer. Most real changes use both.
4
Scope is what makes it useful. A change can apply to everyone, or to a specific role:
5
    site level    everyone sees it
    role scoped   only that job role sees this layout
6
So a page can be dense for a specialist and stripped down for an occasional user, from one underlying definition. EBS approximated this with responsibility-scoped personalizations.
7
Changes are made in a sandbox, tested and published, exactly as with Application Composer.
8
The deeper option, and the distinction interviewers want.
    Page Composer          declarative, in the browser, reversible,
                           role-scoped. No developer.
    JDeveloper / MDS       actual ADF customisation, for structural
                           changes Page Composer cannot express.
                           A developer, and a deployment process.
9
This mirrors the EBS distinction between Forms Personalization and CUSTOM.pll: a light declarative tool for most things, a heavier one that requires skills and a release process.
10
And the same guidance applies. Try the declarative tool first. Reaching for JDeveloper for something Page Composer handles means a deployment cycle, a developer, and a customisation to revalidate at every quarterly update.
11
What it cannot do. It cannot make a page do something new. Rearranging, hiding and labelling are the scope. A requirement to compute something, call something, or behave conditionally belongs in Application Composer or beyond.
12
What the interviewer is probing.1. "What is the difference between personalisation and customisation here?" Probing: the vocabulary. Stalls: "Nothing." Moves up: personalisation is a user changing their own view; customisation through Page Composer applies at a role or site level.
13
2. "What should you be careful about?" Probing: the upgrade angle. Stalls: "Nothing." *Moves up:* changes can be invalidated by a quarterly update if the underlying page changes, so they need retesting each cycle.
14
3. "What can you actually change?" Probing: the scope. Stalls: "Everything." Moves up: layout, visibility, labels and adding limited components — not the underlying processing.
15
4. "How do you keep track of what has been changed?" Probing: the governance. Stalls: "You remember." Moves up: a maintained register of customisations per page and role, because there is no diff to inspect after an update.
Use cases:page-composermdspersonalizationadf-ui