Problem: 

When Regent Award was set up for multiple Reporting School and Attended School COD Source IDs under the same COD Source Entity ID and a COD Export was run, records were duplicated when the process staged the data for the COD Export, which caused the process to fail (timeout) and no file was created.

Cause:

The system did not have logic to handle the scenario for multiple Reporting School or Attended School Entity ID values under the same COD Source Entity ID.

Fix:

The COD Export has improved logic for linking records to the correct COD Attended School code and the correct COD Reporting School codes to prevent the duplicate records from staging and the process from failing.

Testing:

In a Regent Award test environment with an Institutions that has more than one Reporting School or Attended School ID under the same COD Source Entity ID, run the COD Export process. Confirm the COD Export is successfully created and students from each of the Campuses/Sites were selected for export. Review the data in the data file. Confirm the exported data has no duplicated records for the combination of each unique (COD Source Entity ID {in the DocumentID} + Source Type + Reporting School Routing ID + Attended School Routing ID).

Problem:

Some COA items are not showing horizontal totals in MyBorrowing, MyPlan, and What if I Change My Course Enrollment areas.

Cause:

RNA output Cost Name for one field and Cost Display Name for another, making it so that Payment Period and Academic Year level amounts could not be mapped to Student Experience.

Fix:

Updated the code to be consistent between the Cost Display Name and Cost Name.

Testing:

Access Student Experience and make sure that horizontal totals for COA components within My Borrowing, My Plan, and What if I Change My Course Enrollment Areas display correctly.

Problem:

When the ‘Award Full Eligibility in Final AY Only’ option was selected, some Unsubsidized Loans were not being packaged to the expected amounts when the Subsidized Loan eligibility was limited by the student’s Lifetime Aggregate amounts.

Cause:

The Unsubsidized Loan Maximum Amount was being determined using the annual Subsidized Loan Limit instead of the reduced amount of the student’s remaining Subsidized Loan lifetime aggregate eligibility.

Fix:

The Unsubsidized Loan amount calculations use the student’s actual Subsidized Loan amounts that are awarded instead of the annual limit for Subsidized loans.

Testing:

Ensure the Subsidized and Unsubsidized loans are configured in Fund Setup with the setting enabled for ‘Award Full Eligibility in Final AY Only.’ Package a student who is in their final Academic Year, and is near the Subsidized loan aggregate lifetime limits. Confirm the Subsidized loan amount matches the student’s remaining lifetime aggregate Subsidized loan eligibility. Confirm the Unsubsidized loan amounts are awarded to the full eligibility for the Academic Year.

Problem:

Regent Award was unexpectedly populating the Middle Initial field with the full student's middle name in Smart Form applications causing a validation error and students were unable to enter anything in that field and complete the page.

Cause:

Student "Middle Initial" field maximum allowed length was configured as 1. Therefore, when the student’s middle name is not a single character in Regent Award, the questionnaire prepopulation failed.

Fix:

Regent Award updated the prepopulation logic to only prepopulate the first characters of the student's middle name.

Testing:

Identify an affected student. Click on the ‘Start, Edit or Complete’ link for the Smart Form document in the Document Component of the Student Experience portal. Complete the Personal Information section and click ‘Next’. Ensure that no error is received and the student is able to successfully go to the next page.

Problem:

In the 2021-2022 College Financing Plan (CFP) Communication PDF attachment, the 'EFC Based on FAFSA' field unexpectedly displayed a blank value.

Cause:

The ‘Primary Alternate Month EFC’ value was using a non-numeric (string) format when the value was received by the Communication.

Fix:

The Primary Alternate Month EFC has been converted to a numeric (integer) format.

Testing:

Copy the updated HTML to the Communication Templates for Undergraduate and Graduate College Financing Plan PDF attachments. Reload RNA setup. Generate an Undergraduate communication using two Undergraduate students with 2021-2022 ISIRs, where one student has a zero EFC value and another student has a nonzero EFC value. Confirm the ‘EFC Based on FAFSA’ fields have the correct values on each Undergraduate communication. Repeat for two Graduate students. Confirm the ‘EFC Based on FAFSA’ fields have the correct values on each Graduate communication.

