Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
What a sandbox is, and what it is not
Lesson 118 of 177 · 2 min · Free preview
A sandbox is an isolated SET OF CHANGES you can publish or discard. It is not a separate environment, and it is not a backup. Those two misreadings cause most of the trouble in this module. NOT AN ENVIRONMENT. You are still in the same instance, against the same data. A sandbox captures configuration changes, not transactions — so anything you do to actual records while inside one is real and stays real when you discard. NOT A BACKUP. Discarding a sandbox reverses what the sandbox holds, and nothing else. It cannot undo a change somebody made outside it, and it cannot undo a published sandbox. WHAT IS CAPTURED: page personalisations, flexfield definitions, Application Composer objects and fields, and the other configuration the tooling explicitly places in a sandbox context. WHAT LEAKS AROUND IT is the part to internalise, because it is the source of every surprise here. Value set…
This lesson is free
Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.
Watch the full lessonIn 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