A sandbox environment is a copy of the production org and is typically used for developing new functionality, testing and training, without comprising data and processes in the production org.
Only full sandboxes support performance testing, load testing and staging, but there are other types of sandboxes available depending on your requirements. Full sandboxes are a replica of the production org, including all data such as object records, data, attachments and configuration.
With a sandbox in place, it is possible to transfer configurations from the sandbox to the production environment using change sets, which can often save time re-configuring.
Steps to refreshing a Sandbox
- From Setup, enter Sandboxes in the Quick Find box, then select Sandboxes.
- A list of your sandboxes displays. Sandboxes that you can refresh have a Refresh link next to their name.
- Next to the name, click Refresh.
- Review the Name, Description, and Create From values, and edit these values if needed.
- Select the type of sandbox environment you want.
- A table shows the number and type of sandbox licenses available in your org. Click “Next” under the Full option
- Select the data you want to copy (typically all). Click Next
- If you want to activate your sandbox immediately after you refresh it, select Auto Activate. In this case, you don’t receive an activation email.
- Click Create.
- Salesforce starts copying data to the sandbox.
- If you didn’t select Auto Activate while refreshing your sandbox, Salesforce sends you an email when your sandbox is ready to activate.
Logging into the Sandbox when it’s activated
Username: this is your standard username followed by the name of your sandbox. So, for example firstname.lastname@example.org
Password: this is your usual password
Actions after Sandbox Creation checklist
Here’s our handy checklist to ensure working in your sandbox is as low risk as possible:
- Team Member that refreshed the sandbox to unscramble the user email address for other system admin users to enable them to log in
- Switch system deliverability to “System Emails only”
- Remove all manual email addresses from Action Events
- Disable workflows email alerts
- Disable any process builders which send emails to particular users
- Disable the Team Member to user synchronization via Installed Packages
- Amend the “Request Prefix” field for all HCM Form Definitions to reflect the site URL in Setup > Sites
- Amend the “Base URL” field within Installed Packages > Recruit to reflect the site URL in Setup > Sites
- Amend any links in email templates as these will all direct to the production environment
- Scramble any personal and work email addresses
- Switch off any batches within HCM Installed Packages
- Scramble and candidate emails
- Remove credentials from payflow services, as well as the automation via the cron command