Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
The workspace and the lifecycle
Lesson 129 of 176 · 3 min
How an extension is DEVELOPED, VERSIONED AND PUSHED, which is NOT THE SAME as publishing a standalone application. Module 15 covers publishing an application. This lesson exists because the extension lifecycle is a different one, and the differences are all about the fact that you are changing somebody else's environment. AN EXTENSION IS DEVELOPED AGAINST A SPECIFIC FUSION ENVIRONMENT, AND THAT COUPLING IS THE FIRST DIFFERENCE. A standalone application can be developed anywhere and pointed at a service later. An extension has to be built against the environment whose pages it extends, so you need a non-production Fusion environment before you can start — and getting one is somebody else's decision. VERSIONING IS TIED TO THE ENVIRONMENT'S OWN STATE, WHICH IS THE SECOND. An extension is developed against one release and deployed onto an environment that may have moved. So "which version of the extension" is only half the question;…
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