Overview

Jump to the walkthrough video.

Before a form reaches your end users, it's important to validate that everything works exactly as intended. Testing a form in FINAL status gives you quality control over the forms you manage — so you can catch field mapping issues, verify data population, and confirm accuracy before your end users ever see the form.

Quik! moves every form through a structured build cycle: Original Build → Build → Test → Final → Publish. The FINAL status sits at the end of this cycle, just before a form goes live. This is your opportunity to review the form as it will actually appear in production, test that fields map correctly to your data, and validate that any updates work as expected, without impacting your end users.

Testing in FINAL status is especially useful when:

• You need to verify field mappings are correct before the form reaches production

• You want to test data population into a newly updated form

• You need a quality control checkpoint to ensure accuracy and remove friction for end users

Quik! provides two primary ways to test forms before they are made available to end users:

• Test forms before they're published, while they are in FINAL status

• Prefill forms with test data

Note: Previously, a form needed to have been published at least once before it could be tested in FINAL status. That limitation no longer applies, forms that are still Inactive (in Hold or Final status, and have never been published) can now be tested as well, using an additional payload flag. See Testing Final & Inactive Forms with Execute PDF for full directions.

Testing Forms in FINAL Status

The Quik! Forms Engine is the primary method for testing a form while it is in FINAL status. This testing capability is intended only for the owner of the form.

Note: If you need to test your forms before they are released to production, please notify our Forms Team at forms@quikforms.com when submitting your initial forms request. This allows us to keep the form in FINAL status until your testing is complete, ensuring it is not pushed immediately to production. If you want full control over when a form goes live, you can manage that directly in Quick Forms Manager.

Our standard turnaround for form builds—including new and updated forms—is within 10 business days.

If you need forms sooner, we offer a rush build option with an estimated turnaround of 2 to 4 business days. Rush fees apply unless stated otherwise.

If you would like to be notified when your form reaches FINAL status and is ready for testing, you will need to sign up for a Quik Forms Manager (QFM) account. This management tool enables you to receive email notifications for forms in your library once they are available for review in FINAL status.

Quik Forms Manager

• Sign up for Quik Forms Manager:
  https://quikformsmanager.com/signup.aspx

• Learn more about Quik Forms Manager:
  https://support.quikforms.com/hc/en-us/categories/5782186213915-Quik-Forms-Manager-QFM

Once you have completed your sign-up, please reach out to Forms Team at forms@quikforms.com so your account can be activated.

TestFinalFormsMode

To test a form in FINAL status, set the Quik! Forms Engine property:

‌

This setting pulls the form from FINAL status instead of the published version. This originally worked best for forms that had already been published. Forms that have never been published (still Inactive) can now also be tested by adding a second flag, TestInactiveFormsMode: true, when using the Execute PDF endpoint.See Testing Final & Inactive Forms with Execute PDF for setup steps.

Both the Execute HTML and Execute PDF endpoints support TestFinalFormsMode. You can set this property to true regardless of which endpoint you are using to pull forms from FINAL status.

TestDataMode (HTML Forms Only)

To test a form with automatically generated test data, set:

When enabled, the Quik! Forms Engine inserts test data into each text field. The test data is the Quik! Field Name itself (for example, 1own.FName will appear in the Owner 1 First Name field).

This is a useful way to quickly identify which fields appear on a form.

Exceptions

• Checkboxes are not populated automatically, but can be tested by manually selecting them.

• Formatted fields (such as SSN) do not prefill test data.

Important:

• TestDataMode is available only when generating HTML forms (Execute HTML).

• This property is not supported when using the Execute PDF endpoint.

REST Example (Execute HTML)

The following example demonstrates testing a form in FINAL status using Execute HTML, with optional test data enabled:

‌

Testing with Execute PDF

When testing forms using the Execute PDF endpoint:

• TestFinalFormsMode is supported and can be used to pull forms from FINAL status

• TestInactiveFormsMode can be combined with TestFinalFormsMode to test forms in Hold or Final status that have never been published

• TestDataMode is not available

• Any test data must be supplied explicitly using FormFields

Testing How Forms Affect Your Application

If your application includes custom logic or rules tied to specific forms, it is recommended that you set up a non-production environment (such as a demo or staging environment) with TestFinalFormsMode enabled.

This allows you to test both the form and your application's integration before the form is published to production, ensuring compatibility, especially when form designs change significantly.

Testing for Form Accuracy

While reviewing forms for completeness and accuracy is always recommended, it is not always required. Every Quik! form goes through a rigorous build and review process involving multiple reviewers.

Although you are responsible for validating forms for your use case, many customers rely on Quik! to publish forms automatically. If an issue is identified, it is addressed immediately.

Open