Oracle Visual Builder is an Oracle managed service, which means that Oracle takes care of updating the service for you. As a user you don't need to do anything to get the latest version applied to your server. One request we got from customers is to have the ability to upgrade their environments in stages, and now you can better control the timing of upgrade for each instance.
The common scenario is having two Visual Builder instances – one for development and one for production. The customer might prefer to apply updates to the development instance first and delay the updates to the production instance. This will allow them to test their application with the new versions of the VB Runtime/Server and Oracle JET libraries. A new setting in the VB instance setting page allows you to choose which instance will get updated when.
Updates to Visual Builder instances are done in two patching windows, you can choose if you want to get a specific instance updates in the first window (earlier) or the second one (later). The windows are typically two weeks apart. If for example you choose window1 for dev instance and window2 for the prod instance. You'll have a couple of weeks to test your app in the dev instance before we apply the updates to the prod instance for you.
More info in our administrator documentation.
As a reminder, Oracle Visual Builder has an official upgrade policy that aims to keep your app on the latest and greatest set of libraries to help you keep your apps secure and performant. So, you should build into your schedule a slot to take care of upgrading your apps libraries to take advantage of the new features.
By the way, if your Visual Builder instance is part of your Oracle Integration Cloud instance there is a separate way to define the update cycle – see the integration doc.