Title: Display the Award Accepted Date on the Awards Tab

Tickets: RS-12422; RS-13708; RS-13709; RS-13710;

Description:
Regent Award was enhanced to display the date that an award was accepted, whether by the student, by a Regent Award user, by the Import Awards process or by the system, on the Awards tab. This feature tracks only the initial acceptance of the award.

• If an award is created in Accepted Status by the system, the date the award was first created will display as the Accepted Date.
• If a User changes an award from Offered to Accepted via the Modify Award Wizard or Add Award Wizard the date of that occurrence will display as the Accepted Date.
• If the Import Awards process changes an award's status to Accepted, the date of that occurrence will display as the Accepted Date.
• If a student accepts an award via the Portal, the date of that occurrence will display as the Accepted Date.

If the accepted award is later canceled, the "Accepted Date," is still valid and will not be cleared.

Title: Include ISIR Reject Codes in Regent Award Document Assignment Configuration

Tickets: RS-13448; RS-13552; RS-13555; RS-13564; RS-13565; RS-13566;

Description:
Regent Award's Document Setup was enhanced by expanding the configuration options on the ISIR Assignment tab to include ISIR Reject Codes. Documents assigned in response to a specific ISIR Reject Code will auto-satisfy if a subsequent ISIR from the same FAY is received without that specific ISIR Reject Code. Documents configured to require BOTH a Reject Code(s) AND a Comment Code(s) for assignment will be auto-satisfied if either the Reject Code(s) OR the Comment Code(s) are cleared from a subsequent ISIR. If BOTH Reject and Comment Code requirements must be present to assign the document, clearance of one of them means both requirements are no longer present and the document is no longer Needed. For more information, please see the Administrator Guide topic Document Setup Data Elements.

In addition, the Customer Configuration Management (CCM) process was enhanced by updating the DocumentAssignmentISIR XML and CSV templates for the Import/Export Setup Configuration processes. For more information, please see the User Guide topic CCM User Guide Document Setup.

Title: Ohio College Opportunity Grant (OCOG) Disbursements

Tickets: RS-12950; RS-13583; RS-13584; RS-13585; RS-13586; RS-13588; RS-13451; RS-13587; RS-13596; RS-13598; RS-13614; RS-13788; RS-13780;

Description:
Regent Award was enhanced to automatically disburse eligible students with the Ohio (OH) College Opportunity Grant (OCOG) State Grant. In addition, the OCOG report was created.

For more information, please see the User Guide topic Ohio College Opportunity Grant (OCOG).

Title: Enhanced ISIR Print Format

Tickets: RS-11430; RS-13671; RS-13673; RS-13673;

Description:
Regent has enhanced the "Print ISIR" functionality. The "View Report" button on the ISIR tab was renamed to "Print ISIR". A new permission, "Print ISIR," was added under Student Permissions --> ISIR Tab to give users access to the "Print ISIR" button. If the user does not have the new permission, the button will not be visible on the ISIR tab. When the "Print ISIR" button is selected, a PDF document is rendered. This document was designed using the EDExpress specifications in the 2018-2019 EDE Technical Reference as a guide.

Note that the display of the SSNs in the printed report depends on the user's permissions. Only users with the "View full SSN via "View Full SSN" icon" or the "Full SSN always Unmasked" permissions enabled will be able to view and print the ISIR displaying the full SSN (for example "123456789"). Users with these permissions disabled will only view and print the ISIR displaying the last 4 digits of the SSN (for example "xxxxx6789").

Title: Allow the ability to make a subsequent ISIR Correction after the ISIR is set to a "Transmitted" status

Tickets: RS-13556; RS-13559; RS-13579; RS-13580;

Description:
Regent Award was enhanced by providing the user with the ability to make additional changes to the original data on the corrected ISIR transaction when the corrections to an ISIR have already been exported. On the ISIR tab, the "Start ISIR Verification/Correction Wizard" button is now enabled when the selected ISIR is in a "Transmitted" Correction Status. The subsequent export of this ISIR will contain changes to original ISIR data made after the original change export, i.e., the changes to the original ISIR data, not additions to the previously sent corrections. This means that if a user wants an entry made during a previous correction process to remain on the resulting ISIR, that correcting entry should be made again along with any new adjustments.

