Guide to troubleshooting form designs part 5: Test view toolbar and other tips

On the top of the test view, there is a bar with tools you can use when testing.


We've already discussed the Progress and Form inspector tools, so here, we'll go over the other tools.


Under the Options dropdown menu, these tools will be available:

  • Validate form: Check to see if there are any required fields that still need to be completed, and also make sure all constraints are being met. Handy if you are jumping around the form using Go To Prompt (as discussed in section 2 above).
  • Skip to next: Skip to the next field, ignoring the constraint of the current field. A form cannot pass validation or be submitted until all required fields have been completed, and all constraints are met.
  • Clear responses: Clear the response of the field on the page you are currently on. If you are on a field list, then all fields on that page will be cleared.
  • Remove current repeat instance (when in a repeat group): Remove the current repeat instance, and be brought back to the previous repeat instance (or the field before the start of the repeat group if you remove the first repeat instance). If that repeat group's repeat_count property is defined (as opposed to being blank so repeat instances are manually created), then the repeat instance will likely be re-created. (You can learn more about the different repeat group methods in our documentation on repeating fields.)
  • Start over: Clear all data entered in the form, and start again from the beginning.

To the right of Options, you can change the language of the form, which you can learn more about in our documentation on including translations and translating the web forms user interface. Click on Help to open the documentation on testing your forms. Click Close to close the testing web browser tab (this will also close the online form designer, so make sure all recent changes are saved, as discussed above).

Just like with web forms, you can test a form as if it was opened from a case. To learn more, check out our support article on case management tips, tricks, and troubleshooting (section Testing a form used in a case), as well as our guide to unique links for web forms.

More on troubleshooting form design

When you are ready, you can check out the other articles in this series on troubleshooting form design.

  1. Intro and using the test view: Why it is important to test your forms, and how to use the test view options.
  2. Saving and resuming progress: How to save your test progress so you can use it in the updated form definition without needing to start over.
  3. Using the form inspector: Using the form inspector to find errors in your form.
  4. Submitting test data: Ensuring data is correct when submitted to the server.
  5. Test view toolbar and other tips: Other details on the test view and form inspector not covered in the other parts.

Do you have thoughts on this support article? We'd love to hear them! Feel free to fill out this feedback form.


Article is closed for comments.