The Logic tab controls the dynamic behavior of a form. It allows admins to define rules that automatically react to user input as the form is being completed. These rules evaluate values entered by the user, compare them against defined conditions, and trigger specific actions in real time.
Logic rules are directly based on the structure designed in the Designer tab. Only fields that exist in the form can be used in Logic.
As users interact with those fields, the logic engine continuously listens for changes and determines whether a rule’s conditions are met.
This system enables the creation of intelligent, responsive forms that adapt to the user’s answers, display only relevant information, guide completion flow, and reduce data entry errors.
how logic works
Each logic rule follows a simple three-step flow:
User action → Rule condition → System response
When a user enters or modifies a value, the logic engine evaluates that value against the rule’s conditions. If the conditions are met, the configured action is executed immediately.
For example, if the Country field value equals USA, the system enables the State field.
If the value is anything else, the State field can be hidden, disabled, or reset.
This flow can be represented as:
Value → Filter → Action
value
The Value selector defines which field the rule listens to.
Only fields that are already added to the form (from the Designer tab) are available. Selecting a value instructs the system: “When the user interacts with this field, evaluate its value and apply the rule.”
This is always the starting point of a rule and represents the If this field… part of the logic.
filters in the logic tab
Filters define how the selected field value is evaluated. They represent the If this value… is / is not something part of a logic rule.
| Filter | Definition | Example |
| Empty | Returns true when the field has no value and is completely blank. | A Phone Number field is empty because the user did not enter anything. |
| Not Empty | Returns true when the field contains any value. | A Client Email field contains john@example.com. |
| Equals | Checks if the field value exactly matches the specified value. | Status equals Closed. The condition is true only when the value is Closed. |
| Does Not Equal | Checks if the field value is different from the specified value. | Priority does not equal High. The condition is true for Medium or Low. |
| Contains | Checks if the field includes the specified value (text or list fields). | A Notes field contains payment. A multi-select field contains Urgent. |
| Does Not Contain | Checks that the field does not include the specified value. | A Tags field does not contain Follow Up. |
| Greater Than | Returns true when the field value is greater than the comparison value (numeric or date fields). | Outstanding Balance > 100. Due Date > today. |
| Less Than | Returns true when the field value is less than the comparison value (numeric or date fields). | Outstanding Balance < 100. Due Date < today. |
| Greater Than or Equal To | Returns true when the value is equal to or greater than the comparison value (numeric or date fields). | Outstanding Balance ≥ 100. Due Date ≥ today. |
| Less Than or Equal To | Returns true when the value is equal to or lower than the comparison value (numeric or date fields). | Hours Worked ≤ 40. Start Date ≤ 01/01/2025. |
actions available in the logic tab
Actions define what happens when a rule’s conditions are met. They represent the final outcome of the rule.
| Action | What It Does | Example | Notes / Considerations |
| Show Field / Hide Field | Makes a field visible or invisible based on the rule condition. | If User Type = Manager, show Manager Code. | Hidden fields keep their value unless reset. Remove Required before hiding to avoid blocking submission. |
| Enable Field / Disable Field | Allows or prevents user interaction while keeping the field visible. | If Status = Closed, disable Due Date. | Disabled fields retain values and can still be used in logic. Reset if needed. |
| Make Field Required | Marks a field as mandatory before submission. | If Has Company Car = Yes, require Car License Plate. | Do not hide required fields. Add rules to remove the requirement when needed. |
| Reset Field Value | Clears the current value of a field. | If Country ≠ Colombia, reset State/Province. | Affects only the current session. Useful when hiding or disabling fields. |
| Set Field Value | Automatically assigns a predefined value to a field. | If User Role = Admin, set Access Level = Full. | Later rules may override earlier ones. Avoid conflicting logic. |
| Complete Form | Ends the form immediately, as if submitted. | If Agreement = No, complete form. | Prevents further changes. Use carefully, especially early in the form. |
| Copy Answer | Copies a value from one field to another. | Copy Primary Email into Contact Email. | Destination field must meet validation rules. Handle future changes carefully. |
| Skip to Field | Jumps the user to a specific field or section. | If Has Pets = No, skip Pet Details. | Skipped fields may still require input unless hidden or disabled. |
and / or conditions
The Logic tab allows multiple conditions to be combined within a single rule.
AND
All conditions must be true for the rule to trigger.
For example, if Country = USA AND Customer Type = Business → show “Tax ID”.
OR
At least one condition must be true.
For example, if Country = USA OR Country = Canada → show “Region”.
Combined Logic
AND and OR can be mixed to refine rule behavior (if supported).
For example, (USA OR Canada) AND Business → show additional compliance fields.
The Logic tab powers intelligent forms. By responding to user input in real time, it ensures that forms remain relevant, efficient, and accurate. Well-designed logic improves the user experience, reduces errors, and guarantees that collected data aligns with business rules and workflows.
Comments
0 comments
Please sign in to leave a comment.