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’ve upgraded the Conditional Logic feature in FormAssembly! It’s now easier to use and more powerful.

Here’s the rundown of what we’ve improved:

  1. You can now use complex rules, including “NOT” logic.
  2. It’s easier to find and select answers.
  3. Data from hidden questions won’t get submitted.
  4. Chained conditional rules now just work.
  5. Your forms will be automatically updated.

Read on for the details!

1. You can now use complex rules, including “NOT” logic.

Previously, conditional rules were limited to “OR” and “AND” logic. Setting up “AND” logic was also a bit difficult and unintuitive.

Now, however, it’s super easy to add complex rules. For instance, let’s say that you’re selling gourmet chocolate in the U.S., but you need to take precautions so the chocolate won’t melt on its way over. For certain customers who live in warmer states, such as Florida, you need to use special cooling packaging — and you can use conditional logic to make sure that the right options show up for those customers, like so:

  • If “Massachusetts” OR other cool states are selected, show Domestic Expedited/Priority Shipping option
  • If “U.S.” AND “Florida” (or other warm states) are selected, show Domestic Express Shipping option with special cooling packaging
  • If “U.S.” is NOT selected, show International Express Shipping option with special cooling packaging

Try the working example here:

Sorry, an error occurred.

This form is not available.

You can also create more complex setups by expanding and building upon the conditional rules.

2. It’s easier to find and select answers.

With the previous interface, if you had a long form with many questions, it could get time-consuming to pick the right answer for a conditional rule. Say, for example, you needed to set up sections based on countries, but you also had several questions with countries, so the drop-down list was very extensive. You’d have to scroll past the multiple sets of countries in order to pick the right one.

But now you can just start typing the answer you’re looking for, and the input box will automatically show you the available options, each labelled with its corresponding question. It’s quick and easy to find the right answer.

3. Data from hidden questions won’t get submitted.

If a conditional rule hides a question, then the data from that question won’t get submitted. For instance:

  1. Sharon chooses “Pizza” from a catered lunch form. She then answers a “Type of Pizza” question by entering “Pepperoni” in the input box.
  2. Later, she changes her mind. Instead of pizza, she goes back and chooses “Sandwich,” which triggers a conditional rule that hides (and disables) the type of pizza question.
  3. When Sharon submits her response, FormAssembly will clear and delete the data from all the hidden fields, including the “Pepperoni” answer.

In the past, if a respondent answered a question that was later disabled by a conditional rule, the answer would still get sent to the server. This could get confusing. Now, though, you don’t have to worry about it! The data gets cleared automatically when the response is submitted.

4. Chained conditional rules now just work.

Chained rules work even if the questions aren’t nested. For example, let’s say that Sharon’s form asks her whether she wants a Meat, Vegetarian, or Vegan lunch. She chooses the Vegetarian option, which triggers a conditional rule to show her choices for an entree and dessert. Sharon picks “Cupcake” for dessert, which triggers another question that asks her what type of cupcake she’d like.

If she changes her mind and chooses the Vegan option instead, the Vegetarian section and the Cupcake Flavor field will both be hidden by the chained rules.

 

5. Your forms will be automatically updated.

If you want to use the new conditional rules with a form you’ve already created, just open that form in the Form Builder. You won’t have to rebuild any existing rules, because the form settings will be automatically converted for you. Yay!

If you don’t want to change an existing form or don’t need the advanced conditional rules, the form will continue to work as before, with the previous system.

We hope that you’ll find the new conditional logic useful. If you have any feedback for us, we’d love to hear it: email us, comment here, or tweet @FormAssembly!

Pin It on Pinterest

Share This