Problem:
In the WI State Grant report, Regent Award provided incorrect values under the Tuition Code column.

Cause:
The report inadvertently returned tuition amounts instead of tuition code values.

Fix:
The report will return tuition code values.

Testing:
At a school with Wisconsin State Grants, run the WI State Grant report within Regent Award. Confirm the values provided under the Tuition Code column are correct.

Problem: 
Some students had a blocking document that was configured to prevent 2017-2018 Pell awards from packaging and exporting to COD. Regent Award unexpectedly adjusted Direct Loans that were associated with an Award Period that contained the 2017-2018 Pell grants.

Cause: 
When Regent Award packaged the students, the system unexpectedly did not apply the Pell award amounts.

Fix: 
When Regent Award packages other awards that are not restricted by a blocking document, the system will include all amounts regardless of blocking documents in the award period.

Testing: 
Configure a document that blocks packaging for 2017-2018 Pell. Assign the document to a student that has Pell on the same award period as Direct Loans. Package the student. Confirm the loans are not adjusted due to Pell being blocked from packaging.

Problem:
Regent Award was incorrectly populating an error message in the Modify Award Wizard (MAW) stating that a task was blocking packaging when a task was not triggered on the student record that was configured to block packaging.

Cause:
The "Review Eligibility Change" task was automatically created when attempting to process a manual award via MAW. The task blocked awarding and did not allow the process to complete. Since the MAW process was not fully completed through the final step, the task was not visible in the Task tab.

Fix:
The Regent Award logic for the "Review Eligibility Change" task has been modified to prevent the creation of the task while MAW is running. The task will be added during Modify Academic Plan or Batch Packaging processes, once the updates in MAW have been completed.

Testing:
Navigate to an affected student and access MAW for an award needing adjustment. Update the award on Step 1 and move to Step 2 of MAW. Confirm that an error message does not occur stating that a task is blocking packaging of the award.

Problem: 
A 2018-2019 FAY Pell Award was inaccurately calculated based on Year Round Pell (YRP).

Cause: 
YRP amounts were not being correctly re-evaluated during the R2T4 calculations.

Fix: 
The Pell Grant amount calculation method after R2T4 takes place was fixed to avoid overawarding.

Testing: 
Navigate to the affected student. Execute R2T4 for the withdrawn term. Run packaging. Verify the award's amount calculated is based on YRP. The amount should be recalculated for terms which the student had withdrawn. No overawarding for more than 150% should occur.

Problem: 
Some term students had Manual awards for the Ohio College Opportunity Grant (OCOG). Regent Award unexpectedly moved some disbursements from the Summer 2018 crossover term to the Fall 2018 term.

Cause: 
During packaging, Regent Award detected a Federal Award Year (FAY) on the OCOG award that was different than the default FAY on the crossover term. Regent Award repackaged the OCOG award and moved the disbursements to the next term with the same FAY.

Fix:
Regent Award will package all payment periods for OCOG that would be included in the FAY, including crossover periods.

Testing: 
Access an affected student who is eligible for OCOG in both Summer and Fall 2018 terms. Package the student. Confirm the OCOG disbursements remain packaged for Summer 2018 instead of moving to Fall 2018.

Problem: 
An error prevented TEACH awarding. Closed enrollments with a prior grade level were causing Regent Award to use an undergraduate ISIR when attempting to package for the TEACH Grant for a Graduate level program.

Cause: 
Historic closed enrollments were being used in the Loan Period Grade Level evaluation, thus causing the incorrect enrollment to be used for determining TEACH Grant eligibility.

Fix: 
Regent Award logic was modified to exclude historic closed enrollments during the evaluation of the Loan Period Grade Level to allow the correct awarding of TEACH Grants.

Testing: 
Navigate to a student that had an Undergraduate to Graduate Program change completed and the Graduate Program is TEACH eligible. Ensure a Graduate level ISIR is active for the student. Attempt to award TEACH for the active Graduate program by adding the award via the Add Award Wizard. No error should occur.

