How To Test In A SALESFORCE SANDBOX

In this video, you’ll learn about different types of Salesforce Sandboxes, tips on testing in sandbox, and how to make sure your customers are not impacted.
✅ GET THE CHECKLIST - "10 Ways To Make Salesforce Payments Safe, Easy And Profitable" chrgnt.co/Salesforce-Payments...
RELATED VIDEOS AND LINKS:
- How To Test Payments In Salesforce • How To Test Payments I...
- How To Manage Recurring Billing In Salesforce bit.ly/Saleforce-Recurring-Bil...
- Read the blog post: www.appfrontier.com/blog/how-...
- How to Deploy from a SALESFORCE SANDBOX • How to Deploy from a S...
WHY:
Salesforce orgs can be extensive with many different areas of data and multiple applications. Sandboxes give you a chance to test changes without impacting your operations or data in your production Salesforce org.
BEFORE YOU BEGIN, KNOW THIS:
1. The three main types of Sandboxes are:
a. Partial Sandbox, which is a Salesforce Sandbox that includes a copy of your production org’s configuration (including metadata) and a sample of your production org’s data (but typically just a small portion of your total data).
b. Full Copy Sandbox, which is a complete replica of your Production Salesforce Org’s data and configuration.
c. Developer Sandboxes. These are more isolated environments for development and testing, that usually do not have a copy of any of your data.
2. To see the available Sandbox Licenses in your Production Org go to Salesforce Setup, then Environments, then Sandboxes.
3. Keep in mind that the Sandbox contains an either complete or a partial copy of your real customer data, so be careful not to inadvertently charge customers, send emails to customers, or otherwise affect your customers via actions that you take in the sandbox.
4. Sandboxes are separate orgs, with a different Org ID from your Production Org. After a sandbox is created, data does not update or sync between your Production Org and your Sandbox org. So changes made in either Org will not be reflected in the other Org.
5. Log in to your sandbox using the following URL: test.salesforce.com as well as your sandbox username. This is your regular username with the sandbox name added to the end after a dot, for example if your sandbox is named partial, it would be [e-mail].
THE TIPS:
In this video we will cover:
1. Creating and Refreshing Sandboxes
2. Email Considerations
3. Other Sandbox Considerations
4. Licensing
5. Batches and Scheduled Jobs
6. Chargent Payment Gateways
7. Test Data vs. Customer Data
BONUS TIP:
We recommend you to plan for a real Salesforce Sandbox testing phase as part of your launch of Chargent in your Salesforce environment. This includes test and live payments in both a Salesforce Sandbox and your production Salesforce org as well. These testing guidelines are what we have seen resulting in the most successful implementations of Chargent, especially when moving from other billing or payments software.
RESULTS:
Now you know about different types of Salesforce Sandboxes, tips on testing in sandbox, and how to make sure your customers are not impacted.
#Chargent #SalesforcePayments
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
✉️ CONTACT US:
We are always here to help! chrgnt.co/Contact-EraeBKHq5l8

[@ChargentByAppFrontier]

Next, check out "How To Test Payments in Salesforce" kzbin.info/www/bejne/qZKXoIZuabB_d80

[@virgo07]

Music in background is annoying 😢

[@ChargentByAppFrontier]

We appreciate your feedback. Thank you for letting us know.