A GxP sandbox is a type of developer sandbox designated to contain specific Box functionality that have been released over the course of the previous quarter so GxP customers can test and validate that functionality before making it available to their users. This process is often known as controlled release. The creation of a GxP sandbox enrolls the GxP customer into the controlled release process, starting with the Box quarter following enrollment.
This topic includes the following sections:
- GxP Controlled Release Criteria
- GxP Controlled Release Process
- GxP Sandbox Release Schedule
- Creating a GxP Sandbox
In the controlled release process, a controlled release feature is not made generally available to all customers when feature development is complete. Rather, controlled release is bifurcated:
- For GxP customers with at least one GxP sandbox defined, controlled release features are held throughout the quarter and then released to the GxP sandboxes after the quarter is complete. 30 days later, these features become available to all of your users.
- For GxP customers who do not have a GxP sandbox defined, as well as all other Box customers, controlled release features become available to all of your users at feature release.
Feature releases that are not subject to controlled release will be made available to all customers, including GxP customers, at release time.
The GxP sandbox is a test environment, meant to be a way for GxP customers to validate the intended use of Box for regulated content before release to production. For GxP customers, most customer-facing features, the controlled release features, across Box will be held until the end of each quarter, and then will be released for preview into their GxP sandbox environment in bulk (along with a set of release notes). Customers will have a 30-day preview period where they can validate these features in their GxP Sandbox Test Environment before the features in the GxP sandbox are released to their production environments.
This differs from the typical SaaS (software as a service) process where as features are completed, they are generally released to be available.
The GxP sandbox does not replace Box's automated daily testing of Box functionality, which GxP customers view and monitor on the GxP Insights page.
Notes
- GxP customers enrolled in the controlled release process will not be given access to any beta versions of any features. They will only receive the feature when it is released into their GxP sandbox as part of the regular controlled release schedule. Withholding beta versions from controlled release customers is Box's due diligence as a vendor in protecting our GxP customer environments from unintentionally violating their validated state.
- If you choose not to participate in the GxP controlled release program, your current Box environment will still remain GxP compliant and the Box product release process will remain as it always was.
GxP Controlled Release Criteria
Box uses the following definitions to decide what feature releases will be subject to controlled release:
- Major product launch with full marketing support.
- Product/feature release with high customer impact. Standalone release or bundle of related releases.
- Feature/integration release with medium customer impact. Standalone release or bundle of releases.
Feature/integration releases or EOLs with low customer impact or component releases that are part of a larger launch bundle are examples of feature releases that will not be controlled. Bug fixes are also not controlled. These will be released upon completion, as is typical of SaaS software, but will also be included in GxP release notes for review at the end of a quarter.
In addition, desktop products, such as Box Drive, are not part of the GxP controlled release program.
GxP Controlled Release Process
The GxP controlled release process is as follows:
- For enrolled GxP customers, features meeting a specified criteria are held for release throughout a quarter.
- All held features are released to the GxP sandbox on the first business day following the end of the previous quarter. GxP release notes are also released at this time.
- 30 days after held features were released to the GxP sandbox, they are made generally available for GxP customers.
GxP Sandbox Release Schedule
The approximate general GxP sandbox release schedule is as follows:
- Begin Feature Hold: First day of each Box fiscal quarter (Feb 1, May 1, Aug 1, Nov 1)
- Features Released to Sandbox: First day after the last day of each Box fiscal quarter, or the first business day after that if the date falls on a weekend or Box holiday
- Features Released to Production: 30 days after the Features Released to Sandbox date, or the first business day after that if the date falls on a weekend or Box holiday
Specific dates for upcoming quarters are included in the quarterly GxP release notes. A draft of GxP release notes, with most of the quarterly updates included, is typically published to GxP customers 4-5 days before the end of each quarter. The final version of GxP release notes is published to GxP customers typically within 3 business days after the released-to-sandbox dates.
Creating a GxP Sandbox
- Create a developer sandbox. Give the sandbox a name that will help you recognize it as a GxP sandbox.
- Select the Enable GxP sandbox check box.
- Click Create Sandbox.
Note
You can also convert an existing developer sandbox into a GxP sandbox. Note the EID of the existing sandbox and then contact your Box representative.