Problem:

Internal transfer units were ignored by the system, resulting in incorrect grade level progression displayed on the Academic Plan.

Cause:

Regent award did not take into account a program change scenario where the last Academic Year of the previous program was a non-BBAY Academic Year.

Fix:

Logic was added to detect whether the new initialized enrollment refers to a different course enrollment program so the system properly takes into account internal transfer units when calculating grade level progression for the new program.

Testing:

Open the affected student. Load SBL with a program change including internal transfer units that correspond to the number of units required to achieve the next grade level. Complete program change. Run packaging. Verify the expected grade level is correct.

Problem: Pell incorrectly packaged over LEU limit by $1 dollar.

Cause: The application incorrectly rounded Pell amount to the nearest dollar value when the amount was adjusted by LEU.

Fix:
The application will truncate Pell amount when the it's adjusted by LEU.

Testing:
Find Pell eligible student example which is close to LEU limit. Run packaging. Make sure that the adjusted Pell LEU amount is truncated to the nearest cent but not rounded up when close to the limit.

Problem:
Regent Award was unexpectedly providing wrong award data to COD, causing a higher than normal volume of 117 COD rejects.

Cause:
Regent Award was incorrectly marking an award for cancel and recreate and blocking the award from going through the cancel and recreate process. Since the award was blocked from the cancel and recreate process, the FAID update flag was not cleared causing the FAID number change.

Fix:
Regent Award was updated to clear FAID update required flag from awards when blocked from the cancel and recreate process. An isValidForSaving check to AwardCODMetadata flag was added to prevent the changing of the FAID if the award is not in ‘Estimated’ status, if the award has COD records (e.g. Acceptance), or if Actual EST has been run for the award.

Testing:
In Regent Award package a student to confirm that an award number will not increase. Send a generated file to COD.

Problem:
Loans were zeroed out after the census date.

Cause:
Regent Award did not take into account census enrollment level type when calculating loan eligibility.

Fix:
System checks were updated to consider census enrollment level type when determining loan eligibility.

Testing:
Find the affected student. Confirm that student is enrolled through census date at least HT. Run packaging. Make sure that loans remain packaged based on student's enrollment level.

Problem:
R2T4 amount was $1 less than expected.

Cause:
Regent Award incorrectly rounded the amount calculated in R2T4 Step 5/6 down to the nearest 0.50 instead of rounding up to the nearest dollar.

Fix:
Regent Award will correctly round the amount calculated in Step 5/6.

Testing:
In Regent Award, complete R2T4 with a return amount. Then review amount returned by the system during the next EST transaction.

Problem:
The packaging was blocked by BBAY Modification for Academic Year has an invalid FAY assigned to it error.

Cause:
Regent was not properly setting the Academic Year Dates based on a BBAY Modifications when the Academic Plan had multiple AY0s. Some Academic Years received invalid dates (e.g. StartDate after the EndDate).

Fix:
The Regent Award logic was updated to handle multiple AY0s when managing BBAY modifications.

Testing:
Find an affected student(s). Run packaging. Confirm that no errors occur in the MAP wizard.

Problem:
On a student’s COD tab, Regent Award was unexpectedly showing a 'Data is Null' error and no data were present.

Cause:
Some Awards data contained empty date fields for Start and End dates. The unexpected data caused an error on the screen when loading and displaying the data in the grids.

Fix:
Regent Award updates were applied to data loading and displaying for the COD screen to support nullable date values.

Testing:
In Regent Award, navigate to the COD Tab for an affected student. Confirm the screen displays the awards. Confirm the screen does not display the ‘Data is Null’ error.

Problem:
Regent Award was unexpectedly awarding Wisconsin grand based on the 2-term tuition amount if the 1st term in 3-term program is not eligible because there are not enough units for the award.

Cause:
Regent Award eligibility ruleset required that a value from the lookup could be returned and was above $0. The lookup failed when the enrollment level was halftime but the units were below the lookup minimum value.

Fix:
Regent Award was updated to ensure that the WI eligibility ruleset does not set eligibility to false when the enrollment level is HT or higher but the registered units for the given cost group Id is below the minimum units for the lookup table.

