Skip to main content

Add Conditions to Custom Fields

Show, hide, disable, or require fields dynamically based on user input.

Updated over 3 weeks ago

Conditions allow you to control how custom fields behave based on the values entered in other fields. With conditions, you can automatically hide fields, make them required, or disable them to guide users through clean and accurate data entry.

This feature is especially useful when you want to show additional fields only when certain criteria are met—for example, displaying calibration fields only when a calibration interval is defined.

You can also combine multiple conditions using AND and OR logic, giving you full flexibility in designing structured and dynamic forms.

Follow these steps to learn how to add conditions.

  1. Open the Custom Field Editor

    • Click on an existing custom field or create a new one to open the field editor window.

  2. Navigate to the Conditions Section

    • Inside the custom field settings, find the Conditions section at the bottom.

    • This is where you define when the field will be hidden, required, or disabled.

  3. Add Your First Condition

    • Click + Add Rule or + Add Condition to start defining logic.

    • Each rule consists of two parts:

      • When → Choose the field and condition (e.g., “Calibration Interval (Months) is equal to 0”).

      • Then → Select what should happen: Hide, Require, or Disable.

    • By default, the field is always shown unless a condition triggers a change.

    The Conditions section is shown before any rules are added, displaying an empty state with the Add Rule button used to create new conditional logic.
  4. Choose the Trigger Field

    • Under When, open the dropdown and select one of your existing custom fields.

    • Next, choose the operator (e.g., Is equal to, Is greater than, Contains) and enter the value that activates the condition.

    • Example from the screenshot:

      • When: Calibration Interval (Months) → Is equal to → 0

  5. Select the Action (Hide, Require, or Disable)

    • Under Then, choose what should happen when the condition is met:

      • Hide → The field is not visible on the form

      • Require → The user must fill in the field

      • Disable → The field becomes non-editable

    • This allows you to create adaptive forms that respond to user selections.

    A single-condition rule is configured, where the field will be hidden when the selected condition evaluates as true.
  6. Add Multiple Conditions (AND / OR Logic)

    • You can define several conditions for a single field:

      • Multiple conditions within one rule use AND logic

        → All conditions must be met for the action to trigger.

      • Multiple rules use OR logic

        → If any rule is satisfied, the action will apply.

    • This gives you full control over complex visibility and validation behavior.

    A single-condition rule is configured, where the field will be hidden when the selected condition evaluates as true.
  7. Save Your Conditions

    • When you're finished configuring your logic, click Save to apply the changes.

    • Your field will now behave dynamically based on the conditions you've created.

  8. Review the Result in Your Entity

    • Open a record for the entity you updated (e.g., a tool).

    • Test the conditional behavior by entering values—fields will automatically show, hide, require input, or become disabled depending on the conditions you set.

Did this answer your question?