Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
Publishing, and the point of no return
Lesson 119 of 177 · 2 min
Publishing merges a sandbox into the environment and CANNOT be reversed by discarding it. The sandbox is gone; the changes are live for every user. What to check first, in order. ONE: what is actually in it — the sandbox lists its changes, and a sandbox that has been open for three weeks usually contains something you forgot. TWO: does it still apply? A sandbox created before a quarterly update may carry a change to a page that has since changed. THREE: has anybody tested it as a real user, not as the person who built it. AND WHY TWO OPEN SANDBOXES TOUCHING ONE PAGE IS A PROBLEM. Each is isolated from the other, so each looks correct in its own context. Publishing the first, then the second, does not merge them intelligently — the second was built against a version of the page that did not include the first,…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Extensions: sandboxes, Page Composer and the boundaries
- 1What a sandbox is, and what it is notFree preview
- 2Publishing, and the point of no return
- 3Page Composer: what it can change
- 4Descriptive and extensible flexfields
- 5Value sets and validation
- 6Application Composer versus Page Composer
- 7Visual Builder: where it fits
- 8Recognising an unsupported request
- 9What breaks: extensions and quarterly updates
- 10Lab briefing · Extend a page and survive an update