For more details, please see the User Guide topic How do I make corrections to an ISIR?.

Title: Applicant generated ISIRs are not made active Automatically post Verification

Tickets: RS-11592; RS-13432; RS-13553;

Description:
To ensure applicant changes to verified ISIRs are reviewed, Regent Award's Automatic Active ISIR Logic was updated to ensure that, once verification is completed, an applicant-generated ISIR will not automatically be made active.

If the existing Active ISIR for the Federal Award Year (FAY) is “Verified,” and the newly received ISIR Source of Correction is "Applicant," the newly received ISIR will not be made active automatically by Regent Award unless the newly received ISIR has a new Verification Tracking Group for the student for the FAY. Note that if there is a change to the Verification Tracking Group on an ISIR that is generated by the applicant, the ISIR will be made active and NOT inherit the prior verification status. This is current functionality.

If the school is using Regent Award's Inherited Verification functionality, and the inactive applicant generated ISIR is later made active manually by an end-user, the ISIR will inherit the verification status of the previous active ISIR, automatically (current functionality).

For more information, see the User Guide topic Automatic Active ISIR Logic

Title: Update to Automatic Active ISIR "Scenario 16" to actively validate that the incoming ISIR is not rejected

Ticket: RS-12448;

Description:
Regent Awards Automatic Active ISIR Logic looks at specific fields and values on the existing and newly received ISIR in order to determine if the newly received ISIR should automatically be set as the student's active ISIR for the Federal Award Year (FAY). The various scenarios are outlined in the User Guide topic Automatic Active ISIR Logic

In this documentation, there are cases where certain field/value combinations are irrelevant, meaning the field can have any value. Previously, "Scenario 16" was one in which it did not matter whether or not the newly received ISIR was rejected. With this enhancement, "Scenario 16" was updated to specifically check that the incoming ISIR is not rejected when determining whether or not the ISIR should be made active.

Title: Enhancement to the "Review Overaward with Unpaid Disbursements" Task

Tickets: RS-3621; RS-13578; RS-13581; RS-13582;

Description:
The "Review Overaward with Unpaid Disbursements" task trigger was enhanced to trigger once per loan period regardless of the value of the Task Status, unless the amount of the student's overaward for the loan period changes. If the amount of the overaward changes, a new task will be triggered. The amount of the student's unmet cost and unmet need were also added to the task detail.

Title: Auto-Task Escalation Process will not change manually edited Task Due date

Tickets: RS-13181;

Description:
Regent Awards Task Escalation Process was enhanced such that it will not modify the Task Due Date for a task where the Task Due Date was manually edited by a user.

For more information, see the Admin Guide topic on the Auto-Task Escalation Process.

Title: SSN UI Format

Tickets: RS-13342; RS-13525; RS-13528; RS-13529; RS-13531; RS-13536; RS-13538; RS-13540; RS-13541; RS-13543; RS-13544; RS-13545; RS-13546; RS-13547; RS-13548; RS-13549; RS-13550;

Description:
Regent Award was enhanced by standardizing the format of Social Security Numbers (SSNs) on every screen. The Summary, Student Details, ISIR, and COD tabs now display SSN in the following format depending on the user’s permission:

• Masked: “xxxxx6789”
• Unmasked: “123456789”

In addition, the following reports now use the same formatting rules for SSN:

• COD – Failed Export Validation Checks
• ISIR - Corrections
• ISIR - Student Listing
• ISIR - Unmatched
• Loan Status Confirmation
• Student - Batch Load
• Student - SIS And ISIR Discrepancies
• System - SBL Validation Errors
• Rebuild - Unmatched Students
• WI State Grant
• Import Wisconsin State Grant Process Results
• OH State Grant

Title: Improvements to Student Quick Search

Tickets: 13037;

Description:
Improvements were made to "Quick Search" feature in Regent Award (available from the upper right corner of the screen). Prior to these improvements, the "Quick Search" feature occasionally presented students from a previous search result if the user pasted the student ID into the search box and then quickly pressed the 'Enter' key. Improvements were made to the user action processing logic for the "Quick Search" to ensure that only the entered student ID is returned.

