Here are some best practices that really ought to be done post-clone, or refresh, so you don’t look like an idiot.
1. Ensure that the mailer is turned off!!! Depending on what happens in the refresh steps, often emails are redirected to a fake email address. Then check a sampling of customers to ensure that the email is re-directed!!!
2. Ensure that any processes like cost managers and workflows are again running. While you might have the insight to check that something like a Cost Manager ran for your transaction, your users, and any other folks might not clue in.
3. Ensure that data like security profiles and permissions are set appropriately for the new environment, so users have the right access to their data and systems. Otherwise, you might find yourself having to undo all of your hard work with a password reset!
Overall, it is important to be mindful of these best practices any time your production applications
4. Verify that any integrations are still running smoothly and that data is being updated correctly in both systems. This is especially important if you’re relying on third-party integrations to keep your systems in sync!
5. Test your processes! Make sure everything is still functioning as it should, and that data is being updated correctly. This is probably the most important step of all, especially if your refreshed environment includes new or modified processes.
Once you’ve verified that everything is running smoothly, it’s time to take things for a spin in your refreshed environment. Make sure to test all of your processes and verify that data is being updated correctly. And remember, if you’re relying on any third-party integrations, it’s also important to verify that these are still working as expected. Overall, the key is to take your time and be diligent in testing everything before going live in your refreshed environment. This will help ensure a smooth transition and minimize the risk of any unexpected issues down the line. Good luck!
…
