How to create forms with conditional fields in workflows
Forms with conditional fields are ones where certain fields appear or disappear depending on what was filled in before — for example, a "contract number" field that only appears when the request type is "renewal." This simplifies completion and ensures only necessary data is captured.
Why generic forms produce bad data
Forms with all fields always visible create two problems: they confuse whoever is filling them out and capture unnecessary data. The result is forms left incomplete, fields filled in incorrectly and information that's useless in the approval process.
The most common problems:
- Mandatory fields that don't make sense for all request types
- Incomplete submissions because the form looks too long
- Captured data that is never used in the approval flow
- Misinterpretation errors about what to fill in each situation
What a well-configured conditional form does
- Shows only the fields relevant to the selected context
- Makes completion faster and less error-prone
- Ensures that data needed for each process path is present
- Can make fields mandatory only when necessary
Why Jestor solves this
In Jestor, forms support conditional fields natively — without code and without technical configuration. It's possible to define rules like:
- "If request type = purchase, show value and supplier fields"
- "If value above $50,000, show mandatory justification field"
- "If requesting department = HR, show HR-specific fields"
These rules are configured visually, directly in Jestor's form editor.
Where Jestor stands out in conditional forms
- Conditional fields configurable without code in the form editor
- Conditional mandatory fields: required only when a condition is met
- Form integration with pipeline automations
- Public forms (no login required) for external requests
How to apply it in Jestor
- Identify the types of requests the form needs to cover
- Map which fields are needed for each type
- Create the form in Jestor and configure visibility rules per field
- Define which fields are mandatory in each context
- Test each combination of responses before publishing the form
FAQ
Do conditional fields in Jestor work on public forms? Yes. Jestor's public forms support conditional fields the same way internal ones do.
Can I use a field's value to determine the routing within the pipeline? Yes. Form fields feed pipeline automations. Learn more at jestor.com.
Is it possible to have mandatory fields that depend on context? Yes. Mandatory status can be conditional — active only when a specific option is selected.
With Jestor, you can automate workflows, connect departments and build internal systems your way — all without code and with AI support. Discover Jestor at jestor.com and take your company's operations to a new level of efficiency and integration.