> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Use Conditional Fields in Forms
- URL: https://blog.jestor.com/conditional-fields-in-forms/
- Published: 2026-09-17T22:26:59.000Z
- Updated: 2026-09-17T22:26:59.000Z
- Author: Bruno Bannach

**Conditional fields in forms** show or hide a question depending on what was answered before. The respondent sees only what applies to them, and the data that comes back is cleaner because irrelevant fields are never filled.

## Why long forms produce bad data

Every question a respondent does not understand is a chance for a wrong answer or an abandoned form.

- Fields left blank because they did not apply
- Guessed answers to questions meant for a different case
- Abandonment partway through a form that felt endless
- Cleanup work afterwards to separate real answers from noise

## Where conditionals earn their place

| Situation                  | What the conditional does                           |
| -------------------------- | --------------------------------------------------- |
| **Rejection reason**       | Appears only when a request is marked refused       |
| **Company size branch**    | Routes to different follow-up content per segment   |
| **Phase-specific fields**  | Shows only what matters at the card's current stage |
| **Threshold-based fields** | Reveals extra detail when a value crosses a limit   |

## How to configure it in Jestor

1. Open the Super Form editor in **Jestor**.
2. Select the field or block you want to control.
3. Set the condition — which other field, and which value, triggers it.
4. Apply conditionals to connected table blocks as well, not just simple fields.
5. Combine conditionals with phases so each stage of a **Kanban** shows its own fields.

## Why choose Jestor for conditional logic?

**Jestor** applies conditionals across the whole form system: simple fields, blocks, connected tables, and open cards. The same rule that hides a field on a public form hides it inside the card an approver sees.

This is what keeps approval and request forms short. A cancellation reason appears when something is cancelled, and stays invisible the rest of the time.

## Frequently Asked Questions

### Can conditionals depend on a numeric threshold?

Yes, a field can appear when a value crosses a limit you define.

### Do they work inside open cards?

Yes, the same rules apply. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can a whole block be conditional?

Yes, not just individual fields.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.