We have a visual builder application that we develop locally using Visual Builder Studio. At our customer, we import the application into their cloud tenant using Visual Builder.
VBCS has a new release every few months and the most recent release is February 2025.
However, our VB environment only supports version 2410:
Release: 2410
Visual Builder Runtime Version: 2410.2.0
Oracle Jet Version: 16.1.4
While we can import the new release and it runs fine, whenever I have to come back to the VB UI, all options in the left nav menu such as webapps, services, business objects are missing and the only item rendered is files.
I have to replace visual-application.json with an older version:
{
"vbcs.dt.version": "20240618-24.10.1",
"dependencies": {
"upgrade": "micro",
"paths": {
"jet": "https://static.oracle.com/cdn/jet/16.1.4",
"telemetry": "https://static.oracle.com/cdn/trace/8.2.2",
"visualRuntime": "https://static.oracle.com/cdn/vb/2410.2.0",
"oracleImageGallery": "https://static.oracle.com/cdn/fnd/gallery/2410.0.3"
}
},
"source.version": "2410",
"rootURL": "conedsandbox",
"version": "2.0.0",
"migration": {
"2410": [
"MetadataRulesVersionMigrator"
]
}
}
and then reload the browser. I can import a new release and the UI stays complete. But when I go to log in later, it reverts back to showing just the “files” icon.
This is all rather shaky because we have to make sure that we don't stage the application while the older visual-application.json is in place.
It seems rather odd to me that Visual Builder is stuck with a version that is two releases behind Visual Builder. How long does it typically take for Visual Builder to catch up to Visual Builder studio?