Problem: Regent is unexpectedly excluding a course from the census units count when the course has an enrolled date that is AFTER the course start date.

Cause: Only considering the Census Date that is >= to Course Start Date

Fix: Updated logic to consider the Census Date that is >= the Greater of Course Start Date OR Course Enrollment Date

Testing: Create a student with courses where the Enrolled Date is after the Course Start Date. Review the census units count. Courses enrolled both before and after the course start date should be included in the count of Census Units.

Problem:
For students who did not have any ISIR, the College Financing Plan (CFP) PDF attachment did not display any Cost of Attendance (COA) items. The PDF also displayed some technical variables instead of the Customized Information and Next Steps.

Cause:
The Cost of Attendance values were set to blank when students did not have any ISIR. The system also displayed variables when the Customized Information or Next Steps had blank values configured for those fields.

Fix:
The ISIR restriction was removed for the COA items. The Customized Information and Next Steps were updated to blank when those values are not configured with content.

Testing:
Confirm the configuration for the 2022-2023 College Financing Plan, PDF Content Type, has blank values for ‘Next Steps Settings Text' and 'Customized Information from UUS Settings Text.’ Reload RNA Setup if any configuration changes occurred. Navigate to a student who does not have any 2022-2023 ISIR. Package the student. In the student’s Communications sub-tab, Notification drop-down menu, select the correct communication that has the PDF attachment configured. Click Add. Refresh. View the new Communication. View the PDF attachment for the 2022-2023 College Financing Plan. Confirm the individual Cost Items in the PDF match the student’s Costs in the Awards tab in Regent Award. Confirm the Customized Information and Next Steps match the configured blank values.

Problem:
Some Scheduled Academic Year (SAY) students had a duplicated, single-term Academic Year containing paid loan disbursements. The duplicated, autowithdrawn terms caused additional loans to be awarded on the correct, enrolled terms in the SAY AYs.

Cause:
The affected students also had additional, invalid terms on their Academic Plans that did not match the SAY program type and were not linked to the students' current programs. When Regent Award recalculated the Academic Plan structure, the system created some incorrect Academic Years. The system then linked the paid disbursements to the earlier, duplicated terms instead of the correct, enrolled terms later on the Academic Plan.

Fix:
Regent Award has more robust logic for handling invalid and/or duplicated terms. The system checks for incorrect academic calendar types when selecting terms for building a student’s Academic Plan. The system also removes invalid and duplicated terms from the Academic Plan. Regent also has improved logic for linking disbursements to the correct term based on the External Term ID and Academic Year.

Problem:
Students were awarded from funds when the students should not have been eligible per the Funds' configured settings in Fund Setup. For example, some students had less than half-time enrollment in a term, when the fund had a Minimum Enrollment Status of Half-Time. Other students had awards in an optional Summer Trailer term when the fund was configured to Exclude Header and Trailer terms.

Cause:
The funds had eligibility set by a Satisfied Document. The Document’s eligibility overrode the other Fund Setup eligibility settings.

Fix:
Regent Award’s eligibility rules were updated to apply the other configured Fund Setup eligibility checks when the fund has initial eligibility determined by a Satisfied Document.

Testing:
Find an affected student who has a Satisfied Document and a current award from a fund with additional eligibility checks. Edit the student’s data, if needed, to ensure the student does not pass all the eligibility checks. Package the student. Confirm the system does not award the fund for the ineligible periods.

Problem:
The Student Experience Portal and Advisor Assist sometimes displayed an error, “An error occurred while converting Regent plan to StudentX plan.” The error prevented users from viewing or interacting with the Financial Aid and Documents components.

Cause:
The Student Experience portal was trying to get a property from the payment period, but the payment period was empty (null). The problem caused an object reference error on the server that prevented the system from displaying data.

Fix:
The Student Experience portal has an additional “not null” check for payment period objects.

Testing:
View an affected student in Advisor Assist or, in a test environment, create a test account for an affected student. Access the Student Experience Portal or Advisor Assist. Confirm the Financial Aid component is displayed as expected. Confirm the student’s Documents are displayed as expected.

Problem:
In Regent Award For SalesForce (RAFSF), a Batch Synchronization job failed with errors.

Cause:
The RAFSF Application Programming Interface (API) was referencing a payment period that was not returned in the API objects from the target environment.

Fix:
A new RAFSF Managed Package was developed and deployed to the affected environment.

Testing:
Deploy the updated Managed Package to the RAFSF environment. Test synchronizing a batch containing the student who had the reported error. Confirm the system successfully synchronizes to SalseForce. Confirm the affected student does not give the error.

Problem:
Regent unexpectedly doesn't award cents amount of Pell from YRP when the full dollar amount is awarded from regular Pell.

Cause:
YRP check for FT amount used wasn't accounting for cent rounding.

Fix:
Regent Award is updated to ensure to account for cent rounding.

Testing:
In Regent Award, package students and check Pell amounts.

Problem:
The 2022-2023 College Financing Plan (CFP) PDF attachment was only displaying a portion of the form.

Cause:
A tag was missing from the communication code.

Fix:
The missing tag was added to the communication code.

Testing:
Test with a student with costs for a 2022-2023 FAY. Package the student, such as with the Modify Academic Plan wizard (MAP). Run a Communication that generates the 2022-2023 CFP communication as an attached PDF. Review the CFP. Confirm the CFP displays accurately.

Problem:
The students were awarded over Sub/Unsub Aggregate limits

Cause:
Regent Award packaged over aggregate limits when re-calculating loan amount for BBAY students

Fix:
The logic was updated to avoid awarding over limits when calculating loan amounts for BBAY students

