Concept: Adaptive Planning Non-Production Instances
Adaptive Planning non-production instances currently include only sandbox instances that are:
- Clones of production instances or blank non-populated instances.
- Completely independent of production instances. Changes you make in one doesn't affect the other.
Use non-prod instances to:
- Build and test significant changes to the level structure, accounts, or formulas without affecting live or production data.
- Develop and validate imports for a new integration.
- Archive clones of your production instances before making major structural changes
To purchase non-production instances, contact your Named Support Contact (NSC).
Non-Production Instance Refreshes
Refreshing non-production instances involves cloning the production instances. All changes you previously made in the non-production instances are lost. After a refresh, the non-production instances are replicas of the production instances but without these items:
- Transactions
- Import history
- Audit trail
- Snapshot reports
To request non-production instance refreshes, work with your NSC to create a Workday Customer Care request.
Refreshing Production Instances Using Non-Production Instances
Sometimes you can copy and use non-production instances to refresh production instances. These types of refreshes use exact copies of the source non-production instances. Any SAML SSO settings and users in the production instances get overwritten with those from the non-production instances. The customer is responsible for capturing any SAML SSO settings prior to making these requests. If either the production or the non-production instances are connected to a Workday tenant, these types of refreshes aren't possible.