Skip to main content
Documentation
Documentation
Adaptive Planning
Last Updated: 2023-06-23
Instance and Refresh Requests

Instance and Refresh Requests

Sandbox Instance Information

An Adaptive Planning sandbox is a clone of a production instance or a blank non-populated instance. Sandboxes are completely independent instances, so changes in the sandbox will not affect the production environment, and vice versa. A sandbox instance is a tool that you can leverage to test new features or possible changes to your instance without affecting live production instance data.

Use case:

  • Building and testing significant changes to the level structure, accounts, or formula
  • Developing and validating imports for a new integration
  • Archiving a clone of your production instance before making major structural changes

Sandbox Refreshes

A sandbox refresh is a re-clone of a production instance, so all changes previously made in the sandbox will be lost. After a refresh, the sandbox will be a replica of the production instance without transactions, import history , audit trail, and snapshot reports.
Request a Sandbox or Sandbox Refresh
Work with your Named Support Contact (NSC) for either requests:
  • Purchase a sandbox instance.
  • Refresh an existing sandbox instance.
See Create a Case.
Refresh Availability
Refreshes are available Monday through Friday from 8:00 AM to 6:00 PM CT and can take between a few hours and 7 business days to complete. The completion time for a refresh will depend on the availability of our Account Provisioning team and the size of the instance being used for the refresh. Multi-instance sandbox refreshes and sandboxes cloned from instances that are greater than 50 GB typically take longer to process.
Required Information
The Account Provisioning team will need to confirm all required information and receive approval from an Administrative user before starting or scheduling a refresh.
  1. Source Instance Code:
    The unique code of the instance you want copied to another instance. This instance will not be changed/overwritten.
  2. Instance Code to Refresh:
    The unique code of the instance you want to refresh. This instance will be overwritten/refreshed with a copy of the Source Instance.
    • To find the unique code for each instance, go to Administration > General Setup > Code
  3. Refresh date and/or time:
    If no date or time is provided, we will assume that the refresh can start at the earliest availability of our staff
  4. Administrative user who will receive credentials:
    Credentials will need to be sent to an administrative user in the instance
Requests submitted by consultants, customer success managers, or non-admin users require written approval from a customer administrative user.

Submit a Refresh Request

Work with your Named Support Contact (NSC) to submit a Customer Care, Adaptive Instance Management, Adaptive Refresh Instance request. See Workday Adaptive Planning Instance Policy.

Copying Sandbox to Refresh Production

Although not typical, there are some cases when a sandbox can be copied and used to refresh a production instance. Since the refresh uses an exact copy of the source instance (sandbox), any SAML SSO settings and users in the production instance would get overwritten with the SAML SSO settings and users from the sandbox as part of the process. For this type of refresh, it is the customer's responsibility to capture any SAML settings prior to making this request.
This type of refresh is not possible if either the production or sandbox instance is connected to a Workday tenant.