Prerelease Test Environment - FAQ - Internal Only

Options
natalie_poull
natalie_poull Member, ALL USERS, Employee Posts: 5 Master Anaplanner of the Year
in Anaplan Community

Want to learn more about Anaplan's upcoming Prerelease Test Environment and how you should talk about it with your customer? Read on to better understand what the Prerelease Test Environment is, who will be participating, and other important details.

What is the goal of the Prerelease Test Environment? Which customers will be invited to participate in the Prerelease Test Environment? 

The goal of the Prerelease Test Environment will be for some of our larger customers to experience how some of our product updates will work. Three customers have been notified of this environment and will be participating: JDI, BPCE, and Diageo. These customers have been asking for us to allow them to test their models in a test environment before features are released, to ensure that their critical business functions work properly. Note that this is different than having customers work in a Beta environment-- the Prerelease Test Environment is for production. Each of these customers is required to sign the Prerelease Test Environment agreement.

How does a customer log-in to the Prerelease Test Environment? 

As soon as we’re informed that they e-signed the agreement we will create the workspaces and add the BP. The BP can determine the customers to add if they do not see all customers accounted for. If they need SSO setup they will need to inform support. 

The customer should log-in to Prod, where they'll have access to a new workspace. They'll need to copy over their test models from their pre-existing production workspaces to the Prerelease Test Environment WS themselves. 

After customers do their benchmarking with the current production build, we will update the test cores to the new version. After the Prerelease Test Environment environment closes, Anaplan will deactivate these workspaces until the next round of Prerelease Testing (prior to the next major Core release). Customers will have 1 week to run tests, and we aim to close out regression testing by Friday November 2.

Where does the customer go to find out information about when the Prerelease Test Environment is available and how to use it?

The Prerelease Test Environment environment will be available on Tuesday, October 23 for baseline testing on current production. Customers will have one week to run baseline tests then we will update the cores. The Prerelease Testing phase on the new core version will run until Monday, October 29.

We will share release notes ahead of time with customers. The intent of the environment will be for customers to test that their critical business processes still work. The Prerelease environment is not about testing new features.

How does a customer give feedback and/or report issues? 

Customers will log support cases as they normally would, by submitting feedback or any issues via a support ticket. The term "Prerelease Test" must be in the title of the support ticket, and all cases will be routed to L3. note: The BP should coordinate with their customer and support can answer whatever questions they have.

If a business critical process breaks in this environment, will the feature still be released?

Each issue will be assessed by Anaplan to determine severity and impact and a decision will be taken internally at Anaplan regarding feature releases.

What kind of models/data can be put into the Prerelease Test Environment? How does a customer copy data into the environment? 

Any model can be copied to the UAT workspace, and the customer will be responsible for the copy. Customers should refer to the guidelines regarding which features are not included in Prerelease Testing . Support will copy models over that are required for ALM testing (a case must be logged with Support to receive this). The same security will apply in the Prerelease Test Environment as in production.

List of Customers with access to Regression Environment

  • JDI
  • BPCE
  • Diageo

Categories