MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 17 · Quarterly updates and VBCS

Component and runtime versions

Lesson 166 of 176 · 3 min

What upgrading CHANGES, when you GET A CHOICE ABOUT IT, and THE DEPRECATION THAT BECOMES A REMOVAL. Some of what moves underneath you is on a schedule you can influence, and knowing which part is the difference between planning and reacting. WHAT UPGRADING CHANGES IS THE BEHAVIOUR OF THINGS YOU DID NOT WRITE. A component renders slightly differently, a default changes, an interaction behaves in a new way. Usually improvements, usually invisible, and occasionally a page that now looks or behaves wrong — Lesson 6's first failure. WHERE YOU GET A CHOICE, TAKE IT DELIBERATELY RATHER THAN BY DEFAULT. Being able to move at your own pace is genuinely valuable — it lets you test first and upgrade when you have time to look. AND THE TRAP IN HAVING A CHOICE IS STAYING BEHIND TOO LONG. Every version you skip is more change arriving at once when you eventually move,

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.

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 17 · Quarterly updates and VBCS

  1. 1Two calendars, not one
  2. 2Reading a release note for risk
  3. 3Component and runtime versions
  4. 4A regression pack for an application
  5. 5Testing in the update window
  6. 6What breaks: after the update
  7. 7Lab briefing · Assess a real release note