Add field dependencies in a registration form

Achieve complex registration workflows with single or multiple dependencies. Adding nested conditionals was never this easy for achieving complex workflows with 'Add' and 'OR' conditional options.

 

Overview:

This guide will walk you through how to set up conditional dependencies in the vFairs registration form. Conditional dependencies allow certain form fields to appear or change based on the responses in previous fields. You can implement either single conditional logic or multiple conditional logic with AND/OR operators, depending on the complexity of your form's requirements.

Prerequisites:

  • Access to the vFairs Admin Panel.
  • An existing registration form with defined fields.
  • A basic understanding of form fields, such as dropdowns, checkboxes, and radio buttons.

Step-by-Step Guide:

1. Access the Registration Form:

  • Go to the Admin Panel.
  • Navigate to the Registration >> form builder >> click on attendee registration form.

2. Identify the Fields for Conditional Logic:

  • Determine which fields will act as triggers (the fields whose values will control the behavior of dependent fields).
  • Define the target fields (the fields that will be displayed or hidden based on trigger values).

3. Setting Up Single Conditional Dependency:

  • Select the target field you want to make conditional.
  • Scroll down to the Field Dependency section.
  • Choose the trigger field (e.g., a dropdown or radio button).
  • Specify the condition (e.g., if the user selects "Yes" from the dropdown, another field will appear).
  • Save the changes.

1: Go to the form and click "Add condition" under the field you want to add the dependency on.

2: Once the condition menu opens, click on the field criteria dropdown to select the field.

3: From the dropdown select the field on which this field would become dependent on.

4: After selection of the field, select the next criteria pointer (contains / doesn't contain).

 

5: Add the criteria for example: "if company name contains vFairs" then click on Add.

6: After the first condition is added, Click on "Add condition" again to add another dependency.

7: You can add another condition with "And" or "OR" logic. "And" means both conditions need to be true and "OR" means even if one is true.

4. Using AND/OR Logic for Multiple Conditions:

  • In cases where multiple fields control the visibility of a target field, you can use AND/OR logic.
  • AND Logic: The dependent field will only appear if all specified conditions are met.
    • Example: If both  A = "Yes" AND B = "No", the target field will not appear.
  • OR Logic: The dependent field will appear if any of the specified conditions are met.
    • Example: If A = "Yes" OR B = "No", the target field will appear.

5. Setting Up Multiple Conditional Dependencies:

  • In the Field Dependency section of the target field, select the first condition.
  • Click Add Condition to create additional dependencies.
  • For each condition, specify whether you want to use AND or OR logic.
  • Configure all the necessary conditions, ensuring the logic is correctly applied.

6. Testing the Conditional Logic:

  • After setting up the conditions, preview the registration form.
  • Test by filling out the form based on different trigger field inputs to confirm the dependencies are working as expected.

7. Finalizing and Saving:

  • Once satisfied with the form's behavior, save the configuration.
  • Test again in the live environment to ensure the conditions remain intact.

Tips:

  • Use clear and concise labels for form fields to avoid confusion when setting up dependencies.
  • Use AND logic when you need strict control over the visibility of fields based on multiple conditions.
  • Use OR logic when you want more flexibility, allowing a field to appear if at least one condition is met.

Common Use Cases:

  • Showing additional details if a user selects a specific option (e.g., displaying dietary preferences if "Yes" is selected for a meal option).
  • Hiding fields unless a specific condition is met (e.g., asking for additional information if a "No" is selected for a question).