Testing:
Find student example who reached Sub or Unsub aggregate limits. Load SBL file with HT enrollment into current term. Run packaging. For the loans where the aggregate limit was reached, the system should not package any amounts higher than $0

Problem:
At a Regent Award school with Calculated SAP, students who should have had a Suspended SAP status instead had an incorrect calculated SAP Status of ‘FA Warning.’

Cause:
The system did not calculate a SAP status until the term’s SAP Evaluation End Date was reached.

Fix:
When Regent Award calculates a SAP Status for a Payment Period based SAP policy, the system calculates a SAP status when the term’s SAP evaluation date range start date is reached and the SAP evaluation end date is not in the past.

Testing:
Use a test environment for an affected school configured with multiple Calculated SAP policies using the ‘PP3Step’ SAP frequency. Load a low-GPA SBL Calculated SAP node for a student who had a previous term with an ‘FA Warning’ SAP record in the earlier SAP policy, with a SAP date within the term’s SAP Evaluation Start and End Date range. Package the student. View the Awards tab and SAP Wizard. Confirm the system calculates a ‘FA Suspended’ SAP status.

Problem:
For some students, Regent unexpectedly showed an "Object Reference error" when a user tried to package them using Modify Academic Plan (MAP) or in Add/Modify Award Wizard. The affected students were still Batch Packaged.

Cause:
Two root causes were found. In the SAP logic, some graduate students were not linked to their correct SAP records for their Graduate GPA values. Another, separate check for Early Calculation was missing logic to handle the scenario when an underlying payment period was not present.

Fix:
The ‘Assign Student SAP GPA’ logic was corrected to use the core logic for linking the SAP records. A separate check for ‘null’ values was added to the Early Calculation logic.

Testing:
Navigate to the affected students in Regent Award. Try to use MAP or AAW for the student. Confirm the Wizard proceeds to Step 2 without error.

Problem:
Regent Award for SalesForce (RAFSF) synchronization was failing with several errors, such as “Attempt to de-reference a null object” or “Delete failed.”

Cause:
The system was not splitting awards across Academic Years. A logic bug accidentally put all awards under a single Academic Year in the data sent to RAFSF.

Fix:
RAFSF was updated to properly split awards across Academic Years. The RAFSF package was also updated to accept awards with the same Award ID values across different AYs. A new Page Layout for Awards was created to accommodate changes to the Regent Award ID field.

NOTE: Customers must upgrade to the new RAFSF package when upgrading their associated Regent Award instance to 6.0.0.0 or later. The older Regent Award For SalesForce package will not work with the 6.0.0.0 release.

Testing:
Use a test environment with Regent Award for SalesForce (RAFSF) installed. Upgrade to release 6.0.0.0 and update the RAFSF Package to the new version for 6.0. Reload RNA Setup. Access RAFSF as an Administrator, and assign the new Award Layout v2 page layout to all profiles that use the Award Layout. Synchronize the Regent Award data to RAFSF. Confirm the system synchronizes without error. Run a full RAFSF Batch Synchronization. Confirm the Batch Synchronization job completes successfully.

Problem:
In the Student Experience Portal, when students tried to download a file that was attached to a Document Requirement in Regent (attached manually or in Document Setup), the system gave an incorrect API link ending in “null/” and the Document could not be downloaded.

Cause:
A code update accidentally changed the Student Experience Portal so some variables had slightly different names and they did not match consistently throughout the code (upper/lower/camel case).

Fix:
The problematic code was corrected and deployed to the Student Experience Portal server. It resolved the problem for all clients on the shared server.

Testing:
Use a student who has Document Requirements in the Student Documents in Regent. Attach a file in Regent. Create a test account for the student on the Student Experience Portal. Navigate to the Portal’s Documents area. Try to download the attached file. Confirm the document successfully downloads.

Problem:
For some students who had an R2T4 resulting in a Post-Withdrawal Disbursement (PWD), Regent Award unexpectedly just "spins" and could not open the PWD tab.

Cause:
When the R2T4 wizard tried to load the Institution context, one of the properties was null.

Fix:
Regent Award was updated to set the Institution Context Response flag to True when processing a student R2T4.

Testing:
Navigate to an affected student in Regent Award. View the student’s R2T4. Open the student PWD tab. Confirm the PWD tab is displayed.

Problem:
Regent unexpectedly prompted to enter a Password on an attempt to create a new user account with Single Sign-On (SSO) authentication.

Cause:
Regent updated the user interface validation as part of a password policy update. The validation inadvertently had side effects on the SSO user creation.

Fix:
Regent was updated to make sure a new SSO User can be created without a password.

Testing:
Navigate to Administration, User. Add a new user account. Select the Authentication Type: Single Sign On. Fill in other fields. Make sure Password and Confirm Password are disabled and the new user account can be saved without error.

Problem:
Regent Award was unexpectedly updating Pell amounts over or under by $0.01 or $0.02 (one or two cents).

Cause:
The Pell Grant was configured in Fund Setup to round to Cents. Regent Award sometimes lost accuracy when calculating the Pell per-term amounts to the correct cents precision. The issue appeared due to some prior logic that assumed Pell Grant was always calculated in dollars. In some particular cases, the ruleset method truncated the amount while calculating a contribution of a new per-term amount to the total Pell LEU.

Fix:
Regent Award is updated to ensure increased precision when calculating amounts with cents.

Testing:
In Regent Award, repackage an affected student with a Pell calculation to cents. Confirm the amounts in each term are correct.

Problem:
Some Regent users who authenticated using Single Sign-On (SSO) were being prompted to change their Regent passwords.

Cause:
The Regent User Account default settings were requiring a password change on next login, or required a date value for the password expiration date, for all user accounts including SSO accounts.

