Oracle Visual Builder: Applications That Outlive Their First Release · Module 1 · What VBCS is, and when you need it
When you genuinely need Visual Builder
Lesson 7 of 176 · 3 min · Free preview
A screen that DOES NOT EXIST, for users who SHOULD NOT SEE THE FULL ONE, over data from MORE THAN ONE SYSTEM. IF NONE OF THAT APPLIES, SAY SO. Those three are the genuine cases, and a request that matches none of them almost certainly has a cheaper answer. A SCREEN THAT DOES NOT EXIST IS THE CLEAREST. The business has a process Fusion does not model — an approval with their own steps, a form for something the standard application has no concept of. There is nothing to personalise, because there is nothing there. USERS WHO SHOULD NOT SEE THE FULL SCREEN IS THE SECOND, AND IT IS STRONGER WHEN THEY ARE NOT FUSION USERS AT ALL. A warehouse operative, a field engineer, an external partner — people who need to do one thing and should not be given a Fusion licence and a sixty-field page. That is a…
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 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