[NEEDS WORK] Scholarship/Bursaries Program year limit

[Joshua-Lakusta]

Similar to Books & Supplies #3017 and Program Year Limits #3387

Description The system does not apply the PY business rule for Scholarship/Bursaries in the assessment and does not check between different applications. The allotted exemption limit for a program year is $1800. After that point any additional amount is included in the contribution calculation. With the current function the workflow does not account for the of the exemption limit and is also not checking prior applications in the same program year. This will lead to incorrect assessments.

Story

• Student applies for funding September to December PY 2024-2025

• Student reports $1500 of merit based scholarship through SIMS application

• The $1500 is completely exempt as it is less then the $1800 PY limit. So it would not have any impact on their application from this scholarship amount for this application

• Student then applies for funding January to April PY 2024-2025 (same PY)

• Student reports another $1500 of merit based scholarship through SIMS application

• The PY limit for all applications is $1800 and they have not reported a total amount of $3000

• The additional $1200 (3000-1800=1200) needs to be included as a part of the calculation of calculatedDataScholarshipsBursaries (Which is further a part of Calculateddatatotaltargetdresources)

SIMS question source Private Zenhub Image

Actual Behaviour Currently just references the studentDataScholarshipAmount and adds it directly into the calculation. It does not apply the exemption rule or check prior applications to properly asses that same rule.

Expected Behaviour Needs to be workshopped as I do not know the full solution

Additional Concerns

• How do we reference when there is an app submitted and they are submitting another future app but have not received any money. (would they be able to sneak it through SIMS (compared to SFAS where apps once submitted are locked in)
• Change request after the fact. How would the check function

[Joshua-Lakusta]

@HRAGANBC can you review this one and add any additional context you feel is needed before we take it to Devs to start brainstorming a solution.