Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
What breaks: three extension failures
Lesson 135 of 176 · 3 min
AN UNSUPPORTED CHANGE THAT SURVIVED FOUR UPDATES AND NOT THE FIFTH, AN EXTENSION AND A SANDBOX THAT OVERWROTE EACH OTHER, and ONE NOBODY COULD ATTRIBUTE. THE UNSUPPORTED CHANGE IS THE ONE WHOSE SURVIVALS WERE THE PROBLEM. Built against internals, worked immediately, and survived four quarterly updates — each survival read by somebody as evidence that the concern was theoretical. Lesson 2, and by the fifth it is deeply embedded, several people depend on it, and nobody remembers it was ever a risk. WHICH MAKES THE BREAK EXPENSIVE IN A WAY AN IMMEDIATE FAILURE WOULD NOT HAVE BEEN. A year of use, no support position, and a fix required in an update window nobody scheduled for it — where failing on the first update would have cost an afternoon and a decision. THE EXTENSION AND THE SANDBOX THAT OVERWROTE EACH OTHER IS THE ONE WHERE NOBODY DID ANYTHING WRONG. A functional…
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