Sandbox Management Best Practices

-

Sandbox Management and Best Practices

An overview of different types of sandboxes, top use cases for each type, and what is included with each when the sandbox is created or refreshed.

There are 4 types of sandboxes and some are only included in certain Salesforce Editions or purchased for an additional cost, please contact your Salesforce Account Executive for details.

Common use cases for each type of sandbox and recommended best practices

Developer - may be refreshed every day, does not include any data automatically but allows 200 MB of data to be imported or created. The most agile and plentiful sandbox type for proof of concept, metadata-specific development, or just playgrounds for Developers and Admins to run through potential setup changes to review impact.

Developer Pro - may be refreshed every day, does not include any data automatically but allows 1GB of data to be imported or created. Same idea as the Developer but with a higher storage limit for the purpose of creating or loading a subset of records to test newly developed customizations or features that rely on data.

Partial Copy - may be refreshed every 5 days, includes a sample of production data up to 10k parent records and related child records, or 5GB of data total. This sandbox requires a Sandbox Template. A more agile solution than full copies to test specific application areas with selected sample data sets from production.

Full Copy - may be refreshed every 29 days, including a full copy of production data and Sandbox Templates may be used but not required. Typically used for Quality Assurance (QA) and/or User Acceptance Testing (UAT) at the very end of the development life cycle before deploying changes to production.

Sandbox Delivers Real Business Benefits

When you create a separate environment for:

Developing

Testing

Training

You enable:

More stability for your active organization

Shortened cycle times for testing and trials

Realistic training environment

To strategically:

Reduce Operational Risk

By minimizing disruptions to your active organizations and your operations

Raise productivity

Developers spend less time working around constraints of production organization.

Users trained in a real-world environment transition seamlessly to production organization.

Increase efficiency

Tests and trials of new apps, new release features, configuration changes, can be seamlessly handed off to QA and then production organization.

Higher User Satisfaction

Better application quality, fewer disruptions and training lead to more satisfied users of Salesforce.

See also:

Create, Clone, or Refresh a Sandbox   

Sandbox Types and Templates  

MASTER CLASS: How To Use Sandboxes (Master Solution Architect Iman Maghroori)

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more