Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
Surviving a quarterly update
Lesson 133 of 176 · 3 min
What Oracle GUARANTEES, what it DOES NOT, and THE REGRESSION CHECK THAT RUNS IN THE UPDATE WINDOW RATHER THAN AFTER IT. Fusion is updated on a schedule, the environments are patched in a known order, and an extension is the thing in the estate most likely to notice. WHAT IS GUARANTEED IS THE SUPPORTED SURFACE. Documented extension points, REST APIs, the framework's own contracts — Lesson 2. Those are designed to survive an update and generally do. WHAT IS NOT GUARANTEED IS EVERYTHING ELSE ABOUT THE PAGE. Its structure, its internal identifiers, where a region sits, what a delivered component renders. An extension depending on any of that is depending on something Oracle may change in any release, correctly and without notice to you. AND THE HALF NOBODY PLANS FOR IS THAT SUPPORTED THINGS CAN CHANGE TOO. An attribute is deprecated, a resource gains a new version, a page is…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 13 · Extending Fusion applications
- 1Extending against building beside
- 2What an extension can change
- 3The workspace and the lifecycle
- 4Where this meets Page Composer
- 5Sandboxes and coordination
- 6Testing an extension
- 7Surviving a quarterly update
- 8When to stop extending
- 9What breaks: three extension failures
- 10Lab briefing · Extend, then update