Problem: 
Manual awards were added to a student via the Add Award Wizard (AAW) in an "Offered" or "Estimated" status, and the Manual flag was properly set on the award. Then when a user Accepted the award via the Modify Award Wizard (MAW), the Manual flag was removed from the award.

Cause:
The MAW incorrectly identified the Manual awards as awards that needed re-evaluation, thus clearing the Manual flag from the award.

Fix:
Manual awards will remain Manual when modified via Modify Award Wizard.

Testing:
Add a Manual award for a student via the AAW in an "Offered" or "Estimated" status. Once the award has been added access the MAW and "Accept" the award. Confirm the award is still marked as Manual.

Problem: 
Regent Award calculated incorrect Anticipated Units and prorated loan amounts for some undergraduate nonterm students. The students were in a shortened final Remaining Period of Study (RPS) Academic Year (AY).

Cause: 
The school had previously provided manual anticipated units for the RPS, which were being used by Regent Award when packaging. The school had no way of clearing or resetting the manually provided anticipated units value for the payment period, so Regent Award always used that value when packaging the student. The "Reset Anticipated Units" button on the Advanced Packaging screen (within the Modify Award Wizard) was taking no action to clear the manually provided anticipated units unless the student had registered units for the enrollment.

Fix: 
The "Reset Anticipated Units" button logic was updated to allow the user to reset the anticipated units regardless of whether or not the student has registered units on the enrollment.

Testing: 
Navigate to an affected nonterm undergraduate student who has a current Direct Subsidized or Unsubsidized Loan in a shortened RPS final AY. Use the "Reset Anticipated Units" button on the Advanced Packaging screen (within the Modify Award Wizard) to clear the previously entered manual anticipated units. Repackage the student. Refresh the Academic Plan screen. Examine the anticipated units in the final Academic Year. The Anticipated units should match the needed units at the start of the student's final AY.

Problem: 
A user added attended units to a student using a payment period course adjustment. The Academic Plan unexpectedly failed to show the update to the attended units. Once the student was exported for EST, Regent Award displayed a validation error of EST-0041 (Disbursement schedule requires attendance, but there is no attendance in payment period.)

Cause: 
Regent Award was incorrectly using Attempted Program Applicable Units instead of Attended Program Applicable Units to display and calculate attendance in the payment period.

Fix: 
The Regent Award logic has been modified to use the Attended Program Applicable Units for EST validation.

Testing: 
Navigate to a term student who does not currently have attendance in the term and has a disbursement schedule configured to require attendance. Add a payment-period level course adjustment, with positive program applicable attended units. Package the student via the Modify Award Wizard (MAW). Refresh the Academic Plan screen. The Academic Plan should show the changed amount of "Atten" units. Run Export Student Transactions (EST) for the student's awards in the term. The disbursements should successfully export without displaying the EST-0041 validation error.

Problem: 
For some nonterm students close to their NSLDS aggregate loan limits, Regent Award calculated incorrect award amounts that were twice the expected eligible amounts.

Cause: 
The problem was caused by wrong Loan Aggregate balances update for closed/past awards disbursements. As a consequence, Loan Aggregate balances were exceeded.

Fix: 
The award logic calculation was updated to ensure that Regent Award did not allow awarding limits to be exceeded for active/future awards.

Testing: 
Navigate to an affected nonterm student who has aggregate loan amounts close to the maximum aggregate limits. Edit the student's loans in the Modify Award Wizard (MAW). Examine the Calculated Eligibility amounts. The eligible amount for each loan should not cause the student's loans to exceed the aggregate total limits.

Problem: 
A student was close to 600% Pell Lifetime Eligibility Usage (LEU) limits. Regent Award awarded a Pell amount $1 more than expected. The dollar difference put the student over the 600% Pell limits.

Cause: 
Regent Award unexpectedly rounded up instead of truncating or rounding down the final Pell disbursement.

