Form Builder Usability Updates

Disclaimer: As of June 2018, Form Builder 5.0 is the default version of the FormAssembly Form Builder. Visit the release blog post to learn about the Form Builder 5.0 improvements.

We’re rolling out a few updates to the Form Builder today that we hope will make your experience a little easier and more productive.

Changes to Page Creation

One of these updates should make creating multi-page forms simpler. Previously, you had to create at least two pages and add content to both before you could see any change in the form preview. This was confusing for first-time users as clicking the ‘add page’ button alone didn’t seem to have any visible effect. We’ve fixed that.
Now, when you first add questions and then add a page, you will be able to see a page 1 with your first questions and a page 2 will be created. New questions can then be added to page 2. If this sounds obvious, great! that how it should be.
For a quick look at how this all works in practice, check out the screencast we made.

New Look for Read-Only Fields

Every once in awhile you may create a form that has read-only fields. These fields, generally calculated fields, aren’t editable by the respondent. However, previously they looked editable and this may have caused some confusion for your respondents. Now, when you create a calculated field and check the “Lock” box next to it, the field performs the calculations but looks like plain text.
Old style
New style

Changes to Input Validation

In this update, we’ve also made some changes to the free-text validation options available, namely, we’ve eliminated the “alphabetic” validation option. We’ve found that alphabetic-only validation is not well understood, and often assumed to be useful to validate full names. There are many legitimate names that would cause a alphabetic-only validation to fail, for instance, “John O’Connor the 3rd”, so we are eliminating the confusion by eliminating the option.
However, if you find one of your forms really needs alphabetic validation for a field, this can still be done using a regular expression. If you need more information on regular expressions, check out the support documentation.
Note that if your forms currently use alphabetic validation, it will continue to work. The option has simply been eliminated for future forms.
As always, we welcome your feedback here in the comments, in our UserVoice forum or via Twitter @FormAssembly.

Don’t just collect data — leverage it.