Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 12 · Extensions: sandboxes, Page Composer and the boundaries
Application Composer versus Page Composer
Lesson 123 of 177 · 2 min
Two tools with overlapping names and different reach, and the confusion genuinely costs an afternoon at least once per consultant. PAGE COMPOSER changes how a page LOOKS. It works across the delivered applications and it is a presentation tool: reorder, hide, relabel, expose an existing field. APPLICATION COMPOSER changes what OBJECTS ARE. New fields with behaviour, new objects, relationships, and Groovy logic — which is Module 13. It is genuinely more powerful and it applies to a NARROWER set of product families, principally the CX applications rather than the ERP and HCM ones. THAT LAST SENTENCE IS THE AFTERNOON. Somebody reads an Application Composer tutorial, plans an extension around it, and discovers the tool does not apply to the object they are extending. Check which tool applies to your product family BEFORE designing anything; it is one lookup and it decides what is possible. Where both apply, the division is…
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