MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 1 · What VBCS is, and when you need it

What breaks: the application that should not exist

Lesson 12 of 176 · 3 min

Two real shapes — A REBUILD OF A FUSION SCREEN THAT NOW NEEDS MAINTAINING FOREVER, and A DATA-LOADING TOOL THAT SHOULD HAVE BEEN AN INTEGRATION. THE REBUILT FUSION SCREEN IS THE COMMONEST APPLICATION THAT SHOULD NOT EXIST, AND IT ALWAYS STARTS SMALL. Somebody wanted a field added, or a page simplified, or a validation. An application was built that reproduces the Fusion screen with the change in it — and it works, and everybody is pleased, and it is delivered. WHAT THE CLIENT NOW OWNS IS A COPY OF SOMETHING ORACLE MAINTAINS. Every quarter, Oracle improves their screen and the copy does not change. Every field Oracle adds has to be added by hand; every validation Oracle changes has to be replicated; every API change breaks it — and the original request was one field, which Application Composer would have added in an hour and supported forever. AND IT GETS…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 1 · What VBCS is, and when you need it

  1. 1What the product actually is
  2. 2The four things people ask it to do
  3. 3When you genuinely need Visual BuilderFree preview
  4. 4Personalisation first: what you already have
  5. 5Visual Builder against APEX
  6. 6The maintenance bill nobody quotes
  7. 7Where it sits in the Oracle estate
  8. 8What breaks: the application that should not exist
  9. 9Lab briefing · Six requirements, one recommendation each