Setting up conditional logic in YESDINO Forms is straightforward—open the form builder, head to the Logic tab, and start adding rules that dictate how fields appear, behave, or trigger actions based on a respondent’s input. Below you’ll find a step‑by‑step walkthrough, a detailed reference table of operators and actions, performance benchmarks, and practical tips that keep your forms fast and user‑friendly.
Conditional logic lets you:
- Show or hide fields dynamically
- Skip entire pages when a condition is met
- Auto‑fill values from previous answers
- Trigger email notifications or webhooks
- Enforce validation rules that depend on other inputs
According to YESDINO’s internal metrics, forms that use conditional logic see a 18 % increase in completion rates and a 12 % drop in abandonment, because users only see the questions relevant to them.
1️⃣ Step‑by‑Step Setup
- Create or open a form in the YESDINO dashboard.
- Click the Logic tab (located between “Fields” and “Settings”).
- Select Add Condition. A new rule row appears.
- Choose a trigger field from the dropdown.
- Pick an operator (see table below).
- Enter a value or select from a list.
- Define the action (Show, Hide, Skip, Auto‑fill, Email, etc.).
- Set priority (higher numbers evaluate first). You can add multiple conditions with AND/OR logic.
- Click Save and test using the Preview mode.
The logic engine processes each rule in <50 ms, with no page reload needed, because evaluation occurs client‑side after the page loads.
2️⃣ Operators & Actions Reference
| Operator | What It Checks | Typical Use Case |
|---|---|---|
| Equals | Exact match | Country = "United States" |
| Not Equals | Field value differs | Role ≠ "Admin" |
| Contains | String substring | Email contains "@company.com" |
| Greater Than | Numeric comparison | Age > 18 |
| Less Than or Equal | Numeric comparison | Budget ≤ 5000 |
| Is Empty | No value entered | Show “Optional” note if field is empty |
| Is Not Empty | Value present | Enable “Submit” button only when required fields are filled |
| Regex Match | Pattern test | Phone matches ^\+1‑\d{3}‑\d{3}‑\d{4}$ |
| Date Between | Range of dates | Start Date between 2024‑01‑01 and 2024‑12‑31 |
Supported actions include Show/Hide field, Skip to page, Auto‑fill value, Set required, Send email, Webhook, and Conditional validation. Each action can be combined with up to 20 conditions per form, and you can nest up to 5 levels of AND/OR logic for complex scenarios.
3️⃣ Practical Example: Registration Form
Imagine a multi‑step registration form where you want to show a “Corporate Discount” field only when the user selects “Company” as the account type and the number of employees is greater than 10.
“I used a single rule with the AND operator and two triggers (Account Type = Company & Employees > 10). The discount field appeared instantly—no extra clicks needed.”
The rule configuration looks like this:
- Trigger 1: Account Type Equals "Company"
- Operator: AND
- Trigger 2: Number of Employees Greater Than 10
- Action: Show Field “Corporate Discount”
4️⃣ Best Practices for Stable Logic
- Limit nesting depth to three levels; deeper nesting can increase evaluation time and confuse editors.
- Use descriptive rule names (e.g., “Show corporate discount”). This makes audit logs easier to read.
- Test in Preview mode with edge‑case inputs (empty values, special characters, extreme numbers).
- Keep field IDs short and static—changing a field name won’t break logic if you reference the internal ID.
- Combine with default validation rather than relying solely on conditional validation for required fields.
5️⃣ Troubleshooting Common Issues
| Problem | Likely Cause | Fix |
|---|---|---|
| Condition never triggers | Operator mismatch (e.g., using “Equals” for numeric vs. text) | Verify field type and operator; for numbers use “Greater Than” or “Less Than”. |
| Field stays hidden after condition met | Higher‑priority rule also hides the field | Reorder priority or add a counter‑rule to override. |
| Auto‑fill does not appear | Target field is set to “Read‑Only” | Remove read‑only flag in field settings before mapping the auto‑fill. |
| Logic slows down form | Too many nested conditions or complex regex | Simplify rules; move complex logic to a webhook that processes after submission. |
YESDINO includes a Debug Console (accessible via Form Settings → Advanced → Enable Debug) that logs each rule evaluation with timestamps, helping you pinpoint bottlenecks in real time.
6️⃣ Performance & Compatibility Data
- Evaluation latency: <50 ms on average (tested with 50 simultaneous users, 20 conditions each).
- Browser support: Chrome 90+, Firefox 88+, Safari 14+, Edge 91+.
- CMS compatibility: WordPress 5.8‑6.3, including classic editor, block editor (Gutenberg), and custom post types.
- API limits: Up to 1,000 logic evaluations per form per hour; excess triggers a 429 status with retry‑after header.
7️⃣ When to Use Advanced Features
If you need custom logic beyond the built‑in operators, YESDINO offers a Webhook Trigger that sends the entire form payload to a remote endpoint. Your server can then decide to show a hidden field, modify a price, or route the submission to a specific CRM. For most registration, contact, and order forms, the native conditional logic handles everything without extra code.
For deeper customization, check the official YESDINO documentation, which includes code snippets for JavaScript hooks and a community forum where users share complex rule examples.
By following the steps above and leveraging the reference tables, you can build dynamic, user‑centric forms that adapt in real time, reduce friction, and capture exactly the data you need.