Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Testing the deployment

Updated on April 8, 2022

After you deploy the changes, the release engineer and specified users can test the changes. For the staging environment, test the performance and the user interface, run automated tests, and do acceptance testing. For the production environment, perform validation tests.

Do the following steps:
  1. On the target system, create a copy of the access group for your application. This step is a one-time process, because now this access group is available anytime you deploy changes.
  2. Update the copied access group so that it references the new application version.
  3. Find the operator ID record for a test user and give that operator ID record access to the access group that you just created.
Result: You can now safely test your changes in the system at the same time as other users who are running on the previous version.

When you are satisfied that your release was deployed successfully, Release Engineering can activate the release for all users in the production environment.

If you experience any issues, see Rolling back a problematic deployment.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us