Building a questionnaire 

Condition type: Specific answer 

1. Open the Visibility Conditions tab of the question that should be conditionally shown.
2. Click Create new Condition.
3. Set Condition type to Specific answer.
4. Select the Reference question — the earlier question whose answer decides visibility.
5. Select the Reference answer — the answer option that must have been chosen.
6. Save.

Condition type: Scale value 

Use this when the reference question is a Scale / Rating question and visibility depends on the number the visitor picked.

1. Open the Visibility Conditions tab.
2. Click Create new Condition.
3. Set Condition type to Scale value.
4. Select the Reference question; only scale questions qualify.
5. Choose an Operator: >=, <=, >, < or =.
6. Enter a Value to compare against.
7. Save.

For example: show a follow-up question only when the visitor rated satisfaction >= 8.

Multiple conditions 

A question can have more than one condition. Each condition has an Operator field of its own:

Conditions are evaluated in the order they appear in the list, top to bottom. See Condition evaluation for the exact evaluation order.

Rules 

• Conditions can only reference questions that appear earlier in the questionnaire. Keeping to that is the editor's responsibility; nothing enforces it.
• A question with no conditions is always shown.
• Skipped questions count neither toward the progress nor the score.
• For a Scale value condition: when the referenced question has not been answered, the condition fails and the dependent question stays hidden.

Example 

Q1: What is your situation?
    → "Employed"           → show Q2a (work questions)
    → "Self-employed"      → show Q2b (entrepreneur questions)
    → "Looking for work"   → show Q2c (job-seeker questions)

Q2a has one condition: type Specific answer, reference question Q1, reference answer "Employed". Q2b and Q2c work the same way with their own answer.

Trigger — when does this result apply? 

When Scale answer range is selected, three extra fields appear: the Scale question whose answer is checked (only scale questions are listed), and the inclusive Minimum value and Maximum value.

Outcome — what happens when it applies? 

The fields of an inline outcome:

Inverting a condition 

Invert turns a specific answer condition around: the block appears when the visitor did not choose that answer.

That is useful for advice which only applies to people who skipped something. Take a question about organ donation with an option "I have already registered my choice". Attach a block to that option, tick Invert, and everyone who did not register gets the reminder — while the people who did are spared a message that does not apply to them.

Grouping blocks under a heading 

A long result page reads better in sections. Set Show this block to Group heading above other blocks to turn a block into a heading, then set Part of group on every block that belongs underneath it.

What to keep in mind:

• A group heading has no condition of its own. It appears automatically when at least one block in its group is visible, and disappears when none are. The heading's visibility never has to be maintained by hand.
• A group heading has no content — only a headline.
• The headline of a grouped block moves one heading level deeper than an ungrouped one. That matters for the rich text in the body: sub-headings inside a grouped block belong on Heading 5, not Heading 4. Using the wrong level skips a level in the document outline, which screen readers and search engines both read as an error. See Heading levels, and why the RTE needs Heading 4 and Heading 5 for what an administrator has to make available in the RTE.
• Blocks that are not part of any group keep their normal level and can sit before, between or after the groups.

Questionnaire structure 

• Start with a sketch on paper of the question flow and the possible outcomes before building anything in the backend.
• Use descriptive internal titles on questionnaire and result page records; the next editor will thank you.
• Store questionnaire records in a dedicated sysfolder.

Conditions 

• Only reference questions that appear above the current one in the list.
• Test the branching by walking through the questionnaire as a visitor — condition mistakes are easy to miss in the backend.
• Use the Start over button while testing to reset the session. It only appears after the first answer has been submitted.

Result pages 

• Always add a catch-all result as the last entry. Without it, a visitor who matches no trigger sees an error message.
• For score-based questionnaires, make sure the score ranges cover every possible total without gaps.

Scoring 

• Scores can be positive or negative: +2 for a healthy choice, -1 for a risk factor.
• The score is only shown to the visitor when settings.show_score is on.
• Advice blocks with a score condition work whether or not the score is displayed.

Reuse 

• The same questionnaire record can be placed on multiple pages — useful for embedding the same tool in different contexts.
• Each placement has its own settings, so the score can be shown on one page and hidden on another.