arrow-left

All pages
gitbookPowered by GitBook
1 of 1

Loading...

Sandbox Guidance

hashtag
Sandboxes: Create, Clone, and Edit

A sandbox is a copy of your production organization. You can create multiple copies of your organization in separate environments for different purposes such as development, testing, and training, without compromising the data and applications in your production organization. Different types of sandboxes have different refresh intervals, meaning they cannot be replaced for a set amount of days. It is important to be mindful of which sandbox is being used for which process. This guide explores basic sandbox information, and practices.

hashtag
Sandbox General Information

Note From QA Strat:

  • Unit Tests and Apex Tests: Scratch Orgs

  • Feature Tests and Regression Tests: Dev-Pro Sandbox

  • Staging and user-acceptance testing: Partial-Full sandbox

Developer Pro Sandboxes

  • Have a refresh interval of 1 day

  • 1 GB limit

  • Only Metadata is copied

Partial Full Sandboxes

  • Have a refresh interval of 5 days

  • 5 GB limit

  • Metadata and sample data is copied

Full Sandboxes

  • Have a refresh interval of 29 days

  • Same storage limit as production org

  • Metadata and all data is copied

hashtag
Important Practices

  • Give Manage Sandbox permissions to a user to allow them create, refresh, activate, or delete a sandbox

  • Give Setup and Configuration permissions to a user to allow them to view a sandbox

  • Monitor the storage of each sandbox to ensure you don't throw too much into it

hashtag
Creating a Sandbox

  1. Setup -> Sandboxes in Quick Find

  2. Click 'New Sandbox'

  3. Enter a name (Such as 'QA'. The fewer characters the better

hashtag
Creating Sandbox Templates

  1. Setup -> Sandboxes in quick find -> sandbox templates

  2. New Sandbox

  3. Enter a name and description

hashtag
Refreshing a Sandbox

  1. Setup -> Sandboxes in quick find

  2. Next to the name of sandboxes there should be a refresh link, click it

  3. Review the name, values, and description

hashtag
Cloning a Sandbox

A sandbox can be cloned to save time. Instead of pulling source from the production org, you can replicate the data. Sandbox cloning simplifies having multiple concurrent streams of work in your application life cycle. You can set up a sandbox for each type of work, such as development, testing, and staging

  1. Set up -> Sandboxes

  2. Click Clone

  3. Enter a Name

hashtag
For More Information Regarding Sandboxes:

Salesforce's Sandbox Guide & Documentation:

No sandbox template
Has a sandbox template (required)
Has a sandbox template (optional)

Refresh a sandbox before you plan to work on or test new changes in it

  • Make sure you don't refresh or delete a sandbox until you're sure that you're finished the work you have to do in it. Be mindful of the refresh intervals.

  • Select the type of sandbox you want
  • For a Partial Copy or Full sandbox, decide the type of data you want in the sandbox a. Partial: click next, select the template b. Full: click next, select how much data to include(or choose a template)

  • To run scripts after each create and refresh for this sandbox, specify the Apex class you previously created from the SandboxPostCopy interface.

  • Select checkboxes for each object you want from the available objects list
  • Save

  • Select the type of environment you want
  • If you want your sandboxes activate immediately after refresh, select Auto Activate

  • Click Create

  • confirm that the sandbox name selected in the Create From dropdown is the sandbox you want to use as your source org. Click Next, then Create
    Herearrow-up-right