Oracle Visual Builder: Applications That Outlive Their First Release · Module 1 · What VBCS is, and when you need it
The four things people ask it to do
Lesson 6 of 176 · 3 min
A screen Fusion does not have, a simplified screen for one role, a mobile front end, and an extension to a Fusion page. ONLY TWO OF THEM USUALLY NEED THIS. Those four cover almost every Visual Builder request, and separating them is the most valuable thing in this module. A SCREEN FUSION DOES NOT HAVE IS THE STRONGEST CASE AND IS GENUINELY WHAT THIS TOOL IS FOR. A process the standard application does not model, data from more than one system on one page, an interface for people who are not Fusion users at all. Nothing else can produce it. A SIMPLIFIED SCREEN FOR ONE ROLE IS THE SECOND, AND IT IS CONTESTABLE. Somebody who needs three fields from a page that has sixty. Often that is Page Composer's job — Lesson 4 — hiding what a role does not need, at a fraction of the cost and supported through…
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 1 · What VBCS is, and when you need it
- 1What the product actually is
- 2The four things people ask it to do
- 3When you genuinely need Visual BuilderFree preview
- 4Personalisation first: what you already have
- 5Visual Builder against APEX
- 6The maintenance bill nobody quotes
- 7Where it sits in the Oracle estate
- 8What breaks: the application that should not exist
- 9Lab briefing · Six requirements, one recommendation each