Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
When to stop extending
Lesson 134 of 176 · 3 min
The point at which AN EXTENSION HAS BECOME AN APPLICATION, and SHOULD BE ONE. Extensions grow the way action chains grow — one reasonable addition at a time — and nobody notices the point at which the thing stopped being an extension. THE FIRST SIGNAL IS SCREENS OF ITS OWN. An extension adding a field to a page is an extension. One with four pages, its own navigation and its own workflow is an application that happens to be launched from a Fusion page — and the user is no longer in the Fusion page in any meaningful sense. THE SECOND IS DATA OF ITS OWN. Business objects, its own records, its own lifecycle. At that point Fusion is a data source rather than a host, which is exactly the relationship a standalone application has. THE THIRD IS THAT THE UPDATE CHECK KEEPS GROWING. Lesson 6's list is short for…
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