Fix: 
The Regent Award logic has been modified to check for amounts exceeding LEU limits. If the amount would exceed 600.000%, the system will truncate or round down the amount to the nearest dollar or penny, as configured in the Fund Setup.

Testing: 
Navigate to an affected Pell-eligible student who is close to their Pell LEU limit. Package the student via Modify Academic Plan (MAP). Refresh the student and confirm the final total Pell amount does not exceed 600.000%.

Problem: 
In some cases, the Modify Award Wizard (MAW) did not include loan periods for all terms/ payment periods in an Academic Year (AY) when attempting to update the award amounts.

Cause: 
The award was initially assigned to a loan period not covering all terms/ payment periods preventing the user from adjusting disbursement amounts.

Fix: 
Regent Award logic has been modified to verify the assignment of the awards to the loan period, edit the disbursement amounts, and include all valid terms/payment periods when utilizing the MAW.

Testing: 
Navigate to an affected student. Package the student via the Modify Academic Plan (MAP) and refresh. Go to Awards Tab and modify the loans for AY the student is currently attending. Enter an Accepted Amount and select the Override eligibility checkbox. Proceed to the Step 2. Ensure that MAW displays the appropriate terms/ payment periods for the AY and that the Amount field for all payment periods are available to update.

Problem: 
A school configured a Task to restrict packaging for a specific fund, Federal Pell Grant. A student had that Task and a Federal Unsubsidized Loan. When the school tried to export the loan to COD, the system unexpectedly prevented the loan from exporting.

Cause: 
When the COD Export process checked for Task restrictions, it incorrectly applied the restrictions to all funds instead of just the funds configured on the Task Setup.

Fix: 
The COD Export process was corrected to consider the specific configured funds when checking for Task restrictions.

Testing: 
Configure or use a Task to restrict packaging and positive disbursements for only a specific COD-related fund. Navigate to a student who has that fund and other COD-related awards. Confirm that the Task is the only packaging blocker. Export to COD for that student, choosing all the student's awards. The other awards should export successfully. The restricted fund should not export. The student's Activity Log should show an error that the restricted fund failed to export due to the open task.

Problem: 
When disbursements were released directly on COD and the COD Web Response (WB) files imported, to update the disbursement status, Regent Award failed to recognize the loan had been paid. When the students were packaged after the October 1 loan fee change, Regent Award unexpectedly cancelled and recreated the loans with a new Loan Origination Fee. The original paid disbursements were unexpectedly marked as unpaid (DRI=false) and zeroed out.

Cause: 
Regent Award had unexpectedly cancelled & recreated payed loans were the Federal Award ID and Federal Award year did not match.

Fix: 
An update was made to the Regent Award logic so that paid loans are not canceled in the event of a new Federal Award Year with updated fees.

Testing: 
In order to test this update, you must have access to a Time Machine environment and cCOD WB files. Set the server date to before October 1. On a test student with a scheduled disbursement, mark the disbursement as paid by importing a COD WB data file. Package the student via the Modify Award Wizard (MAW) and refresh the student. Change the server date to a date after the October 1 loan fee change. Package the student again via MAW and refresh the student. Regent Award should keep the original loan intact with its original Loan Origination Fee. The paid disbursements should still be marked "Paid" at the original amounts.

Problem: 
In Fund Setup, on the General tab, when an Administrator edited a Federal fund and saved the changes, the screen showed unexpected errors such as "The value 'null' is not valid."

Cause: 
Regent Award did not correctly populate and save empty values for Positive/Negative Cease Date fields in the Cease Disbursement settings section.

Fix: 
System checks were updated to allow empty values for Cease Disbursement settings.

Testing: 
Navigate to Administration, Fund Setup. Filter for funds with a source of Federal. Make an edit to one of the Federal funds and Save. The changes should save without error.

Problem: 
The ISIR Dataview was missing information related to Identity Verification Results.

Cause: 
A Dataview that surfaces the data from the StudentIdentityHighSchoolVerificationResult table was missing.

Fix: 
The new view titled dataExtract_StudentIdentityHighSchoolVerificationResult_View_v001 was created.