Testing:
In Regent Award package an affected student and confirm the Wisconsin grant amount is correct for each term.

Problem:
Regent Award was incorrectly prorating Pell using Formula 4 for the remaining program units, NOT the remaining registered units.

Cause:
Regent Award was incorrectly prorating Pell using the anticipated program units in Formula 4.

Fix:
Regent Award was updated to ensure logic to use the greater of the anticipated or registered units.

Testing:
In Regent Award package the affected student(s) and confirm the Pell award amount.

Problem:
SAP status was not inherited when the student had a program change at the same level (Undergraduate to Undergraduate) and Use Prior Program SAP Status When Program Is Changed At Same Level setting was set to 'Yes'.

Cause:
A previous SAP status of 'MTF/FA Suspended' was not considered as a previous SAP status by system that caused incorrect SAP status change in subsequent term.

Fix:
Updated logic so that 'MTF/FA Suspended' previous status is inherited correctly when Use Prior Program SAP Status When Program Is Changed At Same Level setting is set to 'Yes'.

Testing:
Make sure that Use Prior Program SAP Status When Program Is Changed At Same Level setting is set to 'Yes'. Find the affected student. Complete program change at the same level (grad-to-grad or undergrad-to-undergrad). Run SAP. Review SAP status at current term. It should be inherited from the last term of previous program.

Problem:
In the Return to Title IV (R2T4) Wizard, Step 6, the ‘Step 10 Grant Amount to Return’ was not included as a component of Total Amounts to Return.

Cause:
The ‘Step 10 Grant Amount to Return’ was not factored into the Step 6 'Total Amounts to Return.'

Fix:
The code fix was applied so that ‘Step 10 Total Grant to Return’ was added into the Step 6 ‘Total Amount to Return.’ The field ‘Total Amount to Return’ was made to display the correct read-only value.

Testing:
Navigate to an affected student who has Title IV Grants. In an open Payment Period, add an R2T4 resulting in a Step 10 Grant Amount to Return. Validate that the Step 10 amount is added into the Step 6 amount. Finalize the R2T4. Package the student. Confirm the system updates the awards to the correct recalculated amounts.

Problem:
Regent Award was unexpectedly not moving a loan to a shorter, one-term loan period after loan cancellation in the MAW wizard.

Cause:
The Loan Period Truncation logic for $0 periods was incorrectly being applied to SAY Calendar Types only.

Fix:
Loan period truncation logic was updated to include checks for other calendar types. The term will not be included in the loan period dates if :

• 100% of loan funds are zeroed out on a term
• A student has a term in a Loan Period that has attendance but does not have any Loan Disbursement, or the term's loan disbursement is now $0

Testing:
Find an affected student. Open MAW. Shorten the Loan Period by updating the last term’s disbursement to $0 in MAW for either a Subsidized or Unsubsidized loan. Complete the steps in MAW. Verify the loan period dates match the term dates and do not include the last term.

Problem:
In the Return to Title IV (R2T4) Wizard, for Step 1 values, the ‘Recalculated Pell Amount’ and ‘Pell Amount to Return’ were not updating when a user applied Override amounts.

Cause:
The system used the eligible amount from the normal Pell ruleset when there were manual values.

Fix:
A code fix was applied so that the system calculates the Pell amount as a sum of the Pell override amounts when a user enters those values manually.

Testing:
Find a student who has a paid Pell Grant. Add an R2T4. Manually override the Step1 Pell Grant Amounts for ‘Amount Disbursed,’ ‘Net Inadvertent Overpayments,’ and ‘Amount that Could Have Been Disbursed.’ Confirm that these overridden Pell Grant Amounts are components in the Recalculated Pell amount. Confirm that the ‘Pell to Return’ amount is the difference between the ‘Paid Pell’ and ‘Recalculated Pell Amount’ fields if the Paid Pell is greater than the Recalculated Pell Amount, or otherwise results in zero.

Problem:
Cancelled loans were showing calculated eligibility with an amount greater than zero.

Cause:
Cancelled-and-recreated loan disbursements were maintaining an eligible amount, causing display issues.