Fix:
The Regent system settings were updated to not trigger password changes or password expirations for SSO users.

Testing:
Create a user account that authenticates using SSO. Authenticate to Regent using the SSO account. Confirm the system does not prompt for a password change.

Problem
Grade level change occurred back and forth in the middle of undergraduate program, although sufficient cumulative units amount were present

Root cause
Regent Award was not resetting and tracking cumulative units correctly for non-BBAY academic years

Fix/solution
The system logic was corrected to accurately increment cumulative units

Testing
Find the affected student. Confirm GL for AYs. Run packaging. Confirm that GL does not reduce immediately in the middle of the program and all cumulative units are increased incrementally

Problem:
A packaging error was observed following the Reset Student for Conversion Process Execution. Error stated:
Error validating plan for Student [X]: The number of disbursements was attempted to be increased on a paid Pell Rebuild Award [X] in a closed Enrollment "X" [X]. This student is blocked from packaging.

Cause:
Misordered Pell per-term amounts caused the issue. Some zero dollar per-term amounts in the Pell rounding were applying the cents adjustment incorrectly.

Fix:
A code fix was applied and the rounding method was changed. The sort on Pell rounding was changed to sort on the Payment Period start date. Validation for the rebuild awards was also changed to ensure Pell rounding that skipped applying the cents adjustment when the per-term amount was of zero dollars.

Testing:
Navigate to an affected student and perform MAP (Modify Academic Plan). Confirm the student is packaged with no errors.

Problem:
In Regent Award R2T4 wizard Step 6, the system unexpectedly set some loan amounts in the “Total Amounts to Return” values instead of including them in the R2T4.

Cause:
The system was applying the Award Amount from the most recent COD communication regardless of COD response type. If the most recent COD communication was a Promissory Note or Booking Notification, the Award Amount was $0 and the loan was accounted for in the “Plus Additional” fields instead of the regular R2T4.

Fix:
Regent Award was updated to use the Amount from the most recent Common Record Response (RS) or COD Web Response (WB) types only.

Testing:
Find an affected student who has a most recent COD response on a loan that is not an RS or WB response. Package the student. Create a new R2T4. Confirm the loan amount is included in the main R2T4 calculations. Confirm the Step 6 amounts do not display the loan in the ‘Plus Additional’ fields.

Problem:
Regent unexpectedly created Spouse Documents in Waived status for a Dependent Student after completion of Verification Worksheet (VWS) when the student had previously set an incorrect value for Student Tax Filing Status during FAFSA completion.

Cause:
The Document logic was relying on the Student's Tax Filing Status from FAFSA and ignoring other fields from the Verification Worksheet questions.

Fix:
Regent’s Document automatic creation logic was updated to make sure the Student's Tax Filing Status from FAFSA is verified by additional parameters set during VWS completion.

Testing:
Find a dependent student with an ISIR needing Verification where the Student's Tax Filing Status =2, Married, Filed Joint Return. If needed, add a new VWS Document in REM in NEEDED status in the Student Documents. Create an account on the Student Experience Portal. Complete the VWS as a Dependent Student. Sign out of the Student Experience Portal and sign in as a Parent. Complete the Parent portion of the VWS. Make sure that the system does not create the Spouse’s Tax Transcript and Spouse IRS Verification of Non Filing Letter documents.

Problem:
When a school tried to create a manual R2T4, the R2T4 could not save due to an error: Award Period 2020-2021…doesn’t contain payment period.

Cause:
The payment period contained disbursements from two Pell Grant awards: the regular Pell award for the payment period, and an additional, $0 Pell disbursement from a different FAY in a non-crossover term. When Regent Award recalculated the Pell amount for the R2T4 calculation, the system could not process the extra disbursement.

Fix:
The R2T4 Pell Recalculation was updated to handle Pell grants from two different FAYs when one disbursement is $0.

Testing:
View the affected student’s Academic Plan. View the (Hidden) Award Disbursements. Observe the $0 Pell from the previous FAY. On the Awards tab, add a new R2T4. Save. Confirm the system saves successfully.

Problem:
The Disbursement Details pop-up did not display a disbursement. The disbursement was present on the award and it was successfully paid and sent to COD, but it was not visible in that screen.

Cause:
A display issue prevented displaying the disbursement. The Disbursement Details screen was relying on a certain expected ordering for the disbursements in each term. When the screen collected all the disbursements for the term, it accidentally omitted a disbursement that was outside the expected sequence.

Fix:
The Disbursement Details screen was updated to correctly collect and display all the disbursements for a term.

Testing:
Navigate to the affected student with the missing disbursement. Refresh the Academic Plan screen. Click the per-term amount for the affected award. Confirm the disbursement is displayed as expected on the Disbursement Details screen. Navigate to the Awards screen. Refresh the screen. Click the per-term amount for the affected award. Confirm the Disbursement Details displays correctly.

Problem:
Awards were not reinstating for terms when a manual SAP record with ‘Satisfactory’ status was added after a former status of 'FA Suspended.'

Cause:
The application didn't remove inherited calculated SAP record(s) when new SIS SAP records were loaded. As a result, the system was not able to return a payment period to the award calculation for Satisfactory SAP status.

Fix:
The system removes inherited calculated SAP records when a new SIS SAP record has been loaded.

Testing:
Test at a school with a SIS-provided SAP policy. Find the affected student. Load an SBL data file for a student with 'FA Suspended' SAP status and a later SAP date. Package the student. Run the SAP calculation. Add a manual 'Satisfactory' SAP status. Package the student. Confirm that awards are packaged for terms following the manual 'Satisfactory' SAP status.

