Glance Cobrowse Upgrade Process
A Glance Cobrowse upgrade is a single setting change in the Glance database that determines what version/release of Glance Cobrowse the customer is running. The upgrade process is completed within a few seconds. Following the upgrade, it may take up to an hour for web caching to take place depending on when the visitor connects to the customer's website.
NOTE: Web caching does not involve nor is it controlled by Glance.
For example, visitors who connect to the customer's website for the first time experience the upgrade immediately because they do not have anything cached on their browser. However, if a visitor is on the customer's website minutes before the upgrade, the upgrade may take longer to propagate because the visitor has more recent cached data in their web browser. Additionally, this type of visitor is not impacted by the longer upgrade time because they will simply use the previously "working" version of Cobrowse while the upgrade is processing.
Glance CDN – Standard Implementation
You will be notified via email at least one week prior to the staging site upgrade. During this time, you may coordinate with Glance Support to set up user acceptance testing from your side and any included efforts from Glance as your MSA outlines. You will be given at least two weeks to validate the release before the upgrade is pushed to your production environment.
Upgrading the Self-hosted Cobrowse Script
Customers who host their own scripts will download the new scripts from the Glance CDN as described in Self-hosted Script, followed by updating the staging or production sites to reference the new scripts.