Interviews — legacy technical guide

Legacy request and data flow

DefaultController::indexAction and showAction declare the module_interview_view school permission. tableAction initializes manager/search/preparation/signature/meeting criteria and calls the interview repository filtering flow. interview_all expands the checked table context; a missing permission object also has special handling. This is not a full authorization audit of every legacy endpoint.

newAction constructs and persists an Interview immediately, names it according to the existing count and redirects to parameters. It is a mutating creation link: do not invoke it for read-only automated inspection. saveAssessmentAction, AssessmentDoneAction, InterviewSignAction and unlock actions are separate answer/lifecycle operations.

Legacy persistence separates campaign Interview, participant InterviewUser, questionnaire Assessment, participant assessment AssessmentUser and question/answer records. The Confluence data-model document additionally explains why employee and evaluator answer contexts must not be joined merely by employee user ID. Choice answers and specialist skills/objectives/training content require their respective structures; a scalar answer export is insufficient.