Problem:
When an administrator tried to select a Packaging Philosophy, the system unexpectedly did not display the Packaging Philosophy Setup.

Cause:
Some Priority values in the Packaging Philosophy exceeded 9999. The screen had validation that prevented assigning values higher than 9999.

Fix:
The project team was advised to try to use only values between 1 and 9999. The screen validation was updated to handle values between 1 and 99999.

Testing:
At a school that previously saw the error, log into Regent Award with an Administrator account. Go to Packaging Philosophy Setup. Select a Packaging Philosophy. Confirm the Packaging Philosophy Configuration screen is displayed.

Problem:
Regent unexpectedly set a lower Grade Level resulting in an under-award for Direct Loans for some students in clock-hour nonterm programs.

Cause:
Regent incorrectly calculated the Cumulative Units for Grade Level Progression based on the units used for Enrollment calculation.

Fix:
Regent Award logic was updated to make sure the Grade Level calculation correctly accounts for Anticipated, Actual, and Progression units.

Testing:
Find an affected student and Package them. Make sure Grade Level is correctly set.

Problem:
A FAY 2021-2022 Pell Grant was zeroed out right after an automated R2T4 was created.

Cause:
The application canceled an eligible Pell award after calculating the automated R2T4.

Fix:
The logic was reworked so that Regent Award could correctly calculate the eligible Pell award with an automated R2T4.

Testing:
Find the affected student. Make sure that automated R2T4 is enabled. Load a Student Batch Load (SBL) data file with an R2T4 node and Date of Withdrawal for one course, and registration for other courses in the R2T4 term. Run packaging. Verify that the Pell amount is not reduced while the R2T4 is in 'Open' status. Finalize the R2T4. Confirm the Pell amount is reduced when the R2T4 is Finalized.

Problem:
COD rejections and issues with funds not disbursed took place for the Winter 2022 term. The Cease Auto-Packaging indicator was unexpectedly applied to some aid. Some three-term BBAY Academic Years (AYs) consisted of four terms with two different aid types.

Cause:
The system added an extra term to the AY because the first term was not anchored by Title IV Loan Rules.

Fix:
A code fix was applied to remove the fourth term from the AY.

Testing:
Navigate to affected students who have four-term AYs and execute the Modify Academic Plan wizard (MAP). The AY should become of the correct structure, that is, three terms. For students who have Auto-Packaging Cease indicators for Pell and Loans (Subsidized and Unsubsidized loans) before MAP, for testing purposes, an Administrator can change the Auto Packaging Cease (AC) date in the Fund Setup Configuration so that the current packaging date is before the configured Auto-Packaging Cease date, e.g. if configured AC date is 12/31/2021 it can change it to 12/13/2031. After MAP, the AC indicators will be removed.

Problem:
Regent Award was unexpectedly not printing asterisk ( * ) next to the EFC.

Cause:
Regent Award was incorrectly missing an asterisk during the initial development

Fix:
Regent Award is updated to add an asterisk.

Testing:
In Regent Award click on the Print ISIR icon and review the Printed ISIR file.

Problem:
Some $0 Direct Loan amounts were exported to COD when the award amount was not zero, and a linked MPN was present in 'Accepted' status. The exported $0 amounts caused 042 rejects when the award import was attempted at COD.

Cause:
In some cases, Regent Award failed to sum up the term award amounts correctly when the award amount did not match the sum of the disbursement amounts.

Fix:
Award validation amount logic was updated for setting the amounts, including some amount logic from the R2T4 processes.

Testing:
Find the affected student. Export the loans to COD. Confirm the correct loan amounts are exported.

[Release Notes Draft ]
Problem:
The system did not round down Pell by $1 amount for the second term that caused over awarding of Pell Scheduled Award for full Academic Year (AY).

Cause:
The system occasionally over-awarded Year Round Pell (YRP) amount while there was an external Pell award in the same Federal Award Year (FAY).

Fix:
A code fix was applied so that the system truncates YRP amount when there is an external Pell award in the same FAY.

Testing:
Find the affected students and perform Modify Academic Plan (MAP) and make sure that in the current AY, the Pell amount is rounded down by $1 for the second term.

Problem:
The 'Institutional Financial Aid Application' Smart Form had the 'Middle Initial' field required in the Student Information section.

Cause:
The 'Middle Initial' field was marked as a required field in the Institutional Financial Aid Application
questionnaire.

Fix:
The 'Middle Initial' field was updated to be an optional field in the Institutional Financial Aid Application questionnaire

Testing:
Test with a student who has the ‘Institutional Financial Aid Application’ Document in a Needed status. Login to the Student Experience Portal. Open the 'Institutional Financial Aid Application.' At the Student Information section, find the 'Middle Initial' field. Confirm that it is optional but not required. Continue through the Smart Form with the Middle Initial blank. Confirm the Smart Form is completed successfully without requiring a Middle Initial.

Problem:
The 2022-2023 FAY was incorrectly assigned to a term that was in FAY 2021-2022.

Cause:
Regent Award incorrectly assigned the FAY to the year-long, system-created default loan period.

Fix:
The system has corrected logic for assigning an FAY to the default loan period. Existing default loan periods will properly adjust their FAY references when they are repackaged.

Testing:
Find an affected student. Package the student. Confirm the Spring 2022 term is packaged with 2021-2022 FAY awards.

Problem:
In Document Setup, the ‘Federal Award Year’ (FAY) scope setting did not return any values for selection on the Add Document screen.

Cause:
When data was loaded from the client, the request to the server contained no document identifier to retrieve the available FAY list.

Fix:
Client-side changes were applied in Regent Enterprise Management (REM) screens to properly send the document identifier in the request to the server.

