Forms — legacy technical guide

Legacy responsibilities and model

In smartmobility-legacy:

• src/Company/AssessmentBundle/Controller/DefaultController.php: newAction, indexAction, listAction, getQuestionTypeAction, updateAction, findAllFilteredAction, question retrieval and access updates.
• src/Company/AssessmentBundle/Controller/AssessmentQuestionController.php: question authoring operations.
• src/Company/AssessmentBundle/Resources/views/Default/{list,assessmentForm,assessmentQuestions,question_type}.html.twig: library, form and question screens.
• src/Company/InterviewBundle/Controller/DefaultController.php: selecting and consuming a questionnaire in an interview campaign, saving responses and lifecycle operations.

Legacy Assessment represents a reusable questionnaire; AssessmentQuestion defines a type, order and content, and AssessmentQuestionItem stores options. AssessmentAnswer and item-answer structures represent contributions. InterviewUser and AssessmentUser supply participant contexts. Specialist goals, skills and training content should not be flattened as if every question stored one text value.

The legacy type picker includes 1to1, interview, peopleReview, 360, mobility and test/questionnaire types. 1to1 and interview are distinct codes. Do not route a campaign by translating the label “review” without checking its module/type.