Once you have configured your setup, you need to move this to another tenant to test it.
To set up a UAT tenant, you need to import your integration and templates from your development tenant and any other optional setting you set up in your development tenant. Your UAT configuration should reflect what production is going to be as much as possible.
Following testing, you'll usually want to make changes. These might be fixing configuration bugs or improving the configuration following real employee feedback. To do this, you:
- Make any changes in your development tenant.
- Update the templates (or create new ones).
- Install those template updates.
- Validate the changes work before asking your users to re-test.
You repeat this process until done. You may want to limit feedback iterations to just one or two to ensure the functionality is fully complete at the end of a two-week sprint.
Once complete, you can package up your templates and integration recipes ready for production deployment. You may wish to hold off on packaging until all the initial sprints are completed; then, you can package everything in one go, ready for production deployment.