Testing: 
Ensure that Code, Identity / High School Verification Results, Verification Tracking Group Number, Student is Active?, Days Since Verification Documents Assigned, Student Exported, and Export Date are available on the ISIR Dataview.

Problem: 
A school set an ISIR to "Package Using Corrected active ISIR, not transmitted." When the school tried to pay the disbursement via the Export Student Transactions (EST) for DRI process, Regent Award presented an unexpected error: EST-0009, Award is blocked due to ISIR correction had been exported and no response has been received. A fund can be paid via EST when the school chooses “Package using Corrected ISIR, not transmitted” if the fund's configuration for "ISIR Correction Response is Required for Disbursements" is False or not checked. Otherwise, a corrected ISIR must be received in order to pay the fund via EST.

Cause:
Incorrect validation prevented the disbursement from being verified as valid for the EST process.

Fix:
The validation logic was corrected to allow a student to be packaged and disbursed using a corrected active ISIR that was not transmitted.

Testing: 
Navigate to an affected student with an ISIR set to "“Package Using Corrected active ISIR, not transmitted" in the ISIR Verification / Correction Wizard. Package the student. Run the EST process for the appropriate fund/payment period. The disbursement should export successfully.

Problem: 
After making changes in ISIR Verification/Correction Wizard (fields 26 and 29) changes were not reflected in Step 2 of the ISIR Verification/Correction Wizard.

Cause:
The issue was caused by a code change that had been applied to the ISIR Verification/Correction Wizard to correct a previous issue to separate Dependent and Independent student questions.

Fix:
A code change has been applied to the ISIR Verification/Correction Wizard to reflect changes in the ISIR Verification/Correction Wizard Step 2.

Testing:
Navigate to the ISIR Verification/Correction Wizard and enter corrected values in fields 26 and 29. Ensure the changes are displayed. Proceed to Step 2 and confirm the changes are reflected as Previous and New values.

Problem:
When using the Institution Setup option "Package to the Net Loan Amount for Direct Costs," some students were unexpectedly packaged with Direct Unsubsidized Loan awards for a portion of the Direct Subsidized Loan fees.

Cause:
When determining the fees for "Package to Net" calculations, the system was using fees from an incorrect payment period, and in some cases, the fees could not be found.

Fix:
The system was corrected to ensure that the correct payment period is used when determining fees and creating estimated scheduled disbursements.

Testing:
Re-package an affected student. The Direct Unsubsidized Loan award should be cancelled and the Direct Subsidized Loan fees included in the amount of the Direct Subsidized Loan award.

Problem: 
Some manual Academic Years had duplicated loan period dates. When the extra loan periods were removed via a cleanup script, the packaging process unexpectedly recreated the duplicated loan periods.

Cause: 
When Regent Award packaged multiple user-defined loan periods, the system did not consider the ordering of the manual loan periods in sequence. As a result, sometimes the system created extra loan periods when none were needed. In addition, when a user-defined loan period matched the "default" year-long loan period dates, the system did not reassign awards' loan periods to the "default" loan period.

Fix: 
Regent Award now has improved logic for sequencing manual loan periods, and for managing year-long loan periods. The priority order changed for packaging manual loan periods. When Regent Award packages user-defined manual Loan Periods, the system first looks for loan periods that are used in packaging. Then, Regent Award considers whether additional loan periods are on the default loan period. Finally, the loan periods are ordered by internal database ID. Additional logic improved handling of year-long loan periods. If a loan period's dates and FAY all match the year-long default loan period, and the loan period is not already linked to a user-defined manual loan period, then the system links the loan period to the default loan period.

Testing: 
Run the data-cleanup script, if necessary. Navigate to an affected student who has duplicated loan periods in a Manual Academic Year. Package the student. Open the Program Management Wizard (PMW) and edit the Manual AY. Examine the Loan Periods. Each loan period should be unique, with a different set of dates and/or different Federal Award Year. Confirm no duplicates loan periods appear.

Problem: 
The current award amount of a rebuild award could not be updated via the Modify Award Wizard (MAW).

Cause: 
Regent Award unexpectedly recalculated the Accepted Amount value for rebuild awards being adjusted via MAW.

