Editor Guide — pn_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 determines visibility
5. Select the Reference answer — the specific 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 you want to show or hide based on the numeric value the visitor selected.

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

Example: Show a follow-up question only if the visitor rated satisfaction >= 8.

Multiple conditions 

You can add more than one condition per question. Each condition has an Operator field:

Conditions are evaluated in the order they appear in the list (top to bottom, by sort order).

Rules 

• Conditions can only reference questions that appear earlier in the questionnaire. It is your responsibility to ensure this.
• A question with no conditions is always shown.
• Skipped questions do not count toward progress or score.
• For Scale value conditions: if the referenced question has not been answered yet, 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 a condition: type = Specific answer, reference question = Q1, reference answer = "Employed". Q2b has a condition: type = Specific answer, reference question = Q1, reference answer = "Self-employed". Q2c has a condition: type = Specific answer, reference question = Q1, reference answer = "Looking for work".

Trigger — when does this result apply? 

See §11 for all trigger types.

Outcome — what happens when it applies? 

See §12 for all outcome types.

Inverting a condition 

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

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

Watch out: an unanswered question counts as "not given". If the question is optional, or the visitor never reached it, the answer is absent — so an inverted block will appear. Whether that is what you want depends on the text. A reminder ("don't forget to arrange this") is fine for someone who skipped the question. A statement that assumes a situation ("since you have not arranged this yet") is not. Make the question required if you need the distinction to be reliable.

Grouping blocks under a heading 

A long result page reads better in sections. Set Condition type 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. You never have to maintain the heading's visibility by hand.
• A group heading has no body text — 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.
• Blocks that are not part of any group keep their normal level and can sit before, between or after the groups.

Tab: Settings 

Tab: Button labels 

The navigation buttons carry a standard text that follows the language of the site. Each of them can be given an own text here, per plugin instance — useful when the questionnaire is a checklist rather than a test, or when the tone of the page asks for something else than "Next".

The standard text of each field is shown in grey as long as the field is empty, and an empty field keeps that standard text. There is no need to fill in all of them.

The last two only appear once their function is switched on in Storing and mailing the result: the copy button belongs to the retrieval link, the send button to the mail form.

Tab: Storing and mailing the result 

Leaving a field empty is meaningful here: the extension then falls back to its own standard text or to the installation's setting. You only fill in what you want to deviate from.

Keeping and sharing the result 

With Store the result on, the result page gains a link the visitor can save or share. Opening it later brings back the same result, without a login and without the visitor's session.

Nothing identifying is stored: no name, no IP address, no e-mail address, not even in hashed form. What is stored is the given answers, the score and a random code that appears in the link. Someone who does not have the link cannot find the result, and the answers cannot be traced back to a person.

Two consequences worth knowing:

• The result disappears once the retention period expires. Say so in the text around the link if visitors are likely to rely on it.
• The link is the only key. A visitor who loses it cannot recover the result, and neither can an administrator.

Point Link to the privacy statement at the page where your organisation explains this. The extension only links to it — the text itself is yours to write, and it should mention the retention period and that no personal data is stored.

Mailing the result 

With Allow mailing the result on, the result page shows a form asking for an e-mail address. The visitor receives the full result plus the retrieval link.

The address is used to send that one mail and is not stored — not in the database, not in a log, not on the stored result.

The mail uses the layout of your TYPO3 installation and is sent as both HTML and plain text. Opening text of the mail and Closing text let you replace the standard lines; leave them empty to keep the defaults.

Leave "Switch off the send limit" off on a live site. The limit is what stops the form from being used to send mail to other people's addresses in bulk. Switching it off is meant for testing an installation, where repeated attempts would otherwise be blocked.

Scale display 

Scale questions have a Scale display field that controls how the input is rendered:

Scale and informational questions are score-neutral — they never add to the total score.

Inline outcome fields 

Multiple links in a result? The result page supports one CTA button. If you need multiple links, add them as hyperlinks inside the Body text field.

Questionnaire structure 

• Start with a sketch on paper of the question flow and the possible outcomes before building in the backend
• Use descriptive internal titles on questionnaire and result page records — editors will thank you later
• Store questionnaire records in a dedicated sysfolder to keep the list module tidy

Conditions 

• Only reference questions that appear above the current question in the list
• Test the branching by going through the questionnaire as a visitor — condition mistakes are easy to miss in the backend
• Use the Start over button during 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, visitors who don't match any specific trigger will see an error message
• For score-based questionnaires, make sure your score ranges cover all possible totals with no gaps

Scoring 

• Scores can be positive or negative (e.g. +2 for a healthy choice, -1 for a risk factor)
• Score is only displayed to the visitor if Show score on result is enabled in the plugin settings
• Advice blocks with score-range conditions work regardless of whether 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 FlexForm settings, so you can show the score on one page but not another