Create a Questionnaire
- Open the Strapi admin panel (strapi.product.f14e.com/admin for production, strapi.staging.f14e.com/admin for staging)
- Go to Content Manager -> Questionnaire
- Click Create new entry
- Fill in the metadata (see details below)
- Add questions in the questions section (see Add Question Types)
- Add rules in the rules section (see Configure Rules)
- Add calculated fields if needed (see Configure Calculated Fields)
- Click Save to save as draft
- Use Preview to test the flow before publishing
Metadata fields — what to fill in
Section titled “Metadata fields — what to fill in”Each field in the metadata section configures a different aspect of your questionnaire. Here is what each one does and how to fill it in.
name (required)
Section titled “name (required)”The internal identifier for your questionnaire. Used in sync commands and must be a slug (a URL-safe name — lowercase letters and hyphens only, no spaces — see Glossary).
Examples: household-insurance, pet-health, dental-basic
This is what you type when running sync commands, e.g., yarn sync:questionnaire -q household-insurance.
slug (required)
Section titled “slug (required)”The URL identifier. In most cases this matches the name field exactly.
Examples: household-insurance, pet-health
vertical (required)
Section titled “vertical (required)”Select the insurance product this questionnaire belongs to. Click the dropdown and search for your product (e.g., Household, Dental, Expat, Pet). Each questionnaire must be linked to exactly one vertical.
If your vertical does not exist yet, you need to create a vertical first.
type (required)
Section titled “type (required)”Choose one of two options from the dropdown:
- singleRegion — This questionnaire targets one country (most common)
- multiRegion — This questionnaire is available in multiple countries with region-specific variations
For most new questionnaires, choose singleRegion. See Multi-Region Questionnaires for the multi-region setup.
regions (required)
Section titled “regions (required)”Select the countries where this questionnaire is available. Click to open the list and select one or more country codes.
Examples: DE (Germany), AT (Austria), ES (Spain)
constants (optional)
Section titled “constants (optional)”A list of reusable key/value pairs that questions or rules can reference. Click + to add entries. Each entry has a key (the name, in camelCase) and a value.
Example: maxAge / 65, minCoverageAmount / 5000
These are useful for values that appear in multiple places (e.g., age limits, coverage thresholds). For details on how to use constants in question text, see Configure Interpolations.
progressBar (optional)
Section titled “progressBar (optional)”Defines the sections shown in the progress indicator at the top of the questionnaire. Each section has a label and a list of groupIds it covers.
For setup instructions, see Configure Progress Bar.
featureFlags (optional)
Section titled “featureFlags (optional)”Toggle experimental or per-questionnaire features. You generally do not need to set these unless instructed by Engineering.
questionList
Section titled “questionList”This is automatically populated as you add questions. You do not need to fill this manually.
Metadata fields reference
Section titled “Metadata fields reference”| Field | Required | Description |
|---|---|---|
| name | Yes | Internal slug, used in sync commands |
| slug | Yes | URL identifier |
| vertical | Yes | Linked insurance product |
| type | Yes | singleRegion or multiRegion |
| regions | Yes | Country codes (e.g., DE, AT, ES) |
| constants | No | List of {key, value} pairs for reusable values |
| progressBar | No | Section definitions for the progress indicator |
| featureFlags | No | Toggle experimental features |
| questionList | Auto | Populated automatically from your questions |
See also
Section titled “See also”- Questionnaire Metadata Reference – complete specification of all metadata fields
- Your First Questionnaire – step-by-step tutorial for building from scratch
- Questionnaire Lifecycle – how a questionnaire moves from CMS to browser