Zuora Developer Sandbox
Zuora Developer Sandbox is a testing environment with similar settings and configurations as your Production environment.
Developer sandboxes have copied configuration data from your production system, ensuring that your developers are always developing in a system that is identical to your production environment. In comparison, API sandboxes are ideal for experimenting but are likely configured very differently than your production systems.
Some of the benefits of the Zuora Developer Sandbox:
-
Integration development
-
Integration testing
-
Latest configurations from production, such as product catalog, workflows, notifications, and settings, and ability to automate the population of master configurations to speed your development
-
Frequent refreshes for agile and iterative development processes
-
Self-service tooling for continuous integration and continuous development
-
Self-serve actions, including refreshing and viewing ETC from the UI
-
Refreshes every two weeks
-
Erasure of data upon sandbox refresh so latest configuration and settings copied from production
The following table lists what configuration data is copied from your production environment to Developer Sandbox.
Component Name |
Level 1 |
Configuration |
---|---|---|
Product Catalog |
Product |
Configuration |
Product Rate Plan |
Configuration | |
Product Rate Plan Charge |
Configuration | |
Feature |
Name |
Configuration |
Feature Code |
Configuration | |
Finance |
Finance-Accounting Period |
Configuration |
Platform |
Custom Objects |
Configuration |
Work Flow |
Configuration | |
Data Query |
Configuration | |
Custom Fields |
Configuration | |
Administration |
Entity Profile Attachments |
Configuration |
Entity Profile Info/Manage Tenant Profile |
Configuration | |
External SMTP |
Configuration | |
Manage User Roles |
Configuration | |
Manage Data Access Control |
Configuration | |
Manage OAuth |
Configuration | |
Manage Audit Trails Setting |
Configuration | |
Manage Insights |
Configuration | |
Security Policies |
Configuration | |
Billing |
Batch Aliases |
Configuration |
Billing Cycle Types |
Configuration | |
Billing Period Starts |
Configuration | |
Billing Periods |
Configuration | |
Billing Rules |
Configuration | |
Charge Types/Models |
Configuration | |
Discount Settings |
Configuration | |
Doc Prefixes/Defining Numbering, SKU Formats |
Configuration | |
List Price Bases |
Configuration | |
Payment Terms |
Configuration | |
Revenue Recognition Codes |
Configuration | |
Subscription Setting |
Configuration | |
Unit of Measure |
Configuration | |
Currencies |
Configuration | |
Billing Document |
Configuration | |
Configuration | ||
Configuration | ||
Configuration | ||
Tax Codes |
Configuration | |
Tax Engine and Tax Date |
Configuration | |
Configuration | ||
Finance |
Accounting Codes |
Configuration |
Accounting Rules |
Configuration | |
Aging Buckets |
Configuration | |
Chart of Accounts |
Configuration | |
FX Currencies |
Configuration | |
GL Segments |
Configuration | |
Revenue Event Types |
Configuration | |
Revenue Recognition Code Status |
Configuration | |
Revenue Recognition Models |
Configuration | |
Revenue Start Date |
Configuration | |
Platform |
Communication Profiles |
Configuration |
Product Attributes |
Configuration | |
Sharing Attributes |
Configuration | |
Payments |
Application Rules |
Configuration |
Payment Gateways |
Configuration | |
Payment Methods |
Configuration | |
Payment Retry Rules |
Configuration | |
Reason Codes |
Configuration |
The following table is a comparison between Developer Sandbox and Zuora Central Sandbox.
Developer Sandbox |
Zuora Central Sandbox | |
---|---|---|
Production snapshot of transactional data |
No |
Yes |
Production snapshot of configuration data |
Yes |
Yes |
Snapshot refreshes allowed |
Twice per month |
Once per month |
Self-service UI |
Yes |
Yes |
Intended use cases |
Integration development and testing |
User acceptance testing and performance testing |