How Updates are Reflected in VertiGIS Studio Web Apps

If you have installed VertiGIS Studio Web on-premises, you may be wondering how upgrading to a newer version will carry over into your existing apps. Here is an outline of how it works:

1. Before upgrading, Web Designer and your apps are all on the original version.
2. You install an update of VertiGIS Studio Web which brings Web Designer to the updated version.
3. Post-update, if you don't open and save any of your apps in Web Designer, they are all still encoded as the original version. However, the runtime that processes them is on the updated version, so it converts them on-the-fly to the updated version when they are launched. This means the apps appear to be on the updated version for all intents and purposes.
4. You open an app in Web Designer and save it. This encodes the update to the app so that it runs on the updated version without on-the-fly conversion. This improves runtime performance and solidifies the upgrade, meaning the app can no longer be opened in a separate or rolled-back instance of Web Designer that is on the original version or older.
5. Higher deployment stages of the app are encoded as the original version and undergo on-the-fly conversion when launched until the app is saved and redeployed post-upgrade.

The above applies to SaaS apps as well, though upgrades are automatically applied to Web Designer the moment they are released.

Newer apps cannot be opened in older versions of Web Designer, so it is best to save backups of your apps using File > Download App in Web Designer prior to upgrading if you would like to have the ability to roll back an update.

In app deployment strategies that include multiple environments, the upgrade should be performed in each environment prior to deploying the app again.

For information on how updates to VertiGIS Studio Workflow are reflected in VertiGIS Studio Web apps, please see the following article: When is new functionality in Studio Workflow available in Studio Web?