Testing:
In Document Setup, open the 'Add Document' screen. Navigate to the 'Non ISIR Assignment Scope' section. Select the Scope: Federal Award Year. Make sure that the list of FAYs is available.

Problem:
Regent Award unexpectedly packaged Pell Grant amounts that were over or under the expected award amount by .01 or .02.

Cause:
The Pell Grant fund was configured to round to cents. Regent Award sometimes had inconsistent precision when calculating the per-term amount to cents in the Pell rulesets. In particular cases, the ruleset method truncated the Pell amount while calculating a contribution of a new per-term amount to the total Pell Lifetime Eligibility Usage (LEU).

Fix:
Regent Award Pell ruleset methods are updated with increased precision when calculating amounts with cents.

Testing:
In Regent Award, repackage an affected student with a current non-Manual Pell Grant amount that is off by one or two cents. Refresh the screen. Confirm the Pell amount is correct.

Problem:
Some students had overawarded Wisconsin State Grants for 2021-2022. The award amounts in Regent were higher than the amounts listed in the Notification Report or the WI Grant calculator.

Cause:
The system used some incorrect WI Grant supplemental values.

Fix:
The code fix was applied with the correct supplemental values for the WI Grant.

Testing:
Find an affected student who has an overawarded WI Grant amount for 2021-2022 Academic Year that is not manually corrected. Perform Modify Academic Plan (MAP). Confirm the WI Grant amount matches the values from the 21-22 WI Grant Calculator.

Problem:
A student's awards were not packaged to the amount of Direct Costs. The student had selected the 'Recommended Borrowing' plan in the Student Experience Portal.

Cause:
Regent Award incorrectly handled the Net Amount calculations during the packaging process. As a result, the system failed to include the fees back to the award balances in the final calculation step, and that caused underawarding

Fix:
The logic for the Regent Award balance tracker was updated to apply fee amounts to the award balances to avoid underawarding.

Testing:
Find the affected student. Run packaging in the Modify Academic Plan (MAP) wizard with 'Package to Direct Cost' option. Navigate to the Awards tab. Refresh. Verify the award amounts are packaged for the loan period in question. Confirm the total award amounts are packaged to the amount of direct costs.

Problem:
Regent unexpectedly exported some Direct Loan disbursements to COD twice after R2T4 Finalization, resulting in COD reject codes 205 and 222.

Cause:
Regent incorrectly did not update the COD flag for disbursement that triggers COD export when the disbursement amount was changed after R2T4 Finalization.

Fix:
Regent Award R2T4 processing logic was updated to make sure the COD flag is correctly updated on the disbursement level after R2T4 Finalization.

Testing:
In Regent Award, perform an R2T4 that changes the current disbursement amount for a Direct Loan in the term. Finalize the R2T4. Export the loan to COD. Make sure there is only one disbursement in the COD export data file.

Problem:
Regent Award was unexpectedly blocking packaging with a “duplicate key” error.

Cause:
Regent Award sometimes incorrectly enumerated the Academic Year numbers. The bug caused some duplicated Academic Years and the associated award periods, or a gap between academic years.

Fix:
Regent Award is updated to ensure that Academic Years will get correct and sequential numbers while processing.

Testing:
In Regent Award, find an affected student who previously gave a “duplicate key” error. Package the student. Confirm the student is packaged without error.

Problem:
An administrator used Export Setup Configuration (XML) for the Document and DocumentAssignmentISIR settings. The XML files returned errors when they were imported back into Regent Award

Cause:
Regent Award allowed the values to add duplicated External Document ID values, which should be unique per Campus. The duplication caused errors on import.

Fix:
A validation layer was added onto the Document Setup screen to verify the presence of duplicated External Document ID values in the database when a user adds a new Document Requirement with a External Document ID value already in use. The screen also fixed a bug in the checkbox for ‘Always apply document requirement to all Federal Award Years’ when the Non ISIR Assignment Scope was changed from ‘Federal Award Year’ to a different scope.

Testing:
Log in to Regent as an Administrator. Perform the Export Process with Export Setup Configuration, Document and DocumentAssignmentISIR, XML format. Import the exported file. Confirm no errors occur. Next, navigate to Document Setup. Note an existing External Document ID value. Add a new Document. Try to save the new Document Requirement with an already-existing External Document ID value. Confirm the new Document with the duplicate External Document ID value won't be saved. Find a Federal Award Year scoped Document with ‘Always apply document requirement to all Federal Award Years’ selected/checked. Edit that Document to have a different scope type. Save. Refresh. Confirm the checkbox is unselected for ‘Always apply document requirement to all Federal Award Years.’

Problem:
After a Substantially Equal (SE) Program Change (PC) in the middle of the Academic Year (AY), a term student had a grade level changed from two (2) to one (1) as well as an enrolment level change. The Fall 2021 term was added to a Manual AY using the Program Management (PMW) wizard, with Federal Award Year (FAY) 2021-2022, but the Loan Period was not available in Awards tab (Add Award Wizard, Analyze Loan Period menu). On the Academic Plan, the Loans had a 2020-2021 FAY for Fall 2021 and the school could not add Subsidized or Unsubsidized loans for the Fall 2021 term.

Cause:
The system did not correctly process a Grade Level regression (from grade 2 to 1) for the loan period after the SE PC in the middle of the AY.

Fix:
The system will automatically create a Grade Level regression (from 2 to 1) loan period during packaging after a SE program change in the middle of AY for term students. A manual loan period will not be required in this case.

