Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
Extending against building beside
Lesson 127 of 176 · 2 min
Two answers to "WE NEED SOMETHING FUSION DOES NOT DO", with VERY DIFFERENT COSTS AT THE NEXT UPDATE. Extending means adding to a Fusion page — the user stays inside Fusion and sees something that was not there. Building beside means a separate application the user navigates to. Both are legitimate and the choice is usually made by whoever is asked first. EXTENDING WINS ON EXPERIENCE, AND THAT IS A REAL ADVANTAGE RATHER THAN A COSMETIC ONE. The user is already in the record, already in context, already authenticated as themselves. No navigation, no second application to learn, and no question about which system is authoritative. BUILDING BESIDE WINS ON INDEPENDENCE, AND THAT IS ABOUT THE UPDATE. Your application depends on Fusion's APIs, which are versioned and stable. An extension depends on Fusion's PAGES, which change every quarter — and the difference between a contract and an implementation is the…
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