Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
Sandboxes and coordination
Lesson 131 of 176 · 3 min
Working alongside FUNCTIONAL CONFIGURATION without EITHER OF YOU LOSING WORK. You are not the only person changing this environment, and the other people are doing configuration in sandboxes with a lifecycle of their own. A SANDBOX IS AN ISOLATED SET OF CONFIGURATION CHANGES THAT IS EVENTUALLY PUBLISHED INTO THE ENVIRONMENT. Several can exist at once, they can be published in any order, and until one is published its changes are invisible to everybody outside it. WHICH MEANS THE ENVIRONMENT YOU ARE DEVELOPING AGAINST IS NOT NECESSARILY THE ENVIRONMENT AS IT WILL BE. A field you rely on may exist because somebody's sandbox is active, and disappear when it is not — or arrive later when theirs is published, changing the page underneath your extension. SO THE FIRST RULE IS TO KNOW WHICH SANDBOX YOU ARE IN, IF ANY. Building against a page whose state comes from somebody else's in-progress configuration…
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