Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
Page Composer: what it can change
Lesson 120 of 177 · 2 min
The genuinely useful subset is small and covers most of what people ask for. REORDERING fields and regions so the sequence matches how the work is actually done. HIDING what this organisation does not use — the single highest-value change available, because a form with forty irrelevant fields is a form people fill in wrongly. RELABELLING so the screen uses the client's vocabulary rather than Oracle's. And ADDING SIMPLE FIELDS, which in practice means surfacing a flexfield you defined elsewhere. THE CHANGES THAT LOOK AVAILABLE AND ARE NOT are where an afternoon goes. Moving a field between regions that belong to different underlying structures. Changing the behaviour of a control rather than its appearance. Making a delivered required field optional, or the reverse. Restructuring a page into a layout the framework does not offer. The tell is that you are trying to change what the page DOES rather than what…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Extensions: sandboxes, Page Composer and the boundaries
- 1What a sandbox is, and what it is notFree preview
- 2Publishing, and the point of no return
- 3Page Composer: what it can change
- 4Descriptive and extensible flexfields
- 5Value sets and validation
- 6Application Composer versus Page Composer
- 7Visual Builder: where it fits
- 8Recognising an unsupported request
- 9What breaks: extensions and quarterly updates
- 10Lab briefing · Extend a page and survive an update