Appearance
Sandbox type selection guide
Choosing a sandbox type by test objective helps you balance data fidelity, refresh cost, and environment capacity.
WARNING
Sandbox refresh intervals, storage capacity, and copy limits are not fully documented in the original manual. This article keeps the selection logic, but specific values require manual review.
Sandbox types
| Type | Copied content | Suitable scenarios |
|---|---|---|
| Development Sandbox | Copies production configuration, not business data | Configuration development, unit testing, feature experimentation |
| Partial Copy Sandbox | Copies production configuration and business data in a specified scope | User acceptance testing, integration testing, training |
| Full Sandbox | Copies production configuration and all business data | Release rehearsal, complete-chain testing, complex integration validation |
Selection recommendations
| Business need | Recommended type |
|---|---|
| Validate only object, field, layout, and flow configuration | Development Sandbox |
| Need a small amount of real business data | Partial Copy Sandbox |
| Need a complete business chain and real data relationships | Full Sandbox |
| Need to create or reset environments frequently | Development Sandbox |
| Need to simulate a formal release | Full Sandbox |
Type descriptions
| Sandbox type | Original manual description | Recommended usage |
|---|---|---|
| Development Sandbox | Contains a copy of the production configuration, without business data | Development and unit testing |
| Partial Copy Sandbox | Contains a copy of the production configuration and business data from specified objects | User acceptance testing, integration testing, and training |
| Full Sandbox | Contains a copy of the production configuration and all business data | Complete business chain validation and pre-release rehearsal |
Choosing a Development Sandbox
A Development Sandbox is suitable for configurators who need to quickly validate a solution.
For example, you need to add fields, adjust layouts, or configure flows. In this case, you do not need to copy account and order data. Using a Development Sandbox reduces environment preparation cost.
Choosing a Partial Copy Sandbox
A Partial Copy Sandbox is suitable for tests that need sample data.
For example, business users need to validate the complete flow from account to order. Test data does not have to be a complete copy of the production environment, but you need to preserve relationships between objects.
Choosing a Full Sandbox
A Full Sandbox is suitable for validation before high-risk releases.
For example, before a major version goes live, you need to validate permissions, flows, integrations, and data relationships. A Full Sandbox brings you closer to the production environment.
Manual review checklist
| Item to review | Reason |
|---|---|
| Creation limits for each sandbox type | The original manual documents only some deletion limits |
| Refresh intervals for each sandbox type | The original manual does not provide complete rules |
| Data capacity for each sandbox type | The original manual does not provide complete specifications |
| Data selection method for Partial Copy Sandboxes | The original manual does not describe template or object scope configuration |