Releases and Environments
Table of Contents
Overview
QbDVision offers two release options:
Standard Release - updates are released when development and testing are completed.
Extended Release (XR) - Release dates are scheduled, and new features are only rolled out after completing an entire release cycle, allowing us to validate them.
While Standard and Extended offer identical functionality, they differ in software update frequency and validation compliance.
Note: QbDVision releases are named (e.g., Latin, Metal). See below for details.
These release options are also available via our Enterprise IT package, which offers additional functionality for enterprise customers.
Key Concepts
Comparison
| Standard Release | Extended Release |
---|---|---|
New Features | When available (completed development and testing), can be multiple times per week. | Scheduled, 3x per year. |
Bug Fixes and Other Updates | Scheduled, as needed, usually once a month. | |
Ideal Client | Clients requiring access to new functionalities, and not using QbDVision in a validated state. | Clients using QbDVision in a validated state or clients looking for additional control of the release frequency. |
Identification and Naming | Releases are named via release number. | Named releases (e.g., Metal) in addition to release numbers. |
Extended Picture of Environments
For exploration and validation, QbDVision also offers Sandbox environments. The “Extended Staging” environment is locked to the prior version. However, before a major release, this environment is upgraded early to allow for validation activities to be executed.
Relationship to Validation Package
Extended Release (XR) focuses on stability and regulatory compliance; it is “pre-validated” by purchasing the optional Validation package, which includes comprehensive TPQ (Transfer Performance Qualification ) documentation.
Relationship to Licenses
QbDVision license names are granted to a specific environment; e.g., a Professional XR license is a Professional license in the Extended Release environment.
Release Naming
QbDVision releases are named. We currently use a musical-themed naming convention (e.g., Latin, Metal), in alphabetical order.
Frequently Asked Questions
Does our company use the Sandbox to build and transfer to the Production instance?
No. Your Sandbox is for initial training and testing new features, as well as storing practice data. The Sandbox is also where we conduct training. Never put sensitive data in the Sandbox.
There is no automatic path to move data between Sandbox and Production. Paid options for data migration are available. Please contact your Customer Success Manager for additional information.
Can the Sandbox have a different look and color scheme than Production? I am concerned that some of my users may be signed into Production, think they are in Sandbox, and add more junk. I know the web address will differ, but can we add more differentiation?
We can change the name of your Sandbox to COMPANY-TRAINING or COMPANY-SANDBOX, which should alleviate your concerns. Please get in touch with your Customer Success Manager if you would like to implement this change.