Testing:
Test with a term-based student with a current Academic Year that starts in the Summer term and ends with a Fall term. Load an SBL with a Program Change for the student, with fewer transfer units in the new program, resulting in a grade level reduction for the student. Package the student. Process the Program Change as Substantially Equal. Confirm the Program Change is successful. Confirm the loan amounts are packaged as expected for the different grade levels. On the Loans tab, confirm the FAY on each loan is correct and the Financial Award Period Begin and End dates match the Loan Period dates. On the Awards tab, view the ‘Analyze Loan Periods’ drop-down menu. Confirm the Loan Periods are displayed and include the loan. Click Add Award. In Add Award Wizard (AAW), select the Loan Period in the AY for the individual term. Confirm AAW continues through to AAW Step 2 without error.

Problem:
Regent Award was unexpectedly updating the adjusted Release Date to 10/1/2021 for multiple Subsidized and Unsubsidized loan disbursements, despite the awards not being manually adjusted.

Cause:
Regent Award sometimes incorrectly changed the disbursement adjusted release date.

Fix:
Regent Award is updated to ensure that the disbursement adjusted release date is only updated when the award is active; the award had no payments; and the processing date is after the next origination fee start date.

Testing:
Test using a backup copy of the data from before the disbursements moved for the affected students. In Regent Award, view an affected student’s Disbursement Details. Package the student. Make sure that the adjusted Release Date has not changed.

Problem:
An R2T4 manually entered Pell Amount that Could Have Been Disbursed was unexpectedly not showing in the Post-Withdrawal Disbursement (PWD) tab of the R2T4 Wizard.

Cause:
Regent Award was not creating R2T4 PWDs for some Pell Awards. The system was overriding the Pell Amount That Could Have Been Disbursed with the Pell Amount Disbursed when the Pell Amount Disbursed was not null.

Fix:
Regent Award uses the correct value for 'Pell Amount That Could Have Been Disbursed' for the R2T4 Step 6 and PWD calculations. The Pell logic now matches the logic used for other fund types in R2T4 and PWD.

Testing:
In the R2T4 wizard, manually enter a Pell Grant amount to create a PWD. Navigate to the PWD tab in the wizard. Confirm the manual Pell Grant amount is on the PWD tab.

Problem:
Regent Award unexpectedly removed an undergraduate program’s final Academic Year from the Academic Plan during an undergraduate-to-graduate program change into a nonterm program.

Cause:
Regent Award used the Course Enrollment Program's starting Course Enrollment Number in order to start a new nonterm program.

Fix:
Regent Award is updated to ensure that an application will recalculate a Course Enrollment Program's starting Course Enrollment Number value if an old and a new program do not intersect.

Testing:
In Regent Award, repackage the affected student. Confirm all the Academic Years are present.

Problem:
A student had an R2T4 with additional Subsidized Loan amounts returned above the amount calculated by the R2T4 worksheet.

Cause:
In some circumstances, the system used an incorrect order to decrease disbursements after an R2T4 refund.

Fix:
The order of disbursements decrease after the refund was corrected to Unsubsidized Loan, Subsidized Loans, PLUS Loans, Pell Grant, FSEOG, TEACH, and IASG.

Testing:
Test using a test environment where the server date can be changed (a “time machine”). Load a backup copy of the affected student with paid Subsidized and Unsubsidized loans before the R2T4. Create an R2T4 for the affected term. Confirm the R2T4 calculations are correct. Finalize the R2T4. Package the student. Confirm the Subsidized loans are not zeroing out. Confirm the Subsidized loans are not in Cancelled statuses. Use the Export Student Transactions (EST) process. Confirm the paid amounts are adjusted.

Problem:
Some students in Regent Award unexpectedly had Enrollment levels of ‘Actual - None’ for Fall 2021 before the Begin Actual date was reached. The students had loan disbursements canceled in the ‘Actual - None’ terms and additional, extra disbursements were created in other terms, including in another, fully withdrawn term where the new disbursements affected the R2T4 amounts.

Cause:
Regent Award was incorrectly considering enrollments with only 0-unit registered courses as “Actual - None” enrollment level and canceled the loan disbursements for the period.

Fix:
Regent Award is updated to consider enrollments with only 0-unit registered course(s) as Anticipated until the Begin Actual date. Loans will still be calculated based on Anticipated units.

Testing:
In Regent Award, find a student that has a term containing only course(s) with 0 registered and non-program-applicable units which are not withdrawn. Package the student before the term’s Begin Actual date. Confirm the enrollment level is still Anticipated. Repackage the student on or after the term’s Begin Actual date. Confirm the term’s enrollment level changes to ‘Actual - None.’

Problem:
For some nonterm students, the Federal Aid Years (FAYs) for their paid loans were changed when the Academic Plan (AP) was pushed forward. For example, the student’s Academic Year was moving from 2020-2021 to a 2021-2022 aid year start date across the crossover dates.

Cause:
The system mistakenly canceled and recreated paid loans with moving them from their original payment periods.

Fix:
The code fix was applied so that system will keep paid loans in their original payment periods.

Testing:
Find a student in a crossover period with already paid loans for FAY 2020-2021. Move the Academic Year start day to be after July 1st, 2022 (such as by changing the student’s course data). Confirm that the FAYs for the loans do not move forward. Confirm the FAID value is still for FAY 2020-2021. Export the loan to COD for 2020-2021. Confirm the loan is exported to COD successfully.

Problem:
A school was configured to disburse Pell based on Enrollment Level Units. The ACPA EL (Attended Census Program Applicable Enrollment Level at the time that the disbursement was released) and ACPA Units (Attended Census Program Applicable Units at the time that the disbursement was released) did not display for new Pell Grant disbursements, after the prior disbursements had been canceled, in the Disbursement Details screen.