Fix: 
A condition was added to prevent Regent Award from automatically recalculating the Accepted Amount of rebuild awards being manually adjusted by the end user via MAW.

Testing: 
Navigate to an affected student. Edit a rebuild award via the Modify Award Wizard. Select the Override Eligibility checkbox. Verify the original award amount. Adjust the New Offer and Accepted Amount fields. Proceed to Step 2. Verify that the Adjusted Total field was updated with the same amounts that were entered on Step 1. Return back to the Step 1 to verify that the edited Accepted Amount is not reverted back to the original value.

Problem: 
Incorrect Calculated Eligibility amount displaying for the 2018-2019 Pell Federal Award Year (FAY) in the Modify Award Wizard (MAW.)

Cause: 
Regent Award miscalculated Pell eligibility when the award amount was manually updated with a lower eligible amount.

Fix: 
When calculating Pell eligibility, Regent Award now considers the fully eligible payment period amounts rather than the manual values.

Testing: 
Navigate to an affected student who has Pell eligibility and full-time enrolled terms in FAY 2018-2019. Package the student via Modify Academic Plan (MAP) and refresh. Access MAW. Confirm the calculated eligibility displays the 2018-2019 Pell FAY.

Problem: 
A cancel/recreate error message was displayed in Regent Award when attempting to cancel a manual award in "Offered" status via the Modify Award Wizard (MAW).

Cause: 
Regent Award did not accurately maintain the cancel and recreated flag on the manual award and prevented the award from updating to a "Cancelled" status.

Fix: 
The Regent Award cancel/ recreate logic modified to remove the incorrect flag.

Testing: 
Locate a student who has a manual loan awards in "Offered" status. Edit the manual loan award via MAW and adjust both the New offer and Accepted amounts. Proceed to Step 2 of the MAW and ensure the error does not display. Navigate to the Academic Plan tab and repackage the student via Modify Academic Plan. Ensure the student's Academic Plan and manual award has been updated. Return back to the Awards Tab and Step 1 of the MAW. Change the manual award status to "Cancelled". Proceed to Step 2 of the MAW and confirm the error does not display.

Problem: 
The Add Award Wizard (AAW) and Modify Academic Plan (MAP) unexpectedly displayed an error : Failed to Process. Error Msg: Award Period with duplicate key found on attempt to add award/package a student

Cause: 
Duplicated award periods were created for an Academic Year #0 when import awards process was performed for a student.

Fix: 
Regent Award logic was modified to merge duplicated Award Periods for Academic Year #0 when the Batch Package Process or MAP are run.

Testing: 
Navigate to an affected student. Package the student via MAP. Ensure the errors does not display. Refresh the student. Proceed to the AAW and add an award. Choose a fund and payment period. Click 'Proceed'. Ensure the no error does not display.

Problem: 
Regent Award unexpectedly did not create a student's Pell award. The student had used 100% of that FAY's regular Pell at a different institution, but was eligible for additional, Year-Round Pell (YRP) funding.

Cause: 
The system was awarding YRP funding by adding onto to existing Pell awards. Because the student did not have any regular Pell eligibility, the system did not create the initial, normal Pell award. The Year-Round Pell could not be added on to the missing Pell award.

Fix: 
When Regent Award checks for Year-Round Pell funding, and finds nonzero YRP eligibility, the system will create a new Pell award if the student does not have any existing Pell award for that FAY.

Testing: 
Navigate to an affected student who has used 100% Pell at a different institution for the current Federal Award Year, and who has some remaining 150% Pell eligibility. Package the student, such as with the Modify Academic Plan wizard. Regent Award should create the Pell award for the eligible payment period. The amounts for all institutions should not exceed 150% of the total Pell eligibility for that FAY.

Problem: 
Regent Award unexpectedly awarded a student 2017-2018 Pell at 200% of the annual limit. The 150% disbursements were missing the Year Round Pell (YRP) indicator.

Cause:
This issue was caused when a Pell award with more than 100% on the rebuild/import is loaded, Regent Award did not correctly determine the YRP disbursements when looping over the payment periods in the Federal Award Year (FAY).

