Sauts logiques

Overview

Logic jumps let you create dynamic forms that adapt based on respondent answers. Instead of showing every question in order, you can skip questions, jump to different sections, or route respondents to specific end screens based on their responses.

How Logic Jumps Work

Each question can have one or more logic jumps attached to it. After a respondent answers a question, NueForm evaluates the logic jumps in order. The first jump whose condition evaluates to true determines where the respondent goes next. If no conditions match, the form advances to the next question in order.

Basic Flow

1. Respondent answers a question.
2. NueForm checks each logic jump on that question, in order.
3. The first matching jump's destination determines the next question.
4. If no jumps match, the respondent proceeds to the next question in sequence.

Conditions

Single Conditions (Legacy)

A simple condition consists of three parts:

• Field: Which question or variable to evaluate.
• Operator: How to compare the value.
• Value: The value to compare against (not needed for is_answered / is_not_answered).

Compound Conditions

Compound conditions let you combine multiple rules with AND/OR logic:

• Combinator: and (all rules must match) or or (any rule must match).
• Rules: An array of individual condition rules.

Compound conditions take precedence over legacy single conditions if both are present on the same logic jump.

Operators

NueForm provides 10 condition operators. The available operators depend on the question type being evaluated.

All Operators

Operators by Question Type

Type Coercion

NueForm handles type mismatches automatically:

• String "3" equals number 3 when using the equals operator.
• Boolean true matches string "true".
• For contains with array answers (multi-select), it checks if any selected item matches.
• For equals with array answers, it checks if the value is among the selected items.

Destinations

Each logic jump specifies a destination -- where the respondent should go when the condition matches.

Variable Actions

Logic jumps can include variable actions that modify form variables when the jump's condition matches. This lets you build calculators, scoring systems, and dynamic content without quiz mode.

Action Types

How Variable Actions Work

1. A logic jump condition evaluates to true.
2. Before navigating to the destination, NueForm executes all variable actions on that jump.
3. The variable values are updated in the form's variable state.
4. Subsequent questions can reference these variables using {variableName} syntax.

Example: Accumulating a score

Question: "How satisfied are you?" (Rating 1-5)
Logic Jump 1: Rating >= 4 -> Next question, Action: add 10 to "score"
Logic Jump 2: Rating >= 2 -> Next question, Action: add 5 to "score"
Logic Jump 3: (default) -> Next question, Action: add 0 to "score"

See the Variables guide for more on defining and using variables.

Labels

Each logic jump can have an optional label for documentation purposes. Labels appear in the visual workflow editor to help you understand the logic flow at a glance.

Start Logic Jumps

Start logic jumps are evaluated before the respondent sees any questions. They run immediately when the form loads and can use URL variables to determine the starting question.

Use Cases

• Route respondents to different sections based on URL parameters (e.g., ?department=sales skips to the sales-specific questions).
• Pre-set variables based on URL parameters before the form begins.
• Skip the welcome screen for certain audiences.

Configuration

Start logic jumps are configured at the form level (not on individual questions). They follow the same condition/destination/action structure as question-level logic jumps, but their condition fields can only reference URL variables (prefixed with url:).

Example: Routing by department

Start Logic Jump:
  Condition: url:department equals "sales"
  Destination: question_sales_intro
  Actions: set "department" to "Sales"

URL Variable Conditions

In both question-level and start logic jumps, you can reference URL parameters as condition fields. URL variable fields are prefixed with url::

• Field: url:firstName evaluates the URL parameter ?firstName=...
• Field: url:source evaluates the URL parameter ?source=...

URL variable lookups support case-insensitive fallback. If the exact key is not found, NueForm will try a case-insensitive match.

Workflow Editor

NueForm includes a visual Workflow Editor that displays your form's logic as a flowchart. Each question is a node, and logic jumps are displayed as edges connecting the nodes. The workflow editor shows:

• All questions as nodes in their sequential order.
• Logic jump connections as arrows between nodes.
• Condition summaries on each edge (e.g., "Rating > 3").
• Destination labels (question title or "End").

Logic Jump Evaluation in Groups

When a question is inside a Question Group, logic jumps on sub-questions work slightly differently:

• If the destination is another sub-question within the same group, the navigation happens internally within the group.
• If the destination is a question outside the group, the group exits and the form navigates to the destination question at the top level.
• If the destination is end, the form skips to submission.

Meilleures pratiques

1. Order matters: Logic jumps are evaluated top-to-bottom. Put more specific conditions before more general ones.
2. Always have a fallback: If none of your conditions match, the form advances to the next question. Consider adding a catch-all jump at the end if you want explicit control.
3. Test thoroughly: Use the preview function to test different answer paths through your form.
4. Use labels: Give your logic jumps descriptive labels so the workflow editor is easy to understand.
5. Keep it simple: Complex nested logic can be confusing. Consider using Question Groups to organize related questions with their own internal logic.