Database Upgrade for 3.0

GlobalCapture 3.0 introduces a number of new database driven features that require updates to the database and historical data within it. Upgraded databases can not be reverted without a valid backup. Ensure you have a good backup BEFORE beginning the upgrade.

The database upgrade is straight forward, but may be time consuming for customers with very large and/or unmaintained process collections. The database upgrade runs as part of the GlobalCapture upgrade process, but can also be run manually after the software upgrade if the default settings do not encompass all required data points.

After a good backup of your MongoDB database has been confirmed, run the GlobalCapture setup file. The following upgrade steps are performed. Note, an upgraded database CAN NOT function with a version of GlobalCapture prior to 3.0.

The MongoDB workflows and processes collections will be renamed.
New workflows and processes collection are created.
Workflows are migrated.
The upgrade process will execute, moving updated processes into the new process collection.
Upgrade events are logged to a text file prefixed with “schemaUpgrade” and the date/time of execution located in the Logs path specified by the Square9API web.config.

IMPORTANT NOTE

The upgrade parameters for an automatic upgrade include the migration of all “in-process” data, and 90 days of completed history. Customers who feel the need to migrated more than 90 days of completed process history may due so, post upgrade.

Upgrade Utility / Manual Upgrades — The database update can be run manually. Note, the Capture upgrade manages the upgrade process by default. You do not need to perform any steps outlined here unless you seek to override out of the box behaviors.