I am reaching out to see if there is any value on getting set up in Sandbox before Production. Just want to see if others utilized the Sandbox after the launch to Production.
If you do have Sandbox, have you found it valuable to assist in your Gainsight process?
Thank you for your help in advance.
Already have an account? Login
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Firstly, we make the changes in the *Full sandbox*, where the QA team tests the changes. Then the configuration changes are done in the *Partial sandbox* - UAT is done here.
Finally, the changes are done in Production.
Although, this approach works well in Salesforce but in Gainsight it is challenging because you don't have the luxury of moving change sets as easily as the migration tool in Gainsight is not really easy to use and is not full proof. Migration tool is glitchy and Gainsight doesn't recommend it.
Although, I strongly believe having configuration in the sandbox is the best approach. It's always advisable to make changes in a sandbox than making them directly in Production.
Pros - Risk mitigation, Back up environment, separate environment to build and test.
Cons - Changes need to be done manually in each environment.
Hope this helps.
One of the best use cases I find for GS is for testing rule changes in a full sandbox. You do need a full sandbox though so that you have . For examples, if you build your health scores in a full sandbox, you can test changes to the scorecard before deploying to production. This incredibly helpful if you are trying to test different scenarios with your scoring algorithms. We test lots of data changes in sandboxes and our clients are able to fully vet all changes before we deploy.