Fix:
The processing order was updated in the packaging logic to first calculate and add all eligibility onto eligible awards. Cancelled-and-recreated loans are calculated with zero eligibility.

Testing:
Find the affected student(s). Run packaging. Ensure all eligibility amounts are correct. Canceled loans should have $0 eligibility.

Problem:
Regent Award incorrectly sent the Pell COA amount in the COD Export, ignoring the priority of Pell COA amounts configured at the setup.

Cause:
Regent Award was incorrectly sending the program Pell COA amounts in the COD Export.

Fix:
The system logic was adjusted to use the Pell COA setup and Pell COA override values to populate the Pell COA in the COD Export.

Testing:
Set the Pell COA Override to be $1. Set the Pell COA Setup to be $2. Set the Pell COA in Program Setup to be $3. Run packaging. Originate Pell at COD. Confirm the <AttendanceCost> tag in the COD Export file is $1.

Problem:
YRP Pell disbursements were canceled, despite the award amounts remained accurate on the Academic Plan screen.

Cause:
Regent Award set incorrect status and amounts for YRP disbursements when disbursement schedules were generated.

Fix:
The code was updated to set the correct status and disbursement amounts for YRP Pell.

Testing:
Find the affected student(s) with Regular Pell paid at 100%. Run packaging. Review YRP disbursements: award and disbursement amounts should be the same.

Problem:
Multiple Sub and Unsub loans disbursements were generated.

Cause:
When there was only one enrollment in an Academic Year in a ‘Closed’ status with an ‘Autowithdraw’ close reason, a context was sent to the packaging engine without the awarding calculation option, thereby causing a validation error.

Fix:
Packaging logic was updated to allow a non-BBAY Academic Year to fully process when a term in the Academic Year is duplicated by a term in another Academic Year. Prioritization to use Actual units over Anticipated units was added in the event of duplicate enrollment to ensure proper CE matching logic.

Testing:
Find the affected student. Close all tasks and blocking documents. Run packaging. No errors should occur and no duplicate awards created. Run EST-for-DRI. No override errors should occur.

Problem:
Regent Award was not calculating Total Loans amounts on Recommended Borrowing/Maximum Borrowing Details, Students Loans.

Cause:
The Estimated Amount was being used instead of Offered Amount when calculating My Borrowing info totals (estimated and non-estimated totals) when the award was not in an Estimated status.

Fix:
Regent Award was updated to ensure that Offered amount will be used for all My Borrowing info totals when an award does not have a status of Estimated, even for the estimated totals.

Testing:
In Regent Award Student Experience portal, navigate to the Financial Aid tab. On the Recommended Borrowing/Maximum Borrowing details, check the Total Loans amount.

Problem:
In Regent Plan in the Student Experience Portal, the ‘Borrowing Option Detail’ was not displaying the correct Cost of Attendance (COA) subtotals.

Cause:
The logic for the Academic Plan Cost Items was not consistent across all locations in the Student Experience Portal code.

Fix:
Regent updated the code so that the logic used for Cost Item is consistent throughout the Student Experience Portal.

Testing:
Test in an environment that has Regent Plan. Log in to Student Experience or view the Advisor Assist tab for a student who needs to Select a Borrowing Plan. In My Plan, click Select My Borrowing Option. In My Borrowing, confirm the displayed totals are correct for the ‘Costs and Awards’ in the Borrowing Plan Options sections. View a student who has already selected a Plan. In ‘My Plan,’ expand an Academic Year and view the details. Confirm the Estimated Cost amounts and totals are correct.

Problem:
Incorrect FAY assignment took place on the Academic Year that caused fund awarding to fall into a different Federal Award Year.

Cause:
Regent Award failed to perform a Federal Award Year change on the Academic Year. When the new awards were added, they were incorrectly moved into the default Loan Period having different Federal Award Year.

Fix:
The code was updated so that when no paid loans exist on the default Loan Period, the Federal Award Year of the Loan Period will be re-evaluated.

Testing:
Find the affected student. Run packaging. Confirm that existing awards are not flipping into different Federal Award Years.

