Formulaires — redesign functional guide
Find a redesigned form
Open Performance → Forms [new]. The Forms page lists each form’s name, question count, creator, creation date and status.

Use name, creator, publication and read-only filters to locate a form. Read only filters campaign usage; it does not change editing permissions.
Search and inspect forms
- Open Performance → Forms [new].
- Enter a name or creator criterion, and use publication or read-only filters when needed.
- Review the matching form’s identity and status. Clear the relevant filters to broaden the list.
The controls below refine the displayed list; they do not edit a form.
| Control | Choices / initial state / clearing | Result and practical use |
|---|---|---|
| Search by name | Text; blank initially. Clear to remove. | Search for a distinctive part of the form title. |
| Created by | Text; blank initially. Clear to remove. | Use the creator information available to you to narrow the list. |
| All forms | Single selection: All forms, Draft, Published. Initially all. | Restricts publication status. Select All forms to clear. |
| Read only | Unrestricted, yes or no through the shared boolean filter. Initially unrestricted. | Narrows by campaign usage. It does not change permissions, publish a form or lock it manually. |
| Name / Created at | Sortable fields when available. | Sort the matching forms; this does not change their content. |
| Pagination | Page numbers and Previous/Next. | Use the page controls to browse additional results. |
| Row selection / status menu / create | Conditional controls. | Actions can change form data; check the form's usage and rights before using them. See configuration for safe setup. |
Search criteria are temporary; publication, copying and saving are persistent actions.
Understand the form before assigning it
- Read the selected form’s sections, question wording, required fields and intended audience.
- Check the questionnaire’s content language separately from the interface language.
- Review any generated content before saving or publishing, then follow the campaign’s assignment procedure.
The nextgen editor lets an administrator add sections and typed questions, set their audience and required status, and review the form overview. The form's content language is independent of the interface language. Save the form before adding translations; review every title, instruction, evaluator wording and choice in each locale. Preview the language variants before publishing. Publication makes the form selectable; it does not assign employees or start a campaign.
Generated text needs review before saving or publication. Setup details are in configuration.
Answer a questionnaire in your interview
Employees open their assigned interview, rather than this library. The Interviews guide illustrates that entry point. Their form may differ from the evaluator's because audience and workflow settings apply.
- Read the section instructions and answer the controls shown for your contribution.
- Use the available section navigation to review the whole form.
- Correct missing or invalid answers before finishing preparation.
- Follow the campaign's interview/signature steps; answering a question does not sign the interview.
Question families and options
Available question types depend on the form generation and its configuration. A form may use only a subset of these families.
| Question family | What the participant does | Important option or dependency |
|---|---|---|
| Message / section | Reads explanatory content and navigates groups. | Legacy messages/section headings do not themselves store an answer. |
| Text | Enters a short or longer response. | Nextgen supports configured length and text rules; legacy simple/open questions are different types. No universal text limit is assumed. |
| Single / multiple choice | Selects one or several configured answers. | The form sets choices and permitted counts. An empty answer is not automatically a valid “not applicable”. |
| Rating / scale | Selects a value within the configured range. | Scale labels, bounds and display depend on the form; do not transfer legacy rating conventions to nextgen. |
| Numeric / date | Enters the requested value. | Nextgen schema includes these families; date bounds can be configured. |
| List / referential | Selects from a configured source. | Nextgen options can come from company referentials; language/data availability affects choices. |
| Skills | Assesses configured skills. | Skill selection, levels and permission to add skills depend on form setup. |
| Past / future objectives | Reviews previous goals or defines future ones. | Periods and campaign setup matter. Legacy goal data is not just a text answer. |
| Development | Contributes to development/training content. | Available catalog, opinion choices and specialist settings apply. This is not automatic course enrollment. |
A completed form and a shared form are different. The availability of another participant's answers must be determined from the current interview, not from the fact that both participants see the same question title.
Legacy versus redesign
Legacy questionnaires and redesigned forms use separate catalogs and question models. The two catalogs coexist; seeing both menu items does not mean that forms share saved content, convert automatically or have the same permissions. People Review features, such as its collective matrix, are not automatically available in an interview form.
FAQ and troubleshooting
| Issue | Check |
|---|---|
| Form missing from a campaign picker | Check the form generation, publication status, your access and the language available to the campaign. |
| Form is read only | In nextgen, running, done and archived campaign use counts; draft/not-started use does not. Duplicate for a new version when appropriate. |
| Same question appears differently for the evaluator | Audience, evaluator-specific wording and answer-sharing settings. |
| Labels remain French in an English interface | Authored content and its translations are separate from UI language. |
| Required answer rejected | Expected type, selected count, bounds and configured validation rules. Ask the administrator if instructions conflict. |
Implementation differences
Legacy questionnaires and redesigned forms use different catalogs and question models. See the technical guide for implementation details. Available actions depend on the form, campaign and your permissions.
Dernière mise à jour : 3 novembre 2026