Fix: 
The Regent Award logic was modified to sett the YRP flag to True on the subsequent disbursements for instances where 100% of normal Pell is met.

Testing: 
Navigate to an affected student who is eligible for 150% Pell, and who has a COD Rebuild Pell award in an AY#0. Package the student via Modify Academic Plan (MAP) and refresh the student. Review the Pell amounts on the Academic Plan. The Pell should only be awarded up to 150% of the annual Pell limit. The later, 150% disbursements should be marked as "YRP" in the Disbursement Details. If the Pell eligibility reached 150% before the crossover payment period, and the crossover payment period is set to exhaust the current year, then any Pell in the crossover PP should be from the next FAY.

Problem:
When the configuration item "Auto-Cancel Excluded Title IV Disbursements for R2T4" was set to a value of "Yes," and an R2T4 reversal was performed, the student's loans did not reverse correctly.

Cause:
When "Auto-Cancel Excluded Title IV Disbursements for R2T4" is set to "Yes," Regent Award should automatically cancel Title IV disbursements (except FWS) in the R2T4 period that were excluded from the R2T4 calculation. However, when finalizing the R2T4, the system was not checking whether the disbursement was already reduced by the R2T4 calculation, so it was canceling the disbursement completely rather than leaving it at the R2T4 calculated amount. This impacted reversals because the system then did not have the correct award data to restore the canceled disbursements.

Fix:
A check was added so that when "Auto-Cancel Excluded Title IV Disbursements for R2T4" is on, the system will only cancel the disbursement fully if it was not included in the R2T4 calculation itself.

Testing:
Ensure that "Auto-Cancel Excluded Title IV Disbursements for R2T4" is set to a value of "Yes" and that your student has some Title IV funds that should be excluded from the R2T4 calculation. Perform the R2T4 and Finalize the wizard. Package and run EST to ensure that 1) awards included in the R2T4 calculation are reduced in accordance with the wizard calculations and 2) awards excluded from the R2T4 calculation are canceled. Then perform an R2T4 Reversal and Finalize the wizard. Ensure that all of the student's awards are replaced in the proper amounts according to the academic plan prior to the original R2T4 calculation.

Problem: 
When the configuration item "Auto-Cancel Excluded Title IV Disbursements for R2T4" was set to a value of "Yes," and an R2T4 was finalized, Pell disbursements that included in the payment period as a Post Withdrawal Disbursement were canceled.

Cause: 
When "Auto-Cancel Excluded Title IV Disbursements for R2T4" is set to "Yes," Regent Award should automatically cancel Title IV disbursements (except FWS) in the R2T4 period that were excluded from the R2T4 calculation. However, when finalizing the R2T4, the system was not checking whether the disbursement was already reduced by the R2T4 calculation, so it was canceling the disbursement completely rather than leaving it at the R2T4 calculated amount.

Fix: 
A check was added so that when "Auto-Cancel Excluded Title IV Disbursements for R2T4" is on, the system will only cancel the disbursement fully if it was not included in the R2T4 calculation itself.

Testing: 
Ensure that "Auto-Cancel Excluded Title IV Disbursements for R2T4" is set to a value of "Yes" and that your student has scheduled Pell disbursements will result in a PWD. Perform the R2T4 and verify the PWD amount . Finalize the R2T4 wizard. Package the student via MAP and run EST to ensure that awards included in the R2T4 calculation are reduced or maintained in accordance with the wizard PWD calculations.

Problem: 
A Not Substantially Equal (NSE) program change resulted in the removal of a previously active program in Regent Award.

Cause: 
During the program change process Regent Award used the enrollments associated to previously active programs.

Fix: 
Regent Award logic has been modified to add a code condition that uses the correct enrollments for a new program when a program change is performed.

Testing: 
Load a SBL file with Program A information to create a student. Package the student via Modify Academic Plan (MAP) and refresh the student. Load the SBL file with Program B information. Package the student via MAP and refresh the student. Perform a NSE program change. Load the SBL file with Program C information. Now Program C will be active. Package the student via MAP and refresh the student. Import the SBL file with courses for Program C. Package the student via MAP and refresh the student. Confirm that Program A remains intact on the Academic Plan.