Problem:
Regent Award was unexpectedly overawarding Parent Plus loan in the 2nd term with the amount that is needed in the 1st term.

Cause:
Regent Award application incorrectly distributed the Direct Parent Plus amount evenly according to Fund Setup. Although the total amount was not overawarded for the loan period, this caused overawarding in some payment periods.

Fix:
The Regent Award application was updated to ensure that the distributed Direct Parent Plus amount is based on the remaining payment period unmet cost.

Testing:
In Regent Award, package an affected student and confirm the Parent Plus amount.

Problem:
On the Awards tab, Regent Award did not appear to include resources in the Unmet Need and Unmet Cost calculations and total amounts.

Cause:
The displayed COA values were already adjusted for the Resource amounts. Since Resources are shown separately on the screen, it also appeared that the amounts did not sum up correctly.

Fix:
Regent Award was updated to account for the Resource amounts in the Unmet Need and Unmet Cost calculations.

Testing:
In Regent Award, test with a student who already has a Resource or add a new Resource to a student manually using the ‘Add/Adjust Resources’ wizard. Package the student. Refresh the Awards tab. On the Awards tab, select a loan period from the ‘Analyze Loan Period’ drop-down. Confirm the Unmet Need and Unmet Cost items are correct. Refresh the Awards tab. Select the individual payment periods that make up the same Loan Period as used for testing the drop-down menu. Confirm the Unmet Need and Unmet Cost items add up to the loan period totals. Confirm the amounts are correct.

Problem:
Regent was unexpectedly canceling and re-creating loans for the next Academic Year.

Cause:
Regent Award was not determining the priority of ISIRs in a crossover period correctly. ISIRs that were ‘Not Selected for Verification’ and ISIRs that were ‘Selected for Verification - Not Verified’ were being treated with the same priority, resulting in a latter year ISIR taking precedence after it has already been verified.

Fix:
The logic for determining the priority of ISIRs was updated.

Testing:
Find the affected student. Load 20-21 and 21-22 ISIRs and make them active. Make sure that 21-22 ISIR is selected for verification. Run packaging. Loans should not be canceled and re-created. Ensure the FAY for the loan is not updated.

Problem:
20-21 SEOG Fund budget totals were displaying incorrect values.

Cause:
The Fund Budget logic incorrectly handled budget balances for Accepted, Paid, and Offered amounts.

Fix:
The Fund Budget logic was updated to maintain Paid Amounts for the budget amounts until a negative transaction is completed before reducing the budget amount. Code was also added to clean up existing budget fields on awards for funds having no budgets.

Testing:
Run the "RS-20011" script. Run packaging. Review fund budget setup for the affected fund. Accepted and Offered amounts should be equal and Paid amounts should not be higher than the Offered and Accepted amounts.

Problem:
In a term with an R2T4, Regent Award incorrectly counted courses that were withdrawn on the same day as the R2T4 WDD and before the Census date, causing an incorrect Recalculated Pell amount for the R2T4 calculation.

Cause:
The Year-Round Pell (YRP) recalculation had an incorrect lookup value for the enrollment level. The logic was incorrectly adjusting for Pell amounts counting toward the student’s Pell Lifetime Eligibility Usage (LEU). When the Recalculated Pell Amount was greater than the amount considered for the LEU total, the system calculated the incorrect amount for the Payment Period.

Fix:
Regent Award uses the correct enrollment level for the R2T4 recalculated Pell amount. The logic was corrected for adjusting for a Pell amount that is already included in the student’s total Pell LEU.

Testing:
Test with an affected student who has a relatively high Pell-eligible EFC that would result in a $0 Half-Time Pell amount, but who has Full-Time (FT) enrollment and FT Pell award for the term. Package the student. Update the course data to have half-time attendance in the term prior to the census date, with the attended courses withdrawn on the same date prior to the term’s census date. Create an R2T4 with the R2T4 WDD matching the course withdrawal date. View the Recalculated Pell Amount. Confirm the recalculated Pell amount is $0. Finalize the R2T4. Package the student. Confirm the Pell amount is adjusted to $0.

Problem:
Regent Award was unexpectedly showing no information for some loans with COD history on the Loans tab, COD subtab.