Problem: 
Regent Award packaged unexpectedly low amounts for the Ohio College Opportunity Grant (OCOG). The student had remaining semesters of eligibility, as imported on the OCOG Eligibility Query roster.

Cause: 
Regent Award incorrectly reduced the OCOG value in the remaining semesters because of existing paid disbursements.

Fix: 
Regent Award's logic was updated to prevent paid disbursements from reducing the remaining semester amounts.

Testing: 
Navigate to an affected student who has a paid OCOG grant. Import an OCOG Eligibility Query with an updated remaining semesters value. Package the student. Confirm OCOG is packaged correctly for the remaining semesters.

Problem:
A fund was configured to package to Direct Costs. Regent Award unexpectedly packaged awards from the fund for $1. The extra dollar caused aid exceeding the Direct Cost.

Cause:
Regent Award incorrectly adjusted the Unmet Costs using the Federal Direct Loan disbursement fees. The fees caused a positive Unmet Direct Cost remaining.

Fix:
Regent Award will consider Federal Direct Loan disbursement fees when calculating remaining Unmet Direct Costs.

Testing:
Configure a fund in the Packaging Philosophy to package to Direct Costs only. Access an affected student who has Direct Loans. Package the student to Direct Costs. Ensure the configured fund's awards are not awarded above Direct Costs.

Problem:
A term student had incorrect prorated loan amounts in a shortened Remaining Period of Study (RPS) Academic Year. The student was over-registered for more units than were needed to finish their program. The Direct Loan amounts were unexpectedly based on the registered units in the AY, instead of using the remaining units in the program.

Cause:
The program ended before the Academic Year finished. The last term of the RPS AY was not correctly accounted for in the Award calculation logic.

Fix:
Logic was updated to allow term proration to occur when a program ends, even if that ending term is not the final term in the Academic Year.

Testing:
Access an affected term undergraduate student who has a program that will be complete mid-AY, and has Direct Loans in a shortened Remaining Period of Study. Package the student. Confirm the loans are prorated based on the remaining units to complete the program. The loans should not use the total registered units for the AY.

Problem: 
Regent Award did not auto-package the Ohio College Opportunity Grant (OCOG) for some term students who met the eligibility requirements.

Cause: 
For crossover terms, Regent Award did not package the 2018-2019 OCOG if the term had a packaging blocker for the 2018 Pell grant. Additionally, the crossover payment period costs were not included in the OCOG award period, which decreased the eligibility.

Fix: 
Regent Award will award OCOG for the latter FAY, regardless of the former FAY awards present within the crossover term/payment period. The award period will include costs for all eligible payment periods.

Testing: 
Package affected students using Batch Packaging or the Modify Academic Plan wizard. Confirm OCOG is auto-packaged for eligible terms.

Problem: 
For some term SAY students, some Unsubsidized Loan awards were incorrectly underawarded by $1 in the final term of an Academic Year (AY).

Cause:
Regent Award was unexpectedly rounding Unsubsidized Loan amounts incorrectly for the last term or payment period in an Academic Year.

Fix:
Regent Award will apply standard rounding rules for Federal Direct Loans.

Testing:
Access an affected student who has a current Unsubsidized loan. Package the student via Batch Packaging (BP) or Modify Academic Plan (MAP). Confirm the Unsubsidized Loan packages correct amounts in the last term in the AY, based on standard rounding rules.

Problem: 
A student had error messages whenever a user tried to access Modify Award Wizard, Add Award Wizard, or Modify Academic Plan. The error was different depending on the environment: "Index was outside of the bounds of the array" or "canceled award amount exceeds paid amount."

Cause: 
A Manual Award was canceled. However, the award still had a nonzero amount and a higher than zero paid amount, which resulted in an incorrect award amount.

Fix: 
Updated validation logic for canceled, manual, paid awards. The new logic will apply when a canceled Manual award amount is higher than the paid amount, and the award amount does not equal the sum of the payment period amounts. Regent Award will recalculate the amounts in each Payment Period. Regent Award will then re-check the total amounts for all payment periods together.

Testing: 
Find affected students. Package the student using Modify Academic Plan wizard. Edit the student's Unsubsidized loan using Modify Award Wizard. Use Add Award Wizard to add other awards. The wizards should package the student successfully without errors.

Problem: 
Regent Award scheduled some Pell Additional Eligibility disbursements for dates that fell outside of the term dates.

Cause: 
When there was no change to the award amount, Regent Award did not update the scheduled disbursement dates for all scheduled disbursements.

Fix: 
Logic was modified to ensure that all scheduled disbursements are updated to adhere to the configured Disbursement Schedule Setup.

Testing: 
Access a student record for whom additional Pell disbursements have been scheduled. Package the student. Confirm that the scheduled dates fall within the term associated with the Pell disbursements.

Problem: 
A Regent Award user edited a Direct Loan using Modify Award Wizard (MAW). MAW gave an unexpected error when users tried to update the Adjusted Amount: "You cannot enter a higher Paid Amount on this disbursement." The Adjusted Amount was lower than the existing Paid Amount.

Cause: 
Validation logic within MAW did not account for loan disbursement fees when calculating the gross Paid Amount.

Fix: 
When a user adjusts disbursements in MAW, the wizard will consider disbursement fees.

Testing:
Navigate to an affected student with a paid, two-term, Federal Subsidized or Unsubsidized Loan. Edit the loan in Modify Award Wizard. Enter an amount two dollars ($2) lower than the previously offered amount. In Step 2, update each Payment Period to be one dollar ($1) less than the previously offered amount. In Step 3, enter the same amounts entered under Step 2. Ensure MAW does not give any error message about the "higher Paid Amount." Continue through the wizard. Refresh the Academic Plan screen.

Problem:
The Ohio College Opportunity Grant (OCOG) was not packaging in Regent Award for students who underwent a Program Change from a program that was not eligible for OCOG to a program that is eligible for OCOG.

Cause:
Regent Award was not packaging OCOG when the Federal Award Year (FAY) contained payment periods from an ineligible and eligible program after a program change was completed.

Fix:
After a program change, Regent Award will package OCOG for eligible payment periods in the OCOG-eligible program.

Testing:
Complete a Program Change for a student where the original program is not eligible for OCOG, and the new program is eligible for OCOG. Import an Eligibility Query file for the student. Package the student. Ensure OCOG is packaged for the new, eligible program.

Problem:
After a term student had a Leave of Absence (LOA) break, Total and Term Federal Pell Grant eligibility were calculated incorrectly.

Cause:
The system calculates the number of weeks to use from the term when determining what to apply to a Federal Pell Grant calculation. For Federal Pell Grant calculation (Formula 3) the number of instructional weeks in the term, not the number of instructional weeks the student is actually taking, should be used in the formula. The system incorrectly removed weeks from Federal Pell Grant calculation because the student had an LOA break. The removal caused the incorrect decrease of Federal Pell Grant calculated amount.

Fix:
The code change was applied to ignore students' LOA breaks for Pell grants.

Testing:
Navigate to an affected student. Check Federal Pell Grant eligibility via accessing Modify Award Wizard. Total eligibility amount should be based on the total number of instructional weeks, e.g. $5920 for a regular Academic Year. Check eligibility for the term with the LOA. The term's Pell amount should be based on the instructional weeks.

Problem: 
A student had a paid Wisconsin State Grant for a crossover Summer term. A user changed the Crossover FAY Override in Advanced Packaging. When the student was packaged, the system unexpectedly zeroed out the Summer amount for Wisconsin State Grant and canceled the paid disbursement.

Cause: 
The Wisconsin State Grant can only award from the former FAY. The user changed the crossover term to award from the latter FAY.

Fix: 
When a crossover term has a positive Wisconsin State Grant amount, but a user changes the term's Crossover FAY Override to the latter year, the application will keep the existing Wisconsin State Grant amount. The grant will still be awarded from the former FAY.

Testing: 
Navigate to a student who has a paid 2018 Wisconsin State Grant in a crossover term for Summer 2018. Clear any packaging blockers. In the Modify Academic Plan wizard (MAP), select "Advanced Packaging" (MAP Step 2). Set the Crossover FAY Override to 2018-2019. Continue through the wizard. Refresh the Academic Plan. The system should not change the Wisconsin State Grant.

Problem: 
Some students were charged twice with an Enrollment Fee after a Program Change.

Cause: 
The term that contained the Enrollment Fee Cost Item of lifetime cost frequency was not returned in terms searched after the Program Change.

Fix: 
Enrollment search cache was reworked to make sure that Cost Items previously stored could not be changed. The Lifetime cost frequency was changed to no longer match to a term with a specific program.

Testing: 
Navigate to an affected student. Package the student. Compare Awards in Spring 2018 and Summer 2018 in the Awards tab. The student should be assessed only one time with the Enrollment Fee Cost Item.

Problem:
When files were received from the SAIG Mailbox, all message classes for a specific process type were being imported in error when specific message classes within that process type were not marked as active.

Cause:
Regent Award was incorrectly importing files for inactive message classes (as specified on the Message Class setup screen).

Fix:
Logic was modified to ensure only active message classes as chosen on the Message Class setup screen are imported during the SAIG Receive Files process.

Testing:
Ensure that the SAIG Mailbox is configured. Access the SAIG: Receive Files screen. Select to receive files for a process that's configured with both active and inactive message classes. Ensure only those message classes marked as active are received.

Problem: 
A term student posted attendance and withdrew before their FAY 2019 Pell grant was originated. When the school added a Course Adjustment with Registered Program Applicable Units, the award unexpectedly still did not originate. An error message said, "The origination options for the Disbursement Schedule have not been met - this Award cannot be originated at this time."

Cause: 
The Disbursement Schedule origination settings checked for a different set of registered units than the Registered Program Applicable units.

Fix: 
The Disbursement Schedule origination options were corrected to use the Registered Program Applicable units and Attended Program Applicable units. Those sets of units also include qualified remedial units and Program Applicable units added via Course Adjustments.

Testing: 
Navigate to an affected student who has a crossover term with no current registered units and with a non-originated, FAY 2019 Pell Grant in an Accepted status. Cancel or zero out any 2018 Pell money for the term. If the student currently would not meet the Disbursement Schedule's origination requirements, add a Payment Period level course adjustment with nonzero program-applicable registered units. Package the student. Export the Pell to COD for Origination. The Pell grant should successfully export.

Problem: 
Some Course Adjustment operations did not save data to a Data View.

Cause: 
Course adjustment records were saved for active programs only.

Fix: 
The Data View was updated to include course adjustment records both for active and inactive programs.

Testing: 
Navigate to Courses tab of an affected student who has an Inactive program. Click Add Course Adjustment button and add a new Course Adjustment for the Inactive program. Save and close. In the database, verify that dataExtract_CourseAdjustment_View contains a corresponding record about the added course adjustment.

Problem: 
During the cancel/recreate process, Regent Award was not reviewing the assigned documents or tasks that block packaging, thus allowing the awards to be canceled and recreated in error.

Cause: 
Regent Award did not take into account blocking documents or tasks when completing the cancel/recreate process for loans that had not paid prior to the October 1 cutoff.

Fix: 
Logic was added to Regent Award to check for any blocking documents or tasks prior to completing the cancel/recreate process.

Testing: 
Place a blocking document on a student record that has not had a first disbursement for a Federal Direct Loan paid prior to the origination fee update of 10/1. Run Batch Packaging. Confirm the loan is not canceled and recreated.

Problem: 
A term without course registration was added after a Substantially Equal program change.

Cause: 
Regent Award determined the incorrect next term during the program change.

Fix: 
A new system check was added to validate the correct forthcoming term after a program change.

Testing:
Load SBL file with a program change for the affected student. Navigate to the Academic Plan and confirm student does not have a Summer 2019 term. Process program change as Substantially Equal via Program Management Wizard. View Academic Plan. Confirm that Summer 2019 does not appear on Academic Plan.

Problem:
Export Student Transactions (EST) resulted in Error 0066: Award is not Associated to a Disbursement Schedule.

Cause:
An imported award in a past period had not been linked to a fund's disbursement schedule.

Fix:
Regent Award logic was updated so an imported award is assigned with a disbursement schedule during Student Packaging for current and past periods.

Testing:
On an affected student, import an award into a closed period. Package the student. Export EST for DRI for the student. Make sure EST error 066 does not occur.

Problem: 
ISIR Verification/Correction Wizard reverted back any value selection for High School State field.

Cause: 
Incorrect sorting was set up for drop-down options for ISIR column in ISIR Verification/Correction Wizard.

Fix: 
Sorting options have been fixed for High School State ISIR column.

Testing: 
Navigate to an affected student. Select an active 2019-2020 ISIR. Click 'Start ISIR Verification/Correction Wizard' button. No values should be pre-populating for ISIR question "High School State." Update the field with a state abbreviation value. Save the changes. No errors should occur.

Problem: 
On a 2018-2019 ISIR, Regent Award incorrectly calculated a different Expected Family Contribution (EFC) than the Primary EFC provided. The user made no changes to the factors used in determining the EFC within the ISIR Verification/Corrections Wizard.

Cause: 
Regent Award and Regent Review unexpectedly used the response to "Is Student Married?" field from the ISIR when determining the marital status for the EFC formula.

Fix: 
Regent Award and Regent Review will use the appropriate Student Marital Status or Parent Marital Status fields when determining the marital status for an independent or dependent EFC.

Testing:
Access the ISIR Verification/Corrections Wizard for a student's 2018-2019 ISIR. Change the response to Question 69, "Is Student Married?" only. Save and Continue. Confirm the EFC does not change upon entering Step 2 of the Wizard.

Problem: 
When Regent Award packaged students with 2018-2019 Pell grants, packaging failed with an error such as "Failed to Process. Error Msg: Federal Pell Grant has an already-released or paid disbursement."

Cause: 
Regent Award unexpectedly applied the increased eligibility of Federal Pell Grants to previously paid disbursements, instead of creating new disbursements for the increased eligibility.

Fix: 
For COD-reported funds, the system will create a new disbursement when a student's award amount increases over the paid disbursement amount. The new disbursement will be created regardless of the Fund Setup configuration for "Allow Auto-Adjustment of Paid Disbursements."

Testing: 
Navigate to a student receiving the packaging error. Package the student via Batch Packaging or the Modify Academic Plan wizard. Confirm the student may be successfully packaged without receiving the described error message.

Problem: 
Some 2017-2018 Pell grants could not be exported to COD for correction. Regent Award unexpectedly marked the affected grants as being queued for packaging. The COD export occurred after the scheduled cutoff date of October 1 for prior Pell changes for that Federal Award Year (FAY).

Cause: 
The Pell grants were on payment periods where the PP FAY did not match the Pell award FAY. Regent Award detected the different FAYs and marked the Pell awards as needing reprocessing.

Fix: 
During packaging, Regent Award checks for positive amounts in a FAY-based award. Regent Award ensures the Payment Period FAY matches the award period FAY. For Pell grants after the end of the award period, Regent Award does not repackage the awards. For the previously affected Pell awards, a data-cleanup script corrected the award period FAYs and the "queued for packaging" validation error. The script also marked the awards for export to COD.

Testing: 
Test after the October 1, 2018 Pell cutoff date. Navigate to a student already packaged with a 2017-2018 Pell. Package the student via Batch Packaging or the Modify Academic Plan (MAP) wizard. Navigate to the student's Activity Tab and examine the Activity Log. Confirm the system did not repackage the 2017-2018 Pell grant.

Problem: 
Regent Award incorrectly rounded some Pell amounts per payment period. The awards were using Pell Formula 3 calculations.

Cause: 
Regent Award used incorrect rounding rules for distributing Pell Formula 3 amounts per payment period.

Fix: 
Regent Award's logic was updated to ensure proper rounding in Pell Formula 3 calculations per payment period.

Testing: 
Navigate to an affected student in a Pell Formula 3 program. Package the student via Batch Packaging or Modify Academic Plan. Confirm that the Pell awards in each period are rounded based on the Federal Student Aid guidelines.

Problem: 
At a term school with Modules, Regent Award calculated incorrect Loan Fee amounts for some students. The Loan Fee amounts were two times the expected values.

Cause: 
Regent Award used incorrect units for the Loan Fees amount. The system used the total number of registered units in each Module, in addition to the total registered Program Applicable units in the term.

Fix: 
Regent Award will use the term's Total Registered Program Applicable Units when calculating the Loan Fee amount.

Testing: 
At a school with Modules, navigate to an affected student. Check the Loan Fees amount on the Awards tab. The amount should be based on the Loan Fees from the Cost Setup configuration and Registered Units from the Academic Plan.

Problem: 
Modify Academic Plan (MAP) functionality did not work for students after adjusting manual Academic Year. The system showed Error validating plan for Student: Award duplicates Award's FAID (Financial Award ID).

Cause: 
The system tried to package a loan on an existing Loan Period that was no longer linked to a manual AY. For example, the Loan Period had a different FAY than the updated FAY on the manual Academic Year. The Loan Period contained an award that was marked as not managed by RNA.

Fix: 
New logic was added for when Regent Award is checking loan period linkage to the loan period definitions for a manual AY.

Testing: 
Navigate to an affected student and package using MAP. The student should be successfully packaged.

Problem: 
For a few nonterm students, Regent Award unexpectedly calculated an incorrect number of Cumulative Units on the Academic Plan.

Cause: 
Regent Award was incorrectly calculating Cumulative Units after a student underwent several nonterm Program Changes, including multiple instances of the same program.

Fix: 
Regent Award will calculate the correct Cumulative Units based on the most recent program change that was processed.

Testing: 
Navigate to an affected student that underwent a program change. Package the student. Confirm the Cumulative Units are reflected correctly based on course data.

Problem: 
A user edited an award in Modify Award Wizard (MAW). The user changed the award to Canceled status and continued through the wizard. MAW appeared to cancel the award. However, when the user viewed the award on the Awards tab and Academic Plan, the award was unchanged.

Cause: 
Some User Interface code libraries were accidentally missing.

Fix: 
The missing system libraries were added back to the application.

Testing: 
Navigate to the Awards tab of an affected student. Edit an affected award in Modify Award Wizard. Change the award's status to 'Canceled' in MAW Step 1. Proceed through further steps and complete the wizard. Navigate to Academic Plan and verify that award's status is 'Canceled'.

Problem: 
Regent Award calculated incorrect Anticipated Units on the Academic Plan as a nonterm student was nearing their program completion.

Cause: 
Anticipated Units were calculated incorrectly after a nonterm Substantially Equal mid-year program change. The prior program's units, in the first payment period of the Academic Year (AY), were unexpectedly added to the Anticipated units. The prior program's units were already included in the transfer units for the new program.

Fix: 
Regent Award will correctly calculate Anticipated units after a mid-year Substantially Equal program change.

Testing: 
Navigate to an affected nonterm student who underwent a mid-year Substantially Equal Program Change. Package the student. Confirm the Anticipated Units are reflected correctly in the final Academic Year.

Problem: 
Nonterm students were progressing to the second Payment Period (PP) and did not have completed Progression in the required Units and Weeks.

Cause: 
The system unexpectedly ended the first PP of the students and started the second PP regardless of the insufficient amount of Progression Units in order to complete the first PP.

Fix: 
The system will extend the first Payment Period until there will be a sufficient amount of Progression Units.

Testing: 
Navigate to the affected students and check the number of Progression Units in the Program Management Wizard. If the number of Progression Units is less then half of the Units in the Academic Year definition, the student should continue in the first Payment Period.

Problem: 
Intermittent delays were occurring in Regent Award processing.

Cause: 
Regent Award had a resource contention with schools that shared a server.

Fix:
Logic was updated to ensure delays with processing no longer occur for schools that share a server.

Testing:
Ensure multiple users are logged into the environment. Each user will need to simultaneously run a process, e.g. each user will process and finalize an R2T4 at the same time. Ensure the environment continues processing without a delay occurring.

Problem: 
Regent Award was unexpectedly presenting an "object reference" error message when users attempted to save and finalize an R2T4 within the R2T4 Wizard.

Cause: 
Regent Award was not pulling funds into an R2T4 when the Federal Award Year (FAY) on the loan period differed from the FAY on the payment period.

Fix: 
Regent Award logic was modified to disregard scheduled disbursements with a $0 amount when multiple FAY based awards are present when deciding which disbursements to use in an R2T4 calculation.

Testing: 
Navigate to an affected student that has crossover awards on the R2T4 period. Attempt to save and finalize the R2T4. Confirm the "object reference" error message no longer occurs.

Problem: 
A term student with modules had two R2T4s. Regent Award unexpectedly calculated the Pell eligibility solely based on the first, Reversed R2T4 amount. The system did not apply the Post-Withdrawal Disbursement (PWD) from the second, Finalized R2T4.

Cause: 
The amounts from the first finalized R2T4 were not being marked as updated during packaging, which caused the amount to update to $0 when processing any subsequent R2T4s in the same term/payment period.

Fix: 
Logic was added to Regent Award to ensure the amount from the first finalized R2T4/PWD is included in any subsequent R2T4 processing.

Testing: 
Complete an R2T4 for a student that results in the student retaining some Pell funds. Reverse the R2T4. Package the student and ensure the eligible Pell remains on the student's account. Process a subsequent R2T4 and ensure the Pell award populated in the R2T4 calculation includes the amount from the first R2T4.

Problem:
Regent Award was incorrectly presenting an error message on the R2T4 Wizard stating "PP Start Date must be before the Scheduled PP End Date."

Cause:
The R2T4 wizard presented an error when there were no completed courses prior to the Date of Determination.

Fix:
Logic was modified to ensure an error is not presented when a student does not complete any courses prior to a Date of Determination for an R2T4 calculation.

Testing:
Navigate to a student needing an R2T4 that has not completed any courses prior to the Date of Determination. Access the R2T4 Wizard and attempt to finalize the R2T4. Ensure the error message is not presented.

Problem: 
R2T4 was not recalculating Year Round Pell amounts for withdrawn courses.

Cause: 
Regent Award was not re-evaluating Year Round Pell amounts during R2T4 calculations

Fix: 
Regent Award checks for a finalized R2T4 in a payment period. If a finalized R2T4 exists, any Year Round Pell amount totals are set based on the resultant R2T4 calculations.

Testing:
Package a student who has an R2T4 resulting in a refunded Pell amount. Regent Award should keep the Pell amount at the same R2T4 recalculated amount. Regent Award should not create any extra Year Round Pell disbursements. Any preexisting, erroneous YRP disbursements should be cancelled for that payment period.

Problem: 
Regent Award was unexpectedly rounding R2T4 refunds incorrectly after finalizing an R2T4.

Cause: 
Regent Award was incorrectly ordering scheduled disbursements. For example, Unsubsidized Loan was being packaged prior to a Subsidized Loan in the R2T4 period when determining the calculated gross amount after finalizing an R2T4.

Fix: 
Logic was created to ensure the correct ordering of the scheduled disbursements occurs after finalizing an R2T4. For example, a Subsidized Loan must be packaged prior to an Unsubsidized Loan based on the Packaging Philosophy.

Testing: 
Navigate to a student needing an R2T4. Complete and Finalize an R2T4 where a loan refund results in cents (e.g. $980.60). Process an EST and confirm the refund is rounded correctly (e.g. $981).

Problem: 
The Disbursement Information Report was not including non-Title IV funds in the output.

Cause: 
Incorrect logic in the report unexpectedly joined Common Origination and Disbursement (COD) data and non-Title IV awards.

Fix: 
The report view was corrected with improved logic for COD data and non-title IV awards.

Testing: 
Run the Disbursement Information Report for non-Title IV funds and confirm data is populated.

Problem: 
A SAY school, using Academic Year (AY) based SAP, had provided a historic SAP status on the SBL. When a student was subsequently packaged (with the SAP process ran during packaging), the SBL-provided historical SAP status was unexpectedly being associated to the future, non-historic Fall and Spring terms (i.e, AY1).

Cause: 
Incorrect logic propagated this historical SAP status to future AYs, despite the fact that neither the "Perpetuate SAP" or "Inherit SAP" features were in use.

Fix: 
The logic was corrected to ensure that the SAP status is not propagated to future terms when setup does not designate that the system should do so.

Testing: 
Provide a historical SAP status for a student, then package and run SAP. The Historic SAP status will determine eligibility for awards for the student's first Academic Year in Regent Award. The actual SAP status associated with the first Academic Year in Regent Award remains as "Not Calculated."

Problem: 
Regent Award was failing to import an entire SBL file when a single record within the SBL file produced a validation issue.

Cause: 
Data in an SBL file included two active programs for one student and caused a data validation issue. When the SBL file was imported, Regent Award was failing to import the entire file due to the one record causing a validation issue.

Fix: 
When multiple programs exist that match the next program on the SBL, Regent Award will only consider the most current matching program when importing the SBL.

Testing:
Use an SBL file containing multiple, valid student records, and an invalid record where there are two active programs associated with one student. Import the SBL file. Confirm the file imports successfully for all students except for the single student with a validation issue.

Problem: 
Regent Award was not correctly populating data on the SULA Tab (located within the History Tab) after the import of an NSLDS Financial Aid History (FAH) File.

Cause: 
Regent Award was utilizing an incorrect format when a FAH File was imported that contained SULA data.

Fix: 
Logic was modified to ensure that correct formatting was used when importing a FAH file containing SULA data.

Testing: 
Import an NSLDS FAH File. Navigate to a student with SULA data provided on the NSLDS FAH File. Access the COD Tab and select the SULA sub-tab. Confirm data is populated.

Problem:
Regent Access was utilizing incorrect Student IDs to process questionnaires when there were siblings with the same parent information, leading to incorrect data persisting into the User Interface.

Cause:
The Student Portal was using incorrect Student IDs when processing a student's application data causing the sibling's record to update instead of the student's record.

Fix:
The Regent Access solution was modified to ensure the e-sign control properly aligns with the correct Student ID when processing application data.

Testing:
Create two students via the Student Portal registration page. Complete and e-sign application for the first student and send an invitation for the parent to e-sign. Create the parent's account via the link from email. Ensure available student's document requirement for e-sign is visible. Complete and e-sign the application for the second student and send an invitation to the parent using the same parent's email that was used for the first student. The parent's account already exists so they log in using previously created credentials. E-sign the application for the second student and ensure that the personal information of the first student is not overwritten by the information of the second student.