Form Conditional Logic | Uplup
Create smart forms that adapt based on user responses. Uplup forms have two layers of conditional logic: page-level Logic Rules (route users to different pages based on answers) and field-level Field Visibility (show, hide, or require fields based on other answers).
Table of Contents
- The Logic Tab — Rules & Flowchart
- Page-Level Logic Rules
- Field Visibility (Show / Hide / Make Required)
- Available Operators by Field Type
- Common Use Cases
The Logic Tab — Rules & Flowchart
Open any form and click the Logic tab in the top navigation (between Create and Connect). The Logic tab has two views you can toggle between in the top-right corner:
- Rules — A list of every page in your form. Click Add rule on any page to create branching logic.
- Flowchart — A visual map (Logic Flow) showing how pages connect. Drag from a page’s connector dot to create routing, or click an existing connection to edit it.
Page-Level Logic Rules
Page-level rules let you skip users to a different page based on how they answered a question on the current page. They work the same whether your form is in the standard multi-field layout or in step-by-step (one question per screen) layout.
Adding a Rule
- Open the Logic tab and stay on the Rules view.
- Find the page you want to add routing from. Pages with at least one question show an + Add rule button.
- Click + Add rule. A new rule card opens with two parts:
- If — pick the question, the operator, and the value to match.
- Then — pick the destination page from the Jump to… dropdown.
- Click + Add rule again to add more rules to the same page. Rules are evaluated in order; the first matching rule wins.
- If none of the rules match, the form falls through to the next page automatically (shown as Otherwise — continue to “[next page]”).
Note: Cover pages, Finish pages, and Payment pages cannot have rules added to them. Rules can only be added to content pages that contain a question field.
Editing a Rule
Click any rule’s dropdowns to change the field, operator, value, or destination. Click the trash icon to delete a rule. Pages with active rules show the rule count next to the field count (e.g., “2 fields · 1 rule”) and a branching icon next to the page name.
Field Visibility (Show / Hide / Make Required)
Field-level conditions are configured directly on each field, not in the Logic tab. Use them when you want a field on the same page to appear, disappear, or become required based on the answer to another field on that page.
Opening the Field Visibility Popover
- Open the Create tab.
- Click a field on the canvas to select it.
- In the field’s hover toolbar (top-right of the field), click the branching icon. A popover labeled Field Visibility opens.
Setting Up a Visibility Condition
- Click ON to enable conditional logic for this field.
- Under What should happen? pick one action:
- Show — field appears only when the condition is true.
- Hide — field disappears when the condition is true.
- Make required — field becomes required when the condition is true.
- Under When these conditions are met, build a condition with three parts: the trigger field, an operator, and (when needed) a value.
- Click + Add condition to stack more conditions. All conditions must be true for the action to fire.
- Click Save Changes.
Note: Only fields on the same page as the target field appear in the trigger dropdown. Display-only fields (Heading, Paragraph, Divider, Spacer, Image, Video) cannot use or trigger visibility conditions.
Available Operators by Field Type
The available operators depend on the type of question being checked.
Multiple Choice / Dropdown / Checkbox / Picture Choice / Multi-Select:
- is
- is not
- is answered
- is not answered
Yes/No:
- is
- is not
Number / Star Rating / NPS / Slider:
- equals
- is greater than
- is less than
- is answered
- is not answered
Short Answer / Long Answer / Email / Website / other text fields:
- is exactly
- contains
- is answered
- is not answered
File Upload / Signature:
- has file
- no file uploaded
Common Use Cases
Customer Type Routing (Page-Level Rule)
On a “New or existing customer?” page, add two rules:
- If answer is “New Customer” → jump to the registration page.
- If answer is “Existing Customer” → jump to the account-lookup page.
Qualification Screening (Page-Level Rule)
End early for unqualified respondents:
- If “Are you 18+?” is “No” → jump to the Finish Page.
- If “Are you in a supported region?” is “No” → jump to an ineligibility page.
Business vs Personal Fields (Field Visibility)
On the same page as an “Account Type” field, add Show conditions to extra fields:
- Show “Company Name” when Account Type is “Business”.
- Show “Tax ID” when Account Type is “Business”.
- Show “Purchase Order” when Account Type is “Business”.
Follow-Up Questions (Field Visibility)
Reveal a follow-up only when relevant:
- “Do you have dietary restrictions?” (Yes/No)
- “Please describe” → Show only when the answer is “Yes”.
“Other” Option Detail (Field Visibility)
Show a follow-up text field when a respondent picks “Other”:
- “How did you hear about us?” with an “Other” option.
- “Please specify” text field → Show when the answer is “Other”.
Frequently Asked Questions
Do hidden fields still collect data?
No. If a field is hidden by Field Visibility, its value is not included in the submission.
Can a field be required only when it’s visible?
Yes. When a field is hidden by a visibility condition its required validation is skipped automatically. You can also use the Make required action to flip required on or off based on another field’s answer.
What’s the difference between Page-Level Rules and Field Visibility?
Page-Level Rules (in the Logic tab) move the respondent to a different page. Field Visibility (on each field) shows, hides, or requires individual fields on the current page. You can combine both in the same form.
Which one is evaluated first?
Field Visibility runs as the respondent is filling out the page (it controls what’s visible right now). Page-Level Rules run when the respondent moves to the next page (they control where to go next).