Formulaires — redesign configuration guide

Customer administrator — nextgen / redesign

1. Locate or create a form

Open Performance → Forms [new]. Search by name/creator, filter Draft/Published and Read only, and inspect existing content before creating a new version.

Use the name, creator, publication and read-only filters to locate a form. Read only filters campaign usage; it does not change editing permissions. Search criteria do not modify forms. See functional for each filter.

View full size

The checked UI requires create-form for creation. API routes distinguish read, create, update and delete permissions. Access to the menu alone is insufficient evidence of every action right.

2. Build sections and questions

Start with a title and optional description, then add one or more sections. Give each section a clear heading and, when useful, a short instruction. Use the form overview to review the order before saving. Choose the content language deliberately: it is separate from the interface language. Optional generation can propose content from a sufficiently detailed title; review every generated question and option before keeping it.

Question option	Verified choices / behavior	Effect and validation
Family	Text, numeric, single answer, multiple answers, scale, list, skills, past objectives, future objectives, development, date in the checked builder schema.	Select a family matching the expected answer. Frontend names map to backend question types; they are not interchangeable legacy type codes.
Title / description	Localized content; title and instructions can vary by locale.	Translate the meaning as well as choice labels.
Required	Boolean; checked frontend schema defaults to false.	Required-answer validation applies when completing the participant's preparation. This frontend default is not proof of all server defaults.
Visibility	Employee, evaluators or all.	Selects the question audience; it does not alone determine when another participant sees answers.
Evaluator-specific wording	Optional customization when audience is all.	Backend requires evaluator titles when customization is enabled for all; rejects supplied evaluator wording outside the allowed configuration.
Choice options / counts	Form-defined choices and applicable minimum/maximum selection settings.	Keep labels and allowed counts coherent. Empty choice sets or inconsistent limits need correction before use.
Scale / numeric / date	Type-specific bounds, labels and display settings.	Do not use a legacy rating limit as the nextgen limit. Date questions can have minimum/maximum dates.
List / skills / objectives / development	Referentials, skill selection, periods and specialist options.	Verify the underlying data and participant rights. A development question can depend on the training catalog.
Position / sections	Ordered section/question structure.	Check participant navigation and the preview/overview after reordering.

Generation produces a proposal; review every question, choice, audience and translation before saving or publishing.

3. Save, translate, publish and assign

Save the form before adding content languages. For each language, translate the form title and description, section headings and instructions, question titles and descriptions, evaluator-specific wording and every choice label. Preview each language and correct missing or inconsistent content. Save the finished form, then use its status menu to publish it when it is ready for use. Publication makes the form available for selection; it does not assign employees or start a campaign. Select the published form separately when configuring the nextgen interview campaign.

For example, a bilingual form can combine a required text question with an optional single-choice question. The preview helps authors review the structure and locale, but only completing the assigned campaign shows the respondent workflow and required-answer validation.

4. Manage read-only forms and new versions

Verified in code: FormRepository::formHasActiveCampaign treats use by in-progress, done or archived campaigns as active for the read-only calculation. Draft and not-started campaigns do not count. Thus “read only” and “published” express different conditions.

When changes are needed, inspect existing usage and duplicate into a new version where appropriate. Do not promise that all modifications are permitted simply because a list filter says editable. The backend also validates conditional section structure and specialist answer compatibility. In particular, the development-question opinion scale cannot shrink below the highest already-used opinion. Unpublishing does not establish an undo of prior answers, campaign references or read-only state.

Platform-team reference

Legacy

Activate the appropriate questionnaire/interview capabilities and grant only the required authoring rights. Verify specialized question dependencies, skills and periods. The playbook is a rollout example; its switches and role matrix are not universal defaults.

Nextgen

Legacy shell app/config/neobrain/company/definitions.yml declares smr_settings_forms under enable_new_neobrain_hybrid_platform and smr_settings_forms_access, with nextgen action scopes. API permissions remain separately enforced. Form catalogs require persistence, localized content and referential services.

Optional generation is implemented by nextgen OpenAIFormGenerator, with provider configuration, serialization and cache. The checked implementation does not require routing form generation through AIHub. Provider availability and deployed behavior were not tested; manual authoring remains a separate workflow.

Validation, safe changes and troubleshooting

Before launch, test the selected form with employee and evaluator personas in every intended content language. Check required fields, conditions, options, score scales and expected answer visibility. Inspect both the on-screen result and any generated output required by your process; equivalent PDF visibility across generations is not established.

Issue	What to inspect
Cannot create / update / delete	Respective action right, tenant scope and form/campaign usage.
Evaluator wording rejected	Visibility must be all with customization enabled and evaluator titles provided.
Opinion-scale reduction rejected	Existing development answers require values that would disappear. Keep those values or create a new form version.
Cannot add a language	Save the new form first; check allowed locales.
Generation unavailable	Title length, create permission, provider configuration and service error. Review without repeatedly generating or saving.
Form not found in campaign	Generation, publication, locale and campaign permissions.

Evidence and limitations

Verified in code: legacy Assessment controller/templates; nextgen front src/modules/CompanySettings/Forms/{components/FormsFilters.vue,api/forms.api.ts}, src/modules/ModuleConfig/Campaigns/modules/FormBuilder/{api/formBuilder.api.ts,domain/formBuilder.frontend.schemas.ts}; nextgen back src/Http/Api/Routing/V2/review_form.yaml, src/Domain/V2/ReviewForm/Validator/{ReviewerCustomizationAllowedValidator,OpinionScaleNotShrunkValidator}.php, src/Infrastructure/Persistence/Repository/ReviewForm/FormRepository.php, src/Infrastructure/Service/ReviewForm/AI/OpenAIFormGenerator.php.

Documented in Confluence: Playbook – Interviews, v11, 6 September 2023; SMR models, v1, 13 March 2026. PS methodology, v7, and onboarding, v9, were checked as general context, not form-setting specifications. KBCT 2136702980 is the FAQ folder.

Application coverage: a synthetic nextgen form was created with one section, a required text question and a single-choice question; French and English content were saved, the English preview was reviewed and the form was published. It was not assigned to a campaign, so the respondent flow and answer validation were not observed. Defaults for every question family, all conditional options and legacy migration remain outside this guide's verified scope.