Testing in Quik!'s UAT Environment

When possible, the Quik! development team deploys upcoming product updates to the User Acceptance Testing (UAT) environment prior to a production release. This allows customers to test new or updated functionality in a non-production environment before changes are released to Production.

Follow the instructions below to test your Quik! implementation in UAT.

When testing in the UAT environment, customers must modify the username only.

• Prefix the production username with uat

• Customer ID and password remain the same

Example:

• Production username: johnsmith

• UAT username: uatjohnsmith

This username format applies to all API calls made against the UAT environment.

All Quik! web services are available in UAT by modifying the service URL.

You can access UAT endpoints by either:

• Prefixing the URL with uat, or

• Replacing www with uat

Example:

Production:

UAT:

Apply this same pattern to all Quik! service URLs when testing in the UAT environment.

• The UAT environment is intended for testing upcoming Quik! features only

• UAT should not be used to validate:

  • Finalized form changes

  • Field Rules behavior

Recent form changes should be tested in Production by setting the TestFinalFormsMode flag to true when the form is in Final status.

📄 For more information, see: How Do I Test a Form?

Field Rules should also be tested in Production.

You can control rule behavior using the FieldAttributesManagerOff property to specify whether rules are enforced or ignored at runtime.

📄 For more information, see: Field Rules: Configuring Field Rules Programmatically (At Run Time)