Ask Search:
Edward VazquezEdward Vazquez 

Refreshing a Full Copy Sandbox

Hello,

I need to refresh our full copy sandbox. What post refresh steps have others followed? Is there some sort of checklist that she be followed post refresh? 
Best Answer chosen by Edward Vazquez
Bhavna BanodhaBhavna Banodha
Hi Edward,
There is no as such officialy defined list but below are the points you can check
  • Disable Scheduled Apex Jobs
  • Disable Outbound Messages or point them to QA server endpoints.
  • Reconfigure External Web Service calls for a non-production environment
  • Disable Analytic Snapshots
  • Get the new Sandbox Org ID and instance Id if required
  • Remove the email suffix for required users
  • Create any required users who don't exist in Production
  • Regenerate (or completely disable) Inbound Email Services
  • Delete / modify entries in Remote Site Settings if you don't want to perform certain callouts.
  • Disable "Big Deal Alert" on Opportunities - can be embarassing to send an email with "My awesome test Opp !!1" to CEO
  • If you have managed packages with API keys (like FinancialForce) - ask their support teams to regenerate the keys
  • If you have "power users" that will coordinate User Acceptance Testing - create entries in Delegated Administration area so they can "login as"
  • break Email addresses on Contacts, Leads etc. with suffix like it's done for users (and wherever you store email info if there's any risk of routine communication kicking in for example from workflow email alerts)
  • disable Weekly Data Export?
  • if you have email templates or documents with sensitive data (like Purchase Order and scanned signature of approver) it might be worthwhile to cripple them somehow (fake logo, big red "TEST ONLY" etc..). Documents won't be carried to non-full sandboxes though
https://salesforce.stackexchange.com/questions/955/post-sandbox-refresh-steps

All Answers

Artur NovikovasArtur Novikovas
Here's a good read
https://help.salesforce.com/servlet/servlet.FileDownload?file=015300000036AisAAE
Regards
Artur
Bhavna BanodhaBhavna Banodha
Hi Edward,
There is no as such officialy defined list but below are the points you can check
  • Disable Scheduled Apex Jobs
  • Disable Outbound Messages or point them to QA server endpoints.
  • Reconfigure External Web Service calls for a non-production environment
  • Disable Analytic Snapshots
  • Get the new Sandbox Org ID and instance Id if required
  • Remove the email suffix for required users
  • Create any required users who don't exist in Production
  • Regenerate (or completely disable) Inbound Email Services
  • Delete / modify entries in Remote Site Settings if you don't want to perform certain callouts.
  • Disable "Big Deal Alert" on Opportunities - can be embarassing to send an email with "My awesome test Opp !!1" to CEO
  • If you have managed packages with API keys (like FinancialForce) - ask their support teams to regenerate the keys
  • If you have "power users" that will coordinate User Acceptance Testing - create entries in Delegated Administration area so they can "login as"
  • break Email addresses on Contacts, Leads etc. with suffix like it's done for users (and wherever you store email info if there's any risk of routine communication kicking in for example from workflow email alerts)
  • disable Weekly Data Export?
  • if you have email templates or documents with sensitive data (like Purchase Order and scanned signature of approver) it might be worthwhile to cripple them somehow (fake logo, big red "TEST ONLY" etc..). Documents won't be carried to non-full sandboxes though
https://salesforce.stackexchange.com/questions/955/post-sandbox-refresh-steps
This was selected as the best answer
Edward VazquezEdward Vazquez
Thank you.
Andy BraveryAndy Bravery
This is a very useful list.
As a follow up, which of these activities can be automated and run as part of the SandboxPostCopy script?
For those that cant, could a third party tool like Copado or Autorabit be used to record the user interactions required to perform the activities, and then automatically replay them to reduce the manual effort involved to a minimum?

Additionally, do all scheduled jobs need to be disabled in the sandbox? For example, what if we want to test that the regular running of a dashboard works in pre-production?