Cause:
Some Awards data contained unexpected nullable date fields for Start and End dates. The unexpected data caused an error on the screen when loading and displaying data in the grids.

Fix:
Regent Award updates were applied to data loading and displaying for the COD sub-tab on the Loans screen to support nullable date values.

Testing:
In Regent Award, navigate to an affected student’s Loans Tab, then to the COD sub-tab on that screen. Confirm the screen displays the awards. Confirm the screen does not display the ‘Data is Null’ error.

Problem:
The 'R2T4CompletedOnDate' was showing as blank in the data view table for students who have finalized R2T4 with an R2t4ResultCode of 'REFUND' or 'PWD'.

Cause:
Automated R2T4 logic failed to set the correct 'R2T4CompletedOnDate' value.

Fix:
Code checks were added to ensure that dates are set appropriately when an R2T4 status is Finalized or No Action Required.

Testing:
Open the dataExtract_R2T4_View_v001 table. The data view table should not contain empty values for students who have a Finalized R2T4 in the R2T4CompletedOnDate column.

Problem:
A student had a packaging error, “Failed to Process: Student’s Academic Year #0 is set by BBAY Modification but has no enrollments.”

Cause:
When the system tried to package the student, the logic had assigned the same Manual Academic Year identifier value (SBM ID) to more than one Manual Academic Year.

Fix:
Regent Award was updated to detect an invalid assignment of the SBM ID value to the Academic Year. The system clears the assignment before reconciliation occurs.

Testing:
Find the affected student. In Regent Award, use the Program Management Wizard to view the student’s Academic Year structure. Package the student. Confirm the student is packaged without error.

Problem: Documents with special characters in the file name could not be uploaded into Regent Award and the Error message was not clear.

Cause: The web server did not allow for certain special characters in the file name for uploaded documents.

Fix: The code was updated to show a user-friendly validation message when the file name contains special characters that aren’t allowed: “There is an unsupported character sequence in the file name (e.g. '). Please remove the special characters from the file name and try again.”

Testing:

From the Documents tab in Regent Award, select ‘Add Document’. Upload a file with special characters in the name. Verify the validation message is displayed.

Purpose of Script:
This build script ensures Regent Award is using updated course data for all students upon upgrade. In some cases, resource conflicts at the database level might have caused deadlocks and stopped the Course Enrollment Rollup (CE Rollup) process from completing. Some students might have had pending data changes, such as new course information from the Student Batch Load (SBL) process. For the affected students, the system could not update information such as total unit values.

Data Changed by the Script:
The script identifies any students that have course data changes or other SIS-provided data that was loaded but was not yet fully processed. The script then runs the Course Enrollment Rollup (CE Rollup) process for those students. The CE Rollup process updates the unit totals and other information.

How to Access the Script:
The script is included in the deployment of the 5.8.0.0 release. Each customer will receive this script update automatically when they upgrade to the 5.8.0.0 release.

How to Test the Script:
Before upgrading, find an affected student who had SBL data loaded in a failed CE Rollup process, where the student’s current course data do not match the unit totals displayed on the Academic Plan screen. Perform the upgrade. Refresh the Process Log. Confirm the Process CE Rollup process is Complete. View the affected student. Repackage the student using the Modify Academic Plan wizard (MAP). Refresh the Academic Plan screen. Confirm the total units match the course data.

Title: Data View Updates per 5.8 Release

Tickets: RS-23127;

Description:

The following Data Views were created for new tables:

• dataExtract_AcademicYearPackagingPhilosophyHistory_View_v001
• dataExtract_InstitutionPortal_SPProgressForDisbursementsSettings_Config_View_v001
• dataExtract_ProgramType_Config_View_v001

The following Data Views were created per changes to tables:

• dataExtract_AcademicPlan_View_v004
• dataExtract_Award_View_v005
• dataExtract_AwardCODMetadata_View_v004
• dataExtract_CODAward_View_v006
• dataExtract_CODDisbursement_View_v005
• dataExtract_InstitutionPortal_SmartForm_Config_View_v004
• dataExtract_StudentDetail_View_v004