Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
What breaks: extensions and quarterly updates
Lesson 126 of 177 · 2 min
Personalisations that survive, ones that are silently dropped, and the regression test that tells you which is which before users find out. WHAT SURVIVES RELIABLY: flexfields and their value sets, and Application Composer objects and fields. These sit on published extension points, and Oracle carries them forward deliberately. WHAT IS EXPOSED: page personalisations that depend on the page's structure. Hiding a field is robust; a change anchored to a region that was reorganised is not — and when the anchor no longer exists, the personalisation is dropped. Silently: the page renders, correctly, in its delivered form. Nothing errors and nobody is told. That silence is the whole problem. A hidden field reappears; a relabelled one reverts to Oracle's wording; a reordered form goes back to the delivered sequence. Users notice within a day and report it as a defect introduced by the update, which it is. THE REGRESSION TEST IS…
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