Cause:
The system had conditions that prevented setting the values for ACPA EL and ACPA Units when the override amount was zero or less. These conditions were to prevent disbursement when there was no attendance in the term.

Fix:
A code fix was applied so that the condition was updated to also set the ACPA EL and ACPA Units properties when a term has Attended Census Program Applicable Units.

Testing:
Navigate to an affected student or source a student with canceled Pell Grant disbursements. Using Modify Award Wizard (MAW), add and Schedule a new Pell disbursement in the same Payment Period as the canceled disbursement. The ACPA EL and ACPA Units should populate for the canceled and newly scheduled disbursements in the Disbursement Details screen.

Problem:
The Packaging Philosophy name displayed on the Academic Plan tab and Awards tab did not match the configured option name listed in Modify Academic Plan (MAP).

Cause:
A code change had updated the Packaging Philosophy name only for current or future Academic Years (AYs). The system updated only the AYs where upcoming AYs needed to be packaged with the overriden Packaging Philosophy, but did not override the Packaging Philosophy for the upcoming years (keeping the old values).

Fix:
The code change was reverted.

Testing:
As an Administrator, confirm the current Default values for the configuration settings in Institution Setup → Campus Setup → Packaging Philosophy Setup, ‘Default Campus Packaging Philosophy’ and ‘Alternative Packaging Philosophy.’ If you make any configuration changes, also Reload RNA Setup. View an affected student who uses the Default Packaging Philosophy. On the student’s Academic Plan, use the Modify Academic Plan wizard (MAP), selecting the Default packaging philosophy. Observe the Packaging Philosophy Override is set to the Default packaging philosophy. Find another affected student who uses the Alternative Packaging Philosophy. MAP the student and confirm the Plan Packaging Philosophy Override is set to the Alternative Packaging Philosophy. Change the Alternative Packaging Philosophy to Default Campus Default Philosophy and finish MAP. Refresh. Confirm the Academic Plan now displays the Packaging Philosophy: Alternative Packaging Philosophy.

Problem:
A couple students had many, multiple disbursement records created for Pell awards for FAY 2021-2022.

Cause:
Regent Award incorrectly assigned a 'Historic' flag to some enrollments. That caused duplicate terms and academic years creation on the Academic Plan screen. As a result, the duplicate terms were packaged with Pell that triggered the cancel-recreate process for the Pell disbursements. Regent Award also incorrectly distributed the Year-Round Pell (YRP) amounts between unpaid disbursements, and generated another new disbursement after the payment.

Fix:
The system logic was updated to assign and remove the Historic flag based on the program's start/end dates. The YRP Pell logic was also fixed for the distribution approach of amounts between unpaid disbursements.

Testing
Find an affected student. Run packaging. Confirm that the student’s Academic Plan structure does not have duplicate terms or duplicate Academic Years. Confirm no new disbursements are created on each subsequent packaging run.

Problem:
For some students with Manual Academic Years, Regent Award unexpectedly incorrectly processed the Academic Years (AYs) making them overlap and/or numbered out of order.

Cause:
Regent Award had incorrectly raised an exception when a term was moved from one Manual Academic Year to another Manual Academic Year during the Program Management Wizard (PMW).

Fix:
Regent Award is updated to ensure that the system will correctly process cases when a term is moved from one Manual AY to another Manual AY during the PMW.

Testing:
Find an affected student. Package the student. Confirm the Academic Plan displays the AYs in order. Confirm the AY dates do not overlap.

Problem:
Regent Award unexpectedly did not prorate loans for a Quarter Term Program undergraduate student when the final Academic Year had four terms, including the optional Summer header, and the student’s final enrollment was in the middle, Winter term.

Cause:
Regent used redundant verification resulting in a Direct Loan not being prorated.

Fix:
Regent Logic was updated to make sure loan amount proration is correctly applied to Quarter Term students.

Testing:
Find an affected student with a shortened Remaining Period of Study in their final Academic Year. Package them. Make sure Direct Loan amounts are prorated.

Problem:
Regent unexpectedly used negative Parent and Student Aggregated Gross Income or Income Earned from Work instead of zeroing them out resulting in incorrect EFC in ISIR Correction Wizard.

Cause:
Regent was not checking Parent and Student Aggregated Gross Income or Income Earned from Work values for negative values for EFC calculation.

Fix:
Regent logic was updated to make sure negative values could be used while 0 amounts will be used for EFC calculation.

Testing:
Open ISIR correction Wizard and set a negative number for any of these three values: Parent and Student Aggregated Gross Income or Income Earned from Work. Navigate to Wizard Step 2. Make sure EFC is calculated using 0 (zero) amount of updated values.

Problem:
Regent unexpectedly set a high disbursement number for Direct Loan disbursements resulting in COD Reject.

Cause:
Regent incorrectly canceled and recreated awards and disbursements due to the withdrawal from courses and enrolling again.

Fix:
Regent logic was updated to modify existing disbursements when student withdrew and re-enroll into courses.

Testing:
Find student with awarded with Direct Loan and withdrew from some of the courses in term. Package student. Add courses back and Package student. Make sure existing disbursements are updated instead of creation of a new ones.

Added from Dev 4/26/2022

Affected students will need to have a cleanup script https://regenteducation.atlassian.net/browse/RS-15586

Problem:
A data-cleanup script for Regent Award was not able to resolve some cases of duplicated Academic Years for SAY Programs/AYs that were caused by problematic past program data and program changes.

Cause:
Regent Award had a FAY and Crossover check that reassigned Federal Award Year IDs (FAIDs) when the Loan Period's FAY ID doesn't match the Award Period's FAY ID. However, the system did not apply the logic if the Loan Period was the default Loan Period.