Problem:
In release 4.4.0.0 of Regent Award, an enhancement was introduced that would allow the user to see the same "blocking" messages in all of the Regent Award wizards that are shown in the Modify Academic Plan Wizard (MAP). However, this messaging was incorrectly blocking the use of the R2T4 Wizard when the student had an open R2T4 task.

Cause:
The implementation of the above-mentioned enhancement fully blocked the ability to perform an R2T4, when a student had an open R2T4 task, instead of just displaying additional messaging to the user.

Fix:
The enhancement code was removed from the R2T4 Wizard in order to allow the user to perform R2T4s within Regent Award. The enhancement will be re-visited in a future release.

Testing:
Open a student with an R2T4 task in an "Open" status. Navigate to the R2T4 Wizard. Verify that the R2T4 grid and worksheet are available for completing the R2T4 calculations.

Problem: 
After an R2T4 Reversal, a Pell disbursement was incorrectly reduced, and broken out into additional disbursements to recoup the reduced amount.

Cause: 
The award amounts were incorrectly distributed between all existing disbursements after the R2T4 reversal process.

Fix: 
The logic was updated to distribute the new amounts between unpaid disbursements only, and to leave the paid disbursements in place and unchanged.

Testing: 
Reverse a finalized R2T4. Navigate to the Academic Plan and verify that the existing paid Pell disbursement amounts are not reduced (duplicated or split).

Problem: 
An eligible Direct Loan Post Withdrawal Disbursement (PWD) amount included the gross amount of the disbursement rather than the net on the Academic Plan. Therefore, the student student was overawarded.

Cause: 
Regent award incorrectly added Net PWD amount of $1 from Inadvertent Overpayment to Gross PWD amount.

Fix: 
The Regent Award code was fixed to avoid overawarding.

Testing: 
Execute the R2T4 wizard where the results contain a PWD. Verify the Net PWD amount and accept the PWD on the PWD worksheet. Finalize the R2T4. Package and run the EST for AR. Review the disbursement details for the paid award on the Academic Plan. The student should be paid with Net amount of PWD.

Problem: 
The "Student - Completed Units" report was unexpectedly not including transfer units in the "PA Completed" unit count.

Cause: 
Regent Award applied the incorrect logic when counting completed units for the report output.

Fix: 
The units calculation approach was updated for the "Student - Completed Units" report.

Testing: 
Run the 'Student - Completed Units' report. Check the output against the Academic Plan units for a student who has transfer units. The report should include the program applicable transfer units in the report output as "PA Completed" units.

Problem:
The COD Award Disbursement Report is unexpectedly not returning data when a specific term is selected in the parameter criteria.

Cause: 
The COD file xml schema was disrupted by previous changes.

Fix: 
The data source was updated to use correct COD xml schema.

Testing: 
From the Standard Reports option, choose the COD Award Disbursement Report. Select a specific term from the drop down parameter criteria. Ensure that the report is returning the appropriate data.

Problem:
The EFC column was missing from the SNAP CSV Report.

Cause:
The Regent Award Database lookup had returned a NULL value therefore the values were skipped in the report output logic.

Fix:
The Regent Award Database procedure was updated to return an empty string instead of NULL values.

Testing: 
Submit three applications via SNAP and update one to "Started", one to "In Progress" and one as "Completed". Run the SNAP CSV Report. Ensure the EFC column is present and that the data appears in the respective column.

Problem: 
Manual award modification in Step 1 of the Modify Award Wizard (MAW) was blocked by a non previously existing "Review Eligibility Change" task.

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 this 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: 
Confirm that no tasks are in an "Open" status for the student. Package the student via the Modified Academic Plan (MAP). Refresh and close any new tasks. Verify that all documents are in 'Satisfied' status. Navigate to the Awards tab and create a manual award for the student via MAW. Confirm no errors display in Step 1 of the process and finish the process. Navigate back to the the Academic Plan tab and MAP the student again. Refresh the student. Ensure the Academic Plan accurately reflects the manual award.