Using Field Conditions

What Are Field Conditions?

Field Conditions allow Forms to dynamically adjust based on user input.

Using conditional logic, you can control how fields behave depending on the values of other fields.

For example:

Making a field required only when another field has a specific value
Showing or hiding fields based on selections
Automatically setting a field’s value

This helps guide users through Forms and ensures that the correct information is collected.

How Field Conditions Work

Field Conditions follow a simple structure:

If another field meets a condition → Then update this field’s properties

Conditions are applied to the field being affected, not the field triggering the condition.

Creating a Field Condition

Field Conditions can be added after a Form has been saved.

To create a condition:

Edit an existing Form
Locate the field you want to control
Select “Add a Field Condition…”
Choose the field that will trigger the condition
Define the condition (e.g., “Value is exactly Yes”)
Select what property to update

Below is an example screenshot of creating a field condition on a “Custom ESI Protocol” field:

Example: Making a Field Required

Scenario:
If the “Load Images Into Database” field is set to Yes, require the “Load File” field.

Configuration:

Trigger Field: Load Images Into Database
Condition: Value is exactly Yes
Action: Set “Load File” to Required

Result:
When a user selects Yes, the “Load File” field becomes required.

What Can Be Controlled

Field Conditions can modify the following properties:

Requirement
- Required
- Not Required
Visibility
- Visible
- Hidden
Value
- Automatically set or update a value

Multiple properties can be updated by a single condition.

Important Behavior to Understand

Conditions Are Triggered by User Interaction

Conditions only run when a user changes a field’s value.

They do not:

Run automatically when a Form first loads
Trigger from default values alone

Conditions Do Not Automatically Revert

Once a condition changes a field, it stays that way, even if the triggering condition is no longer true.

To create reversible behavior:

Define a second condition with the opposite logic (this is common in hide/show logic behavior)

Multiple Conditions

Multiple conditions can be applied to the same field
Conditions are evaluated independently (OR logic)
If multiple conditions affect the same property, the most recently created condition takes precedence

Supported Conditions by Field Type

The available conditions depend on the type of field being evaluated.

Text Fields (Basic & Rich Text)

Any Value
No Value
Text is exactly
Text contains
Text does not contain

Number Fields (Whole & Decimal)

Any Value
No Value
Number is exactly
Number is Not Exactly
Greater than / Greater than or equal to
Less than / Less than or equal to

Yes or No

Any Value
No Value
Value is exactly

Date Fields (Date Only & Date and Time)

Any Value
No Value
Date is on
Date is Not On
Date is after
Date is on or after
Date is before

Choice Fields (Single & Multiple Choice)

Any Value
No Value
Choice is exactly
Choice is not exactly
Choice is any of
Choice is none of

Reference Fields

Any Value
No Value
Choice is Exactly
Choice is Not Exactly
Choice is Any Of
Choice is None Of
Display Value Contains
Display Value Does Not Contain

Best Practices

Keep logic simple when possible
Complex conditions can be difficult to maintain
Use visibility to reduce clutter
Show fields only when relevant
Pair conditions for reversible behavior
Always define both on and off states when needed
Test your Forms thoroughly
Walk through different scenarios to ensure conditions behave as expected. Forms have a preview mode you can use to test.