Mini Intake: English Exams - Registration process changes

[sadatmalik]

See: https://www.canva.com/design/DAFtz28cQHE/JZI_5copovFN8N1fE2lQYg/view

Review and implement registration screen changes for English Exams from the relevant slides.

To clarify, it will only make sense to do this for all languages, not just english exams.

[sadatmalik]

Discussed this with John - and agreed to proceed with this change.

[cazcam34]

[EhsanEhrari]

@cazcam34 , I need some clarification on this. Does this mean we should move it to the candidate account registration form? If so, in which step of the registration process should I add it?

[EhsanEhrari]

To move the entire exams section from the mini intake form to the registration form for the candidate: What should we do? Design Consistency:

• The design for the exams section in the registration form is identical to the one in the mini intake form.

• A button is provided to allow users to add additional exams if they wish.

Frontend Changes:

• Implemented a new component RegistrationCandidateExamComponent for handling exams in the registration form.
• Form includes fields for exam type, score, year, and notes.
• Adding functionality to dynamically add and delete exams.

Backend Changes:

• New API endpoints are required to handle the creation and management of candidate exams.
• When a candidate is created, their exams will also be created and stored in the candidate_exams table.

The exams section will successfully move from the mini intake form to the registration form with the same design and functionality to manage multiple exams.

[EhsanEhrari]

@camerojo Please have a look on my comment on the PR.

[EhsanEhrari]

On the candidate registration page, we have two approaches for registration:

• Update the Entire Records at Once: This approach updates all records (e.g., 5 exams) at once. This method, which I implemented and copied from the occupation section, requires sending the complete set of records in a single update.

• Update One Record at a Time: This approach finds the specific record (e.g., one exam) and updates only that record. This method is easier and more straightforward.

As per my discussion with John, we need to transition from the old approach (updating the entire records at once) to the new one (updating one record at a time) and have only one model instead of two.

[EhsanEhrari]

Candidates can review and edit the exams after profile completion!

[EhsanEhrari]

CandidateExamPortalApi provides endpoints for managing candidate exams in the portal API. It implements the IJoinedTableApi interface to ensure standardization and consistency for operations on candidate exams.

This API includes methods for:

• [x] Creating a new candidate exam record (create method of IJoinedTableApi )
• [x] Updating an existing candidate exam record (update method of IJoinedTableApi )
• [x] Deleting a candidate exam record (delete method of IJoinedTableApi )

This implementation focuses on managing a single candidate exam record at a time, adhering to the standardization provided by the IJoinedTableApi interface.