Testing Quik! Updates in a UAT Environment

When possible, the Quik! development team pushes any product updates to our User Acceptance Testing (UAT) environment for customer testing prior to a production release. Follow the instructions below to test your Quik! implementation in this non-production environment.

HOW TO TEST UAT

Credentials

When testing in the UAT environment, customers must add "uat" to the beginning of the username for the account credentials used to call UAT APIs. For example, if a customer's production username is johnsmith, their username to be used when testing in UAT would be uatjohnsmith. Customer ID and password remain the same.

When calling Quik! APIs directly

Everything in our UAT environment is available by prefixing web service URLs with “uat” or by replacing “www” with “uat”. For example, a web service such as “https://websvcs.quikforms.com/rest/QuikFormsEngine/qfe/execute/html” becomes “https://uatwebsvcs.quikforms.com/rest/QuikFormsEngine/qfe/execute/html” where “uat” is added after the https:// and before the existing URL. Apply this same pattern to all URLs for accessing them in the UAT environment. 

Important Notes:

Quik!'s UAT environment is designated for testing upcoming features only.

• Recent form changes should be tested in Production with the flag "TestFinalFormsMode" set to true if the form is in Final status. For more details, please visit: How Do I Test a Form?

• Field Rules should also be tested in Production. You can use the "FieldAttributesManagerOff" property to specify whether the rules should be ignored or enforced. For more information, please visit: Field Rules: Configuring Field Rules Programmatically (At Run Time)

Note: The Quik! DLL is now considered legacy and has been deprecated. It is no longer in use. This guide below is provided for reference purposes only.

When using the Quik! DLL

If you are using the Quik! Forms Engine DLL, it is difficult for Quik! to provide a new version that points to our UAT environment. Instead it is more reliable and easier if you override its settings by applying different configuration settings within your application. If you are running a .NET web application, then these settings can be added to the web.config. Other .NET applications will have these settings applied in the app.config file. Take note of the UAT endpoint URLs in the config settings below as these changes will tell the QFE.dll to call against our UAT environment.

Here's how to override URLs in a web/app config:

1) At the very top of the file, under <configuration>, copy the following tags:

configuarationSettings

REST OF THE FILE HERE

2) At the very bottom, just before closing </configuration>, place the following:

applicationSettings