Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
Recognising an unsupported request
Lesson 125 of 177 · 2 min
Four shapes of request that cannot be built inside the boundary, and how to say so with an ALTERNATIVE rather than a refusal. ONE: "change what this delivered process does". A different calculation, a skipped step, an altered posting rule. The boundary is that Oracle owns the process logic. The alternative is usually configuration you have not found yet — ask the functional consultant before concluding — or a separate step around it. TWO: "write to the database directly". A fix script, a bulk correction, a trigger. Not available, and Module 1 says why. The alternative is the supported interface for that object, or a file load. THREE: "make this field behave differently" — conditionally required, defaulted from another record, validated against something else. Page Composer cannot; a flexfield with a value set sometimes can; Application Composer can where it applies. The honest answer names which of the three, and…
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