Oracle Visual Builder: Applications That Outlive Their First Release · Module 1 · What VBCS is, and when you need it
Personalisation first: what you already have
Lesson 8 of 176 · 2 min
Page Composer and Application Composer cost A FRACTION of an application and are SUPPORTED THROUGH UPDATES. What they can and cannot express. These are the tools that make most Visual Builder requests unnecessary, and the second half of that sentence is the argument. "SUPPORTED THROUGH UPDATES" IS THE PROPERTY THAT MATTERS MOST AND IS THE ONE NOBODY WEIGHS. A personalisation is applied to Oracle's page and survives a quarterly update because Oracle designed the mechanism to. An application is yours, and every quarter it has to be tested — Lesson 6, and Module 17 in full. PAGE COMPOSER CHANGES WHAT AN EXISTING PAGE LOOKS LIKE. Hide fields, rearrange, change labels, add simple content, and do all of it per role. That covers the "simplified screen for one role" request almost entirely — Lesson 2's second case — and it takes an afternoon rather than a project. APPLICATION COMPOSER GOES FURTHER…
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