Types de questions de mise en page

Statement

A display-only question that shows text to the respondent without requiring an answer. Useful for instructions, section transitions, or informational content.

Type identifier: statement

Properties

Behavior

• The question number is not displayed for statements.
• No input field is shown.
• The respondent clicks the button to advance to the next question.
• Statements are never "required" since they have no answer to validate.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

Statements do not produce an answer. The value is effectively undefined.

Welcome Screen

An introductory screen displayed at the beginning of the form, before any questions.

Type identifier: welcome_screen

Properties

Behavior

• The welcome screen is displayed before Question 1.
• The title and description support rich text and {variable} substitution.
• Clicking the button begins the form.

Answer Format

Welcome screens do not produce an answer.

End Screen

A closing screen displayed after the form is submitted. In quiz modes, multiple end screens can be added with conditional display based on the respondent's score.

Type identifier: end_screen

Properties

Standard Mode Behavior

In standard mode, a single end screen replaces the default thank-you screen. Its title and description are displayed after submission.

Quiz Mode Behavior

In quiz modes, multiple end screens can be defined:

• Knowledge Quiz / Lead Qualification: The end screen with a scoreRange matching the respondent's total score is displayed.
• Match Quiz: The end screen that accumulated the most tallies from the respondent's choice outcomes is displayed.

End screen questions appear in the question list but are not shown during the form flow. They are only rendered after submission based on the scoring logic.

Answer Format

End screens do not produce an answer.

Summary

A review screen that displays all the respondent's answers before final submission. The respondent can review their answers and optionally go back to edit any question.

Type identifier: summary

Properties

Behavior

• The summary displays all answered questions with their responses.
• Each question in the summary is clickable, allowing the respondent to jump back to that question and edit their answer.
• The question number prefix is hidden.
• Two buttons are presented: confirm (submit) and edit (go back).

Dependencies

The Summary question requires access to all questions and all answers. The form renderer passes allQuestions, allAnswers, onGoToQuestion, and onRestart props to this field.

Answer Format

The Summary question does not produce its own answer. It is a display-only component.

Save Answers

Offers respondents the option to save their current answers to their browser's local storage. When they visit another NueForm form, any previously saved answers can be pre-populated.

Type identifier: save_questions

Properties

The Save Answers question type has no additional properties beyond the common question properties.

Behavior

• Displays the respondent's current answers.
• Offers a button to save the answers to local storage.
• Saved answers are keyed by question title, so if a future form has a question with the same title, the answer is pre-populated.
• The question number prefix is hidden.

Use Case

This is useful for multi-form workflows where respondents fill out several related forms. Common information (name, email, company, etc.) can be saved once and auto-filled in subsequent forms.

Answer Format

The Save Answers question does not produce its own answer. The saved data is stored in the browser's local storage.

Question Group

Groups multiple sub-questions into a single form step. The sub-questions are presented one at a time within the group, with internal navigation. This allows you to create sections of related questions that function as a single unit in the overall form flow.

Type identifier: question_group

Properties

Behavior

• The group appears as a single step in the overall form.
• Sub-questions are presented one at a time with forward/backward navigation within the group.
• Each sub-question can have its own logic jumps. If a logic jump's destination is:
  • Another sub-question within the group: navigation happens internally.
  • A question outside the group: the group exits and navigation continues at the top level.
  • end: the form skips to submission.
• The "Back" button navigates within the group first. If the respondent is on the first sub-question, pressing "Back" exits the group and goes to the previous top-level question.
• The question number prefix is hidden for the group container.

Sub-Question Logic

Logic jumps on sub-questions can reference answers from other sub-questions within the same group, or answers from top-level questions outside the group (via the flatAnswers map).

Variable actions on sub-question logic jumps execute against the same variable state as the parent form.

Validation

Each sub-question within the group is validated individually. The respondent must satisfy each required sub-question as they navigate through the group.

Sub-questions that are skipped by internal logic jumps are not validated (their required constraint is waived).

Answer Format

The answer is stored as an object (Record<string, unknown>) mapping each sub-question ID to its answer:

{
  "sub_q1": "John Smith",
  "sub_q2": "john@example.com",
  "sub_q3": 5
}

Multi-Question Page

Displays multiple questions on a single screen simultaneously. Unlike Question Groups (which show one sub-question at a time), Multi-Question Pages show all their sub-questions at once.

Type identifier: multi_question_page

Properties

Behavior

• All sub-questions are rendered on a single screen.
• The respondent fills in all visible questions and clicks a single "OK" button to proceed.
• The question number prefix is hidden for the container.
• Logic jumps on sub-questions can trigger navigation to questions outside the multi-question page.

Validation

All required sub-questions must be answered before the page can be submitted. Validation errors are shown inline next to the relevant sub-question.

Answer Format

The answer is stored as an object (Record<string, unknown>) mapping each sub-question ID to its answer:

{
  "sub_q1": "Jane Doe",
  "sub_q2": "jane@example.com",
  "sub_q3": "Engineering"
}

Markdown

A rich content block that supports Markdown formatting with inline form fields. You can embed text inputs, dropdowns, and other interactive elements directly within Markdown content.

Type identifier: markdown

Properties

Inline Field Syntax

Embed form fields within your Markdown using double curly braces:

{{type:label}}

Where type is the field type and label is the display label for the field.

Behavior

• The question header (title and description) is hidden for Markdown questions. The Markdown content IS the question.
• Inline fields are parsed from the Markdown content and rendered as interactive inputs within the text.
• The respondent fills in the inline fields and submits the entire Markdown block as one answer.

Validation

Each inline field follows its own validation rules based on its type.

Answer Format

The answer is stored as an object (Record<string, unknown>) mapping each inline field label to its value.