Fix:
Regent Award is updated to remove the "is default Loan Period" check from the code that checked whether the Loan Period’s FAY in the FAID doesn't match the Award Period's FAY. Now, the system fixes the Loan Period's FAID even if it is on the default Loan Period.

Testing:
Find an affected student in the population from the script to resolve Duplicate AYs for SAY Program/AYs. Run the script. Package the student. Confirm the student is packaged successfully.

Problem:
Some students had packaging execution blocked by an error similar to, “Error validating plan for Student…The payment period on paid disbursement number [#] with fund and paid amount was moved from original pp (Removed Payment Period Id) to pp”

Cause:
Regent Award was not able to change the payment period identifiers for paid disbursements. That caused data duplication and triggered the blocking error during the packaging.

Fix:
The logic was updated to allow changing the payment period ID values for paid disbursements, as long as the term is the same.

Testing:
Find an affected student. Run packaging such as the Modify Academic Plan wizard (MAP). Make sure that no blocking errors occur at MAP wizard on all steps. Confirm the student’s Academic Plan contains only one instance of each term.

Problem:
In Term Setup, Programs sub-tab, Regent Award unexpectedly included Enrollment Level values from other Institutions in the Enrollment Level dropdown.

Cause:
Regent Award did not apply the filter to select Enrollment Level setup only from the Campus and Institution when populating records for Progam-Term editing.

Fix:
Regent Award is updated to ensure for the Program-Term editor, the Enrollment Levels now are displayed only for the ones from the Campus and Institution the Program belongs to.

Testing:
Test at a school with multiple Institutions. In Regent Award, Term Setup, open the Programs sub-tab. View the Enrollment Level dropdown for programs. Confirm the Enrollment Level values are specific to the Institution and Campus.

Problem:
A calculated R2T4 Refund Pell amount was not fully returned on the Export Student Transactions for Accounts Receivable (EST for AR).

Cause:
The application incorrectly updated the term award amount after finalizing an R2T4 with a Refund.

Fix:
The calculation approach during the R2T4 finalization process was fixed.

Testing:
Find an affected student with an R2T4 in Open status and a Refund result for a Pell Grant. Confirm the amounts in Step 10. Finalize the R2T4. Run packaging. Review the disbursement amounts on the term when R2T4 took place. The disbursement amounts should correspond to the Step 10 amounts of the R2T4 wizard.

Problem:
A student's Pell eligibility was not calculated correctly, and caused underawarding.

Cause:
Regent Award applied incorrect rounding rules combined with invalid handling of external Pell history usage during the eligibility calculation process.

Fix:
The awarding logic was updated to take into account the external Pell percentage used.

Testing:
Find a student who has an external Pell Award (at a non-Regent school) in the same FAY. Confirm the Pell percentage used. Package the student. Review the current FAY Pell amount. Edit the Pell in Modify Award Wizard. Confirm the remaining eligibility calculation in the FAY is taking into account the external Pell percentage used. For example, if the external Pell was used at 50%, Regent Award should still be able to package up to 50% of the regular Pell scheduled amount (and up to an additional 50% of YRP).

Problem:
Regent unexpectedly included attended courses' units withdrawn prior to the R2T4 Withdrawal Date (WDD) into the Recalculated Pell amount for R2T4 when R2T4 WDD is before Census.

Cause:
Regent incorrectly calculated the non-Census Enrollment level for the Recalculated R2T4 Pell amount.

Fix:
Regent was updated to ensure the Enrollment Level for Recalculated R2T4 Pell amount on a student who withdrew prior to or on Census date includes attended courses withdrawn on the WDD.

Testing:
In Regent create or find a term student enrolled in 3 courses (A, B, C). Post attendance on courses A and B only. Withdraw from all three courses, with the withdrawal date for course A prior to the R2T4 WDD, and course B and C withdrawal date = R2T4 WDD. Use the R2T4 WDD on or before the Census Date. Add R2T4 and make sure R2T4 Recalculated Pell amount is calculated according to Enrollment Level that is based on only the course B units.

Problem:
Regent Award unexpectedly didn't allow to create Fund Budget without Federal Award Year (FAY) selection for Funds that have Scope Academic Year (AY).

Cause:
Regent unexpectedly required FAY selection for Fund Budget when Fund Scope is AY.

Fix:
Regent UI logic was updated to make FAY selection is not needed for Fund Budget when Fund Scope is AY.

Testing:
Create Budget for a Fund that has Scope AY. Do not define FAY and Save Budget. Make sure Budget is saved without error.

Problem:
A student was underawarded Pell by $1 when packaged close to the Pell Lifetime Eligibility Usage (LEU) limits.

Cause:
The Pell calculation had an internal function that returned an invalid Pell LEU amount in some cases. The result caused underawarding when LEU approached the limit.

Fix:
The logic of the function was updated.

Testing:
In Regent Award, find a student who has a Pell LEU value of 599%. Package the student. Verify that after the packaging, the Pell is awarded up to the 600% LEU limit. Run the 'Pell LEU' Report. Make sure that none of the students have Pell LEU amounts over 600% after repackaging.

Problem:
Regent Award did not calculate eligible Pell amounts properly for some students in clock-hour programs.

Cause:
The application made an incorrect Pell Formula 4 nonterm Pell award calculation in a shortened remaining period of study (RPS) Academic Year. The miscalculation caused overawarding.

Fix:
The calculation logic was updated to eliminate the risk of overawarding Pell for clock-hour programs in a shortened RPS AY.

Testing:
Find an affected student enrolled in a clock-hour program and having a Pell award in a shortened RPS academic year. Run packaging. Verify that Pell amounts are correct for the shortened payment periods.