Skip to main content
Conditional Logic is a powerful feature in Formora that allows you to create dynamic forms that adapt in real-time to user input. By setting up rules, you can show or hide specific fields (or groups of fields) based on the values entered or selections made in other fields. This makes your forms feel more interactive, personalized, and can significantly improve completion rates by only presenting relevant questions.

​
Benefits of Using Conditional Logic

  • Personalized Experience: Tailor the form to each user, asking only relevant questions.
  • Shorter Apparent Length: Forms appear less daunting as irrelevant sections are hidden.
  • Improved Data Quality: Guide users to provide more accurate information by simplifying the form.
  • Reduced Cognitive Load: Users don’t have to process and skip over questions that don’t apply to them.
  • Streamlined Workflows: Can direct users down different paths within a more complex form.

​
How Conditional Logic Works in Formora

Typically, you configure conditional logic on the field that you want to show or hide (the target field). The logic is based on rules that evaluate the state of one or more trigger fields.
  • Access: Conditional logic rules are usually set up in a dedicated “Conditional Logic,” “Display Logic,” or “Rules” tab within the Properties Panel of the target field.
  • Basic Structure: The core of a rule is: IF [Trigger Field] [Operator] [Value] THEN [Action] ON [This Field].
Mockup of a conditional logic rule builder: selecting trigger field, operator, value, and action.

Conceptual interface for defining a conditional logic rule

​
Defining Conditions (The “IF” Part)

A condition is made up of three parts:
  1. Trigger Field: The field whose value will trigger the action. You select this from a list of other eligible fields in your form (usually input fields like Text, Number, Select, Radio, Checkbox).
  2. Operator: The comparison to perform on the trigger field’s value.
  3. Value: The specific value the trigger field is compared against.

​
Common Operators

Formora likely supports a range of operators depending on the trigger field’s type:
  • Is / Equals: The field value exactly matches the specified text (case-sensitivity might be an option).
  • Is Not / Does Not Equal: The field value does not match.
  • Contains: The field value includes the specified substring.
  • Does Not Contain: The field value does not include the substring.
  • Starts With: The field value begins with the specified text.
  • Ends With: The field value ends with the specified text.
  • Is Empty: The field has no value.
  • Is Not Empty: The field has a value.
  • Equals The number is exactly the specified value.
  • Does Not Equal:
  • Greater Than:
  • Less Than:
  • Greater Than or Equal To:
  • Less Than or Equal To:
  • Is Empty: No number entered.
  • Is Not Empty: A number is present.
  • Is Selected / Equals: A specific option is chosen (for Radio/Select) or checked (for Checkbox).
  • Is Not Selected / Does Not Equal: A specific option is not chosen/checked.
  • Contains (for Checkboxes): At least one of the specified options is checked if the checkbox field allows multiple selections.
  • Does Not Contain (for Checkboxes): None of the specified options are checked.
  • Is Empty: No option selected/checked.
  • Is Not Empty: At least one option selected/checked.

​
Defining Actions (The “THEN” Part)

Once the condition(s) are met, an action is performed on the current field (the one whose Properties Panel you are in).
  • Show Field (Most Common): If the conditions are true, this field becomes visible. Often, fields with conditional logic are hidden by default until their conditions are met.
  • Hide Field: If the conditions are true, this field is hidden. This can be used to remove fields if a previous selection makes them irrelevant.
Other Potential Actions (depending on Formora’s capabilities):
  • Require Field: Make this field mandatory if conditions are met.
  • Set Value: Automatically populate this field with a specific value.
  • Skip to Page (for multi-page forms): Jump to a different page in the form.
  • Enable/Disable Field: Make a field interactive or read-only.

​
Multiple Conditions for a Single Field

Often, you’ll need a field to appear based on more than one condition. Formora should allow you to:
  • Add Multiple Rules: Define several distinct conditions that can affect the field.
  • AND Logic: Requires ALL specified conditions in a rule group to be true for the action to occur. (e.g., Show field IF Country IS USA AND Age IS Greater Than 21).
  • OR Logic: Requires ANY ONE of the specified conditions in a rule group to be true for the action to occur. (e.g., Show field IF Inquiry Type IS Support OR Inquiry Type IS Billing).
Look for options to specify “Match all conditions (AND)” or “Match any condition (OR)” when setting up multiple criteria.

​
Use Cases & Examples

  1. Address Forms:
    • Field: “State/Province” (Text Input)
    • Condition: IF “Country” (Dropdown) IS SELECTED “United States” THEN SHOW “State/Province”
    • Condition 2: IF “Country” (Dropdown) IS SELECTED “Canada” THEN SHOW “State/Province”
    Diagram showing State field appearing if USA or Canada is selected for Country.

    Conditional State/Province field based on Country selection

  2. Event Registration:
    • Field: “Dietary Restrictions” (Text Area)
    • Condition: IF “Attending Dinner?” (Checkbox) IS CHECKED THEN SHOW “Dietary Restrictions”
  3. Feedback Forms:
    • Field: “Please Specify Other” (Text Input)
    • Condition: IF “Reason for Contact” (Radio Group) IS SELECTED “Other” THEN SHOW “Please Specify Other”

​
Tips for Effective Conditional Logic

  • Plan Your Flow: Before building, sketch out the logic paths on paper or using a flowchart tool, especially for complex forms.
  • Start Simple: Implement basic conditions first and then add complexity.
  • Test Thoroughly: Check all possible combinations of inputs to ensure your logic behaves as expected. Use the Form Preview extensively.
  • Avoid Circular Logic: Don’t create conditions where Field A depends on Field B, and Field B depends on Field A, as this can lead to unpredictable behavior.
  • Consider Default States: Decide if fields governed by conditional logic should be hidden or visible by default before any conditions are met.
  • Keep it User-Friendly: While powerful, overly complex logic can sometimes confuse users if not implemented intuitively.
Conditional Logic is a cornerstone of modern form building, transforming static questionnaires into interactive conversations. The next section, Using Templates, can help you get started quickly with pre-built forms that might already include some logic.
⌘I