MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications

What an extension can change

Lesson 128 of 176 · 3 min

The scope of WHAT IS SUPPORTED, and the change that is TECHNICALLY POSSIBLE AND UNSUPPORTED — which is the one that HURTS IN A YEAR. The tooling will let you do more than Oracle will support, and nothing marks the boundary as you cross it. That gap is this lesson. WHAT IS SUPPORTED IS WHAT THE EXTENSION MODEL EXPOSES DELIBERATELY. Adding fields and regions in the places designed to receive them, adding pages, calling REST APIs, adding your own logic in the ways the framework provides. Those are contracts, and a contract survives an update by definition. WHAT IS UNSUPPORTED IS ANYTHING REACHING INTO THE DELIVERED PAGE'S INTERNALS. Selecting an element by whatever identifier it happens to have, altering a component Oracle owns, depending on the structure of markup you did not write. That is an implementation, and an implementation carries no promise at all. AND THE WHOLE PROBLEM 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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 13 · Extending Fusion applications

  1. 1Extending against building beside
  2. 2What an extension can change
  3. 3The workspace and the lifecycle
  4. 4Where this meets Page Composer
  5. 5Sandboxes and coordination
  6. 6Testing an extension
  7. 7Surviving a quarterly update
  8. 8When to stop extending
  9. 9What breaks: three extension failures
  10. 10Lab briefing · Extend, then update