Parent update first effort
User Story
As a ministry or student user i need to update the workflow processes to accommodate the use of the supporting user form for self declaration and for mixed declaration types. This is important to better assist students in completeing their applications accuratly
Acceptance Criteria
Baseline information
- [ ] Changes to the 25-26 program year and onward
- [ ] Changes to the FT application only
Modify application
- [ ] Replace the current parent questions with a function similar to the dependants sections
- [ ] Student will default have one box for adding a parent and they can not remove this field
- [ ] They can add an additional parent to a maximum of 2
- [ ] Student should be able to remove the second parent by clicking "X"
- [ ] Include the current BCSC question to determine declaration eligibility
- [ ] Make sure there is validation in the app that would ensure the two full names are not the same
- [ ] Modify the content for the BCSC question to remove the plural option for parent(s) it should just be singular
Mock up

Students can complete one or both parent declarations using this method.
Variable handling and names
- [ ] Stop relying on the variable:
studentDataParentValidSinNumber
Workflow
assessment-gateway
- [ ] Modify the assessment-gateway to allow the processing of one to two provided parents, which will always create a supporting user on SIMS to allow the data collection later, either from the students or using the supporting users' portal.
- [ ] Adapt the below assessment-gateway tasks to process the new parent collection
- [ ] create-identifiable-supporting-user
- [ ] retrieve-supporting-info-for-parent
- [ ] parent-income-verification
- [ ] Create a new version of the assessment gateway to be used from the program year 2025-26 onward. Suggested name
assessment-gateway-v2since it does not need to be associated with a program year.
Suggested new flow
Worker changes
- [ ] Create a new worker to allow the processing of the new supporting user creation, suggested name
create-identifiable-supporting-user. - [ ] The new worker can process one or two parents creation in parallel and should be prepared to process a partner once the partner is converted to use the same flow.
- [ ] Keep the individual parent's creation idempotent using the full name as an identifier to distinguish it in the scope of the same assessment.
load-assessment-consolidated-data
- [ ] Reuse the existing workflow, unless there is a strong reason to create a secondary version.
- [ ] Adapt the current
load-assessment-consolidated-datato load the new parents array.- [ ] Create a new mapping
studentDataParentsfrom$.data.parents.
- [ ] Create a new mapping
income-verification changes
- [ ] Adjust the
income-verificationto skip the CRA income check if the supporting user does not have a SIN associated, for instance, if the information was provided by the student or, in the future, if the supporting user provided the data but chose not to provide a SIN. - [ ] Suggested new flow.
- [ ] Adapt the existing worker
cra-integration-income-verification. The worker can be adjusted in a backward-compatible way to return the new variable likecanExecuteIncomeVerification.
Full-time assessment
- [ ] The below area must be removed, assuming the data will always exist in the supporting user dynamic provided column.
- [ ] Adapt the flow as below to allow the workflow to be processed using only data provided from supporting users, either provided by the student on behalf of the parent or by the parents themselves.
Income verification Scheduler
- [ ] CRA income should never select a record associated with a supporting user where there is no SIN present.
Missing items for future work. Can add additional sub status for parents to show how they were declared student or by parent Update to current parent tracker to display given names outstanding Parent email to students update How to ID the supporting user (given name makes most sense) Partner? Supporting user portal search updates Edit function enhance to be an edit with update questions around resubmitting this data.
Tracker Card Access
-
[ ] A new self declare tracker card appears in the standard tracker card section for students required to self declare parent financial information.
-
[ ] Tracker card includes one "Self Declare" button per parent who requires self declaration.
Unique Parent Buttons TBD based on app questions
Each "Self Declare" button is clearly labeled with the name or identifier of the parent it refers to.