Add effective-date row for CALS
Academic Applications Bug
Summary of problem
In OLD SAM, CALS (and EDU) has additional logic which caused the program to send a change even if the program stayed the same. This was done in order to set the term with the DARS catalog. Note, Education has not reported any issues with the DARS catalog years, so at this point, this bug is no longer impacting EDU, only CALS.
The request from the RO is: apply modified logic to CALS students to align with policy on requirement years in DARS. From the long email string with the title of "Old SAM Modification for CALS & EDU" it appears that business logic was added so Effective Date and Declare Date were being sent by SAM to SIS.
Effective Date and Declare Date should be the first day of the fall term during summer SOAR. (as per Beth Warner's answers in 10/29/2018 email)
Effective Date and Declare Date should be the first day of the spring term during JSOAR. (as per Beth Warner's answers in 10/29/2018 email)
Logic lives with part of the export (from notes from 2022)
Eric may be a resource when evaluating how to solve this issue.
3/18 Update from Eric:
It was unclear from the previous email thread if a 2018 change to the SAM logic had actually been implemented, so I completed some old-SAM vs. new-SAM testing and documented the results here: https://docs.google.com/document/d/1L-H1uCpeQE1PqntvNS7UYseGYMmii0HixvjIUywJEi8/edit#heading=h.9a3oy4ceuhi0
The results indicate that there is definitely a difference in old-SAM vs. new-SAM behavior when it comes to setting the Declare Date and Effective Date for new rows that have the same Program/Plan as the old rows (i.e. student keeps the same major that they came into SOAR with). I bolded the text in the description above re: Effective Date and Declare Date changes that should be implemented, because I confirmed that is the correct logic.