|
Upgrading to Evolve Suite 2020.2
If you want to upgrade from an earlier version of Evolve Suite, then you should read this chapter carefully before installing any software.
|
|
If you are in any doubt about how to proceed with upgrading your copy of Evolve Suite, or any standalone components such as
Document Generator or V-Modeler, please contact the Quest support. |
In a multi-user environment, where more than one client machine accesses a networked Evolve Repository, you must upgrade all your clients. The user who upgrades the network databases must have administrator rights to the database as schema changes are required to upgrade to this version. Once a Evolve Repository has been used with a newer version of the client software, an older version of the client may not be able to correctly use the database.
NOTE ON PRODUCT COMPATIBILITY - EVOLVE, PORTAL, CMI, CORPORATE PUBLISHER, COLLECTOR & WEB SERVICES
|
|
Important:
Casewise Portal & Casewise Publisher are deprecated. There is no version of Portal or Publisher that runs with Evolve Suite 2020. Web Services are however compatible with CW Suite 2016 and can still be operated from a standalone server (that must NOT have Evolve Suite/Evolve 2020 installed on the same server). New JSON/REST based webservices are now available in 2018.1 and above, please ask Support.
|
If you are upgrading from Evolve Suite 2020.1 or earlier, and you use other Quest products, such as Evolve, Analytics (CMI), or Collector, then you will need to upgrade them at the same time as upgrading your Evolve Suite installation. Previous versions of these products will not work with this new version of Evolve Suite.
It is therefore necessary to take the time to plan your upgrade procedure to prevent users of one system trying to use it while another part is being upgraded. All components will need to be taken offline while they are all upgraded. Each of these components have their own installation guides which you should read before attempting to upgrade them.
|
