Using Conditional Logic in Forms

Conditional Logic (also known as "skip logic" or "branching logic") makes your forms smarter and more interactive by showing or hiding fields, or making them required, based on a user's previous answers. This creates a more personalized and efficient experience, guiding users through your form in a way that's most relevant to them.

Note: Conditional Logic is a Pro feature.

Why Use Conditional Logic?

Implementing conditional logic in your forms offers several key benefits:

• Personalized Experience: Users are only presented with questions that are relevant to their specific situation and previous responses.

• Shorter Forms: By dynamically hiding unnecessary fields, forms appear less daunting and quicker to complete, which can significantly reduce form abandonment.

• Improved Data Quality: You collect more accurate and targeted information by guiding users down the correct path and asking only relevant follow-up questions.

• Increased Conversion Rates: A smoother, more relevant, and less cluttered form experience can lead to higher completion and conversion rates.

• Streamlined Processes: Automate parts of the information gathering process by tailoring the questions asked to the user's needs or choices.

Common Use Cases for Conditional Logic

Here are some practical examples of how conditional logic can be applied:

• Service/Product Interest: If a user indicates interest in a specific service or product, show additional questions related to that service.

  • Example: Question: "Which services are you interested in? (Checkbox)" Options: "Web Design," "SEO," "Content Writing." If "Web Design" is checked, show fields like "What is your current website URL?"

• Consent and Opt-ins: If a user agrees to terms or opts into a newsletter, reveal relevant fields.

  • Example: Question: "Do you agree to the terms and conditions? (Checkbox)" If checked, the submit button becomes active or an email field for the newsletter appears.

• User Segmentation: Ask different questions based on user type.

  • Example: Question: "Are you a Business or Individual?" If "Business" is selected, show fields like "Company Name" and "Number of Employees."

• Event Registration: Show different options based on attendance type.

  • Example: Question: "Are you attending in-person or virtually?" If "In-person" is selected, show fields related to dietary restrictions.

Setting Up Conditional Logic

Conditional Logic can be setup on the Logic page in the form builder. Click on the "Logic" button in the top navigation bar.

1. Define a Rule: Rules generally follow a structure like this:

   • IF: Select the field that will trigger the logic (the "trigger field"). This is the field whose value will determine the action.

   • CONDITION (Operator): Choose the comparison operator (e.g., Is, Is Not, Is Empty, Is Filled, Contains, Greater Than, Less Than).

   • VALUE: Specify the value of the trigger field that needs to be matched for the condition to be met (e.g., a specific text, a selected option).

   • THEN (ACTION): Choose what should happen when the condition is met (e.g., Show, Hide, Make Required, Make Optional).

   • TARGET FIELD(S): Select the field or fields that will be affected by this action.

   Example Rule:

   • IF Dropdown: "Are you interested in our newsletter?"

   • IS Yes

   • THEN Show

   • TARGET FIELD Email Input: "Your Email Address"

Supported Fields

• Trigger Fields: Fields that can typically trigger conditions are those with distinct options or states, such as:

  • Multiple Choice (Radio Buttons)

  • Checkboxes

  • Dropdown lists

  • Sometimes, Text Inputs (e.g., "Is Filled" or "Contains a specific word")

• Target Fields: Most field types can usually be the target of a conditional logic rule, meaning they can be shown, hidden, or have their required status changed. This includes:

  • Text Inputs (Single Line, Paragraph)

  • Email, Number, Date, Time fields

  • Multiple Choice, Checkboxes, Dropdowns

  • Section Breaks or entire groups of fields (if supported)

Multiple Conditions & AND/OR Logic

Complex forms might require more sophisticated logic:

• Multiple Rules for One Target Field: You can often apply several different logic rules that all affect the same target field. For example, one rule shows a field, and another rule (based on a different trigger) also shows the same field.

• AND vs. OR Logic: When a single action depends on multiple conditions:

  • AND Logic: All specified conditions must be true for the action to occur. For example, "Show Field C IF Field A is 'Yes' AND Field B is 'Option 1'."

  • OR Logic: If any one of the specified conditions is true, the action will occur. For example, "Show Field C IF Field A is 'Yes' OR Field B is 'Option 1'."

  • The interface for setting up AND/OR logic varies. Some systems allow you to group conditions or select "Match all conditions (AND)" or "Match any condition (OR)."Placeholder for image:

Testing Your Conditional Logic

Thorough testing is crucial:

• Use Preview Mode: Always use the form's "Preview" mode to test your conditional logic.

• Test All Paths: Try every possible combination of answers for your trigger fields to ensure the target fields appear, disappear, or change their required status exactly as intended.

• Check for Conflicts: Ensure different rules don't unintentionally override each other in unexpected ways.

Troubleshooting Common Issues

If your conditional logic isn't working as expected, consider these points (and for more, refer to docs/troubleshooting.md):

• Conflicting Rules: Make sure you haven't set up rules that contradict each other (e.g., one rule says "Show Field X" and another says "Hide Field X" based on conditions that can be true simultaneously).

• Incorrect Values: Double-check that the values specified in your conditions (e.g., "Yes," "Option A") exactly match the actual values of your trigger fields. Case sensitivity can be a factor.

• Logic on Hidden Fields: Ensure that a field you are trying to use as a trigger isn't itself hidden by another preceding logic rule.

• Typos: Simple typos in values or field names within the logic setup can cause it to fail.

Conditional logic is a powerful feature that can dramatically enhance the user experience and efficiency of your FluidForms. By carefully planning and testing your logic paths, you can create truly dynamic and responsive forms.