Problem:
Regent Award was not accurately displaying "Watched Students" on the dashboard under the "Recent Activity - Watched Students" section after logging out of the User Interface and logging back in. The Dashboard displayed recent activity for all students, not just the students on the user’s Watch List.

Cause:
Invalid filtering was occurring which prevented "Watched Students" from displaying on the "Recent Activity - Watched Students" section on the dashboard.

Fix:
Logic was modified to ensure that any Watched Students are displayed on the dashboard under the "Recent Activity - Watched Students" section. The Dashboard refreshes the Watched Students activity whenever the user logs into the system.

Testing:
Navigate to a student record and select the "Add to Student Watch List" button. Log out of the Regent Award UI and log back in. Ensure the student selected is now visible under the "Recent Activity - Watched Students" widget on the dashboard.

Problem:
Regent Award was not correctly calculating student's grade level after completing a Program Change.

Cause:
Grade levels were not calculating for historic programs when a Program Change occurred on a student's Academic Plan.

Fix:
Regent Award logic was modified to ensure that grade levels are calculated for enrollments that are associated with historic programs.

Testing:
Navigate to a student needing a Program Change and the Grade Level for the prior program was at least a Grade Level 2. Process the Program Change and ensure the Grade Level in the new program is accurately reflected.

Problem:
Regent Award is unexpectedly presenting an error when users attempt to create a Disbursement Schedule.

Cause:
Incorrect logic within the database was causing Regent Award to present an error when a user attempting to create a new Disbursement Schedule.

Fix:
A variable within the database was updated to ensure new Disbursement Schedules are able to be created without an error being presented.

Testing:
Navigate to Administration and select Disbursement Schedule Setup. Select "Add Disbursement Schedule" and ensure an error is not presented.

Problem: 
Program Setup, "Default Academic Calendar/Period/Unit" section, Regent Award unexpectedly updated three setup parameters. The screen set them as if a user selected the first option in three drop-downs when Inherit from Campus" checkbox was not selected, and a user Edited and Saved Program Setup configuration without making any changes.

Cause: 
The screen set the "Inherit from Campus" checkbox to the default value.

Fix: 
The code was corrected to not change the value.

Testing: 
Find a Program where Default Academic Calendar/Period/Unit setting has Inherit from Campus checkbox unselected. Edit Program Setup configuration for this Program, do not make any changes, Save configuration. Refresh. Make sure that parameters in Default Academic Calendar/Period/Unit section remain unchanged.

Problem:
Regent Award was throwing an "internal server error" when attempting to remove users from a role after all users within the configuration were assigned to the same role.

Cause:
A command time out issue was causing the "internal server error" to be presented when removing all users from a role.

Fix:
Logic was enhanced to load user data quickly to prevent an "internal server error" when removing all users from a role.

Testing:
Navigate to the roles configuration section under the Administration Tab. Select a role and navigate to the "Users" tab. Select "edit", select "add all", and then save. Select "edit" once more and attempt to remove several users from the role. Confirm that an "internal server error" does not occur.

Problem: 
Documents grid was not showing the correct amount of assigned documents.

Cause: 
Regent Award validation rules prevented the upload of files containing special symbols in the file name.

Fix: 
System validation for special symbols in file names was removed.

Testing: 
Select the affected student. Navigate to Documents tab. Click 'Add document' button. Choose 'Select Document Requirement' link. From 'Submitted Documents' select a file with special characters present in the file name. Click the Save button. Confirm that file name containing special symbols is successfully uploaded. Verify that the Documents grid shows all documents assigned to the student.

Problem: 
A term unexpectedly contains Registered Units from a moved course. Originally it had only one course and a user had moved this course to another term.

Cause: 
Regent Award unexpectedly did not delete the enrollment when a user was moving the last course from a term, keeping the same external course ID for that course in the term to which the course is moved.

Fix: 
Regent Award logic was updated so now it deletes orphaned terms.

Testing: 
Find a term student with only one course in the term. Update the student with SBL moving this course to current or future term keeping the same external course ID. Package the student. Refresh. Make sure registered units are zeroed out in the original term.

Problem:
The Federal Supplemental Grant (FSEOG) Offered, Accepted, and Budgeted amounts were not updating under the Fund's Budget Setup when a student's Return to Title IV (R2T4) resulted in a refund of the FSEOG fund.

Cause:
When an R2T4 was processed for a student and a refund of the FSEOG fund was required, Regent Award was not recalculating the Offered, Accepted, and Budgeted amounts under Budget Setup.

Fix:
Logic was modified to ensure that the Offered, Accepted, and Budgeted amounts for the FSEOG fund budget are recalculated when a student's R2T4 results in a refund of the FSEOG fund.

Testing: 
View the Budget Setup for a budgeted FSEOG fund. Navigate to a student needing a refund of the FSEOG fund due to a finalized R2T4. After packaging the student, navigate to the FSEOG Budget Setup under Configuration and ensure the "Offered", "Accepted", and "Budget" amounts are updated to reflect the award change from the student's finalized R2T4.

Problem: 
Check boxes at Compare Details section of Compare ISIR Wizard did not filter out results when checked/unchecked.

Cause: 
JavaScript code selected the wrong HTML element, thus 'Only Show Differences' checkbox was not selected.

Fix: 
The code was updated to target the correct checkbox element at Compare ISIR Wizard.

Testing: 
Navigate to ISIR tab. Click on the 'Compare ISIRs' button. Click on the lines for two ISIRs to compare. Under the 'Compare Details', check 'Only show differences' checkbox. The screen shows only the difference between the selected ISIRs.

Problem:
Users were unable to complete the ISIR Verification Wizard in Regent Award for students whose birthdate fell on February 29th.

Cause:
Incorrect validation was in place related to birthdates that fall on February 29th.

Fix:
Validation logic was corrected to ensure that a birthdate of February 29th can be entered in the ISIR Verification Wizard.

Testing:
Navigate to an ISIR that has been selected for verification. Select the "Start ISIR Verification/Correction Wizard" button. Enter a DOB of 02/29/YYYY within ISIR Field #9 and select "Continue". Ensure the ability to provide a DOB of 02/29 is present and the ISIR Verification Wizard can be completed without receiving a validation error.

Problem:
Fields on the ISIR Printout produced by Regent Award did not match those within the User Interface on the ISIR Tab.

Cause:
Invalid logic was in place that caused the printout view of the ISIR to not match the data presented within the UI.

Fix: 
Mapping of the printout fields was resolved to ensure the ISIR printout matches the data within the UI for the following fields:

• Field 3 - Original Name ID
• Field 109 - Parents' U.S. Income Tax Paid
• Field 152 - Federal School Code #6 Housing Plans
• Field 165 - Preparer's Social Security Number
• Field 173 - Transaction Data Source/Type Code
• Field 179 - Student Asset Threshold Exceeded
• Field 184 - Student IRS Display Flag
• Field 185 - Parent IRS Display Flag
• Field 186 - Student IRS Type of Tax Return Data Field Flag
• Field 196 - Parent IRS Type of Tax Return Data Field Flag

Testing:
Navigate to a student record and select the ISIR Tab. Select the Print ISIR button and ensure the output provided matches the data in the UI.

Problem: 
Regent Award was unexpectedly throwing an error message stating "sorry, an error occurred while processing your request" when attempting to select the "print ISIR" button.

Cause: 
An error was found in the HTML that provides the ability to print an ISIR.

Fix: 
The HTML error was resolved to allow users to print an ISIR.

Testing: 
Navigate to the ISIR tab for a student. Select the "print ISIR" button and confirm an error message is not provided stating "sorry, an error occurred while processing your request."

Problem: 
Newly imported students (without an Academic Plan populated) were receiving an error message stating disbursements were less than $0.

Cause: 
Previous logic allowed negative numbers to be included in award calculations, thus causing the error message reported.

Fix: 
Logic was modified to ensure negative numbers are not included in the award calculation; rather, the award calculation would include a $0 amount.

Testing: 
Import new students via the SBL. Package the students via Modify Academic Plan wizard. Ensure an Academic Plan is created with no error message presented.

Problem:
Advanced Packaging within Regent Award was not adhering to the setting of packaging with the Latter Federal Award Year (FAY).

Cause:
Regent Award was incorrectly setting the Pell Grant eligibility for a nonterm crossover payment period, thus preventing the Latter Year setting to take effect within Advanced Packaging.

Fix:
Logic was modified to ensure that the Latter Year setting within Advanced Packaging is respected when there is a crossover nonterm payment period.

Testing:
Navigate to a student that has a crossover non-term payment period for the 18/19 and 19/20 FAYs. Ensure the student does not have an 18/19 ISIR but does have a 19/20 ISIR. Under Advanced Packaging, select the Latter Year setting option for the crossover payment period and complete packaging. Ensure Pell is packaged using the Latter Year ISIR for the payment period.

Problem: 
Regent Award unexpectedly re-packaged a reduced Pell amount using Pell Lifetime Eligibility Usage (LEU) value from COD Standard Response file, while this value already includes previously paid disbursements from the same payment period.

Cause: 
Regent Award incorrectly used the Pell LEU from a COD response file and adjusted the total eligible amount, reducing the award amount.

Fix: 
Regent Award logic is updated to exclude the paid amount when the award is adjusted by the Pell LEU from COD response.

Testing: 
Navigate to a student whose remaining Pell LEU is more than 525%. Package student for the current payment period with full Pell eligibility and two 25% disbursements. Pay the first disbursement. Export EST to DRI, EST to COD, Import COD Standard response file. Verify COD Pell LEU from the response, it should be increased by 25%. Package student and make sure second unpaid disbursement is not reduced.

Problem: 
Regent Award was inadvertently decreasing anticipated units by half within Advanced Packaging for clock hour programs.

Cause: 
Regent Award was incorrectly calculating anticipated units when one Academic Year had manual course units associated and another Academic Year had no course units associated.

Fix: 
Logic was modified to ensure anticipated units are calculated correctly within Advanced Packaging for clock hour programs.

Testing: 
Navigate to an affected student in a clock hour program. Access Modify Academic Plan wizard, Advanced Packaging and ensure the anticipated units are reflected correctly.

Problem:
Regent Award was inadvertently cloning IOProcess data when triggering scheduled Batch Packaging (BP) runs.

Cause:
The scheduled process record was not set up to run correctly when a scheduled Batch Packaging process was triggered.

Fix:
The scheduled process record is set up to run when a scheduled Batch Packaging process is triggered via the scheduled jobs.

Testing:
Schedule a BP job under the Scheduled Processes tab. Once the BP job is kicked off, ensure that the process is shown in the Process Log.

Problem:
Performance and deadlock issues were occurring in Regent Award causing slower than normal processing times.

Cause:
Deadlocks were occurring within the database causing performance issues for users within the User Interface.

Fix:
Updates were made to the database tables to allow for faster processing within the Regent Award User Interface.

Testing:
Have multiple users available to test simultaneously. One user should work through the Program Management Wizard for a student. Another user should add a student break and another user should update a course using Course Overrides. All of these processes should be worked at the same time and confirm that deadlock and performance issues do not occur.

Problem:
Regent Award was incorrectly processing Federal Pell Grants on the Export Student Transaction (EST) Process for students who were not currently in attendance. (Please see Confirm Current Attendance Prior to Disbursement)

Cause:
Previous Regent Award logic allowed COD based funds with a positive transaction amount to process on the EST when the disbursement level amount was already accepted at COD with DRI = true, ignoring the check of current attendance for disbursement.

Fix:
The EST process was modified to check for current attendance in the payment period prior to checking if the disbursement level amount has been accepted with a DRI = true at COD.

Testing:
Navigate to a student that is not currently in attendance and has a schedule Pell disbursement for the payment period. Attempt to run an EST process for the Pell disbursement and confirm an EST validation is presented stating the student is not currently in attendance.

Problem:
Regent Award was inadvertently closing an Automated R2T4 record as "Not Required" due to no Title IV eligibility in the R2T4 period.

Cause:
Regent Award was not correctly applying the Date of Withdrawal (WDD) and Date of Determination (DOD) to the R2T4 record before sending that record through the automated calculation process to determine if the R2T4 period contained Title IV aid.

Fix:
Automated R2T4 logic was modified to ensure the WDD/DOD is correctly applied in the R2T4 calculation when determining Title IV eligibility.

Testing:
Ensure R2T4 Automation is turned on under Institution Setup. Navigate to a student whose aid has fully disbursed and the student has attended more than 60% of the R2T4 period. Import an SBL with the R2T4 DOD/WDD. Process Batch Packaging for the student and ensure the R2T4 is not closed as "Not Required" due to no Title IV eligibility.

Problem:
Pell was not recalculating in the R2T4 Wizard when a student's enrollment decreased.

Cause:
R2T4 Recalculated Pell was not taking into account Year-Round Pell eligibility when setting correct award amounts in the R2T4 Wizard.

Fix:
R2T4 Wizard logic was modified to ensure the Pell Recalculation amount is accurately calculated, including Year-Round Pell eligibility.

Testing:
Navigate to a student whose Pell Grant disbursed, but then enrollment decreased thus causing a need to a Pell recalculation and an R2T4 to be calculated. Access the R2T4 Wizard and ensure the Recalculated Pell Grant amount is accurate.

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 unexpectedly unable to package some nonterm students after R2T4 finalization. An error occurred in a crossover payment period when Pell disbursements had award FAY not equal to payment period FAY.

Cause: 
Regent Award was incorrectly attempting to change a payment period ID on a disbursement set by R2T4 during the award reconciliation process.

Fix: 
Regent Award Packaging logic was updated to prevent payment period ID change attempts for disbursements set by R2T4.

Testing: 
Find a nonterm student that has paid disbursement in a crossover period where payment period is from previous FAY and award is from current FAY. Perform R2T4, finalize, and package student. Make sure that during packaging no blocking error messages appear.

Problem:
WI State Grant Report displayed incorrect data in the Tuition Code column.

Cause:
An issue was present in the report view when gathering the report data.

Fix:
The report view was updated to ensure the information is displayed accurately.

Testing:
Run the WI State Grant Report and ensure the Tuition Code column displays accurately for the affected student(s).

Problem: 
The Wisconsin State Grant report unexpectedly displayed Fall 2018 data in the Spring 2018 columns, Spring 2018 data in the Summer 2018 columns, and then did not display any Summer 2018 data.

Cause: 
An issue with the database view that produces the report data caused it to display incorrectly.

Fix: 
The report database view was corrected to ensure that the data will display correctly in the report output.

Testing: 
Run the Wisconsin State Grant report for FAY 2018-2019. Confirm that Fall 2018 data displays in the Fall 2018 columns, Spring 2018 data displays in the Spring 2018 columns, and Summer 2018 data displays in the Summer 2018 columns.

Problem: 
Batch Packaging via 'Scheduled Processes' was not creating the Process Log records when executed.

Cause: 
When the new process record was created for Scheduled Batch Packaging process run, the system carried over an incorrect value for Started On (processingStartDate) from Scheduled Packaging parameter sets. It was expected to be left as blank.

Fix: 
A code fix was applied to leave Started On date blank when Scheduled Batch Packaging Process is initiated.

Testing: 
Navigate to Processes > Scheduled Processes menu item. Add New Schedule with 'Batch Package' process type and frequency 'Once' settings. Once the scheduled process run takes place, verify Process Log. The relevant process type - RNA Analysis should be showing at Process Log.

Problem: 
Regent Award was inadvertently calculating SAP for students with missing grades when the configuration option to "Delay SAP Calculation Due to Missing Grades" was set to Yes.

Cause: 
Regent Award allowed SAP to be calculated for students whose courses were missing grades in the current SAP review period as well as the previous SAP review period.

Fix: 
Logic was modified to ensure that the SAP calculation is delayed and a "Missing Grades" Activity Log entry will be provided when a student has missing grades and the configuration option is set to Yes.

Testing: 
Ensure "Delay SAP Calculation Due to Missing Grades" is set to Yes under Institution Setup. Calculate SAP for a student with missing grades. Ensure the SAP calculation is not completed and an Activity Log Entry is reported that states the student has "Missing Grades."

Problem:
Students were presented with a server error when attempting to upload a document via the Document Portlet.

Cause:
Regent Award configuration was not properly adhering to the "UseSecureConnection" setting when students were attempting to upload documents via the Document Portlet.

Fix:
Modifications were made to the Document Portlet to ensure a server error is not presented when uploading documents.

Testing:
Navigate to the document portlet and attempt to upload a document. Ensure a server error is not presented.

Problem:
The "Parent's Legal Residents" date question's date reference was incorrect on both the 2018-2019 and the 2019-2020 TASFA Access Questionnaires.

Cause:
This question failed to be updated over the past several years as Annual Regulatory Changes were made to the questionnaires.

Fix:
The "Parent's Legal Residents" date question was updated on both the 2018-2019 and the 2019-2020 TASFA Access Questionnaires :

• For 2018-2019, the question was updated from "Parents Legal Residency Before 01/01/2010" to "Parents Legal Residency Before 01/01/2013."
• For 2019-2020, the question was updated from "Parents Legal Residency Before 01/01/2010" to "Parents Legal Residency Before 01/01/2014."

Testing:
Access the 2018-2019 TASFA questionnaire as a dependent student. Ensure that the "Parent Legal Resident" question states "Parents Legal Residency Before 01/01/2013." Access the 2019-2020 TASFA questionnaire as a dependent student. Ensure that the "Parent Legal Resident" question states "Parents Legal Residency Before 01/01/2014."

Problem:
Users were inadvertently seeing a "Download" screen when they attempted to download the most recent version of a SmartForm.

Cause:
There was an issue with the logic that caused the same download screen to appear for SmartForms as the user would see for attachments in the Document Portlet.

Fix:
Updates were made to ensure that if the document "attachment" is a SmartForm, the user will always download the latest version of the form when clicking the "Download" button.

Testing:
Enter the portal and attempt to download a SmartForm. Confirm that clicking the "download" icon immediately beings a download of the latest version of the SmartForm without any additional screens appearing.

Problem:
Regent Award inadvertently created duplicate "Review R2T4" tasks each time an R2T4 node was imported on the SBL with a non-unique Date of Determination (DOD) and a null value for the 50% Indicator.

Cause:
The logic that determines how to match an imported R2T4 node to an existing "StudentR2T4" record was incorrectly considering a null value in the 50% Indicator field to determine uniqueness.

Fix:
The matching logic was updated for determining whether a "StudentR2T4" record should be updated using newly imported SBL data, or if a new record should be created from the newly imported data. The updated logic appropriately accounts for a blank value in the 50% Indicator field. Minor data cleanup to remove duplicate "StudentR2T4" records is automatically included with this fix. Any existing duplicate "Review R2T4" tasks have been linked to the remaining non-duplicate "StudentR2T4" record, so as to retain any relevant notes in the task and restrict processes that the tasks are maintaining or action items that the tasks are driving. Activity Log Entries will be added to those students affected by the data clean-up.

Testing:
Import an SBL with an R2T4 Node containing a Date of Determination and Withdrawal Date but a null value for the 50% Indicator field. Import a second SBL with identical data. Confirm that a duplicate "Review R2T4" task is not created. Import a third SBL with a different Date of Determination and a null value for the 50% Indicator field. Confirm that a new "Review R2T4" task is created.

Problem: 
The scheduled Auto-Task Escalation and Auto-Task Assignment processes failed to create entries in the process log screen.

Cause: 
The error was caused by a missing UserId parameter at the related database procedure.

Fix: 
The necessary valid parameters were added to the procedures.

Testing: 
Log into the database of the affected instance. Execute dbo.rem_Task_AutoPrioritize and dbo.rem_Task_AutoAssignment procedures without any parameters. Login to the instance in the Regent application. Navigate to Process Log to verify that the corresponding log entries have been successfully created for the executed processes on behalf of the system user.

Problem:
Regent Review was inadvertently experiencing performance issues causing a decrease in processing times.

Cause:
Updates to the "Student - Watchlist" dashboard made in a prior release caused performance issues and slower processing times.

Fix:
The stored procedure for the "Student - Watchlist" dashboard was updated to include the five most recent activity log entries per student. The filtering, paging, and sorting capabilities have been removed from the dashboard to allow for faster processing times.

Testing:
Have multiple users attempt to complete a process within Regent Review, i.e. ISIR Verification, Document updates. Ensure processing times are not slowed down and normal processing is able to occur.

Problem:
Processing delays were unexpectedly occurring for Regent Review.

Cause:
The stored procedures associated with the User Interface were causing processing delays when attempting to run multiple processes.

Fix:
The stored procedures were optimized to allow for multiple processes to run consecutively without causing any processing delays.

Testing:
Navigate to the document for a student and mark a document as "Received". Toggle to the Task Tab and attempt to close the "Review Received Document" Task. Ensure there are not any processing delays between the toggle of the Document Tab and Task Tab.

Problem:
Regent Award unexpectedly did not allow users to switch between pages on Documents Tab for some students that had more than ten documents.

Cause:
Regent Award had redundant client-side decoding logic that failed and did not allow further document processing when document names contained "%" (percent) characters.

Fix:
Regent Award's redundant decoding logic was removed.

Testing:
Navigate to Document tab for any affected student that has more than ten documents (and so two or more pages with documents). Make sure that it is possible to navigate between document pages.

Problem:
Regent Award unexpectedly doesn't allow the user to add an individual program from the list of available programs to list of selected programs on Fund Setup screen.

Cause:
Regent Award was using incorrect comparison logic for verifying Program List available items vs. selected items.

Fix:
Regent Award logic was updated so available items in Program List are now correctly compared with selected.

Testing:
Navigate to Fund Setup. Select a fund. Click on the Programs tab. Click on the Edit button. Click on the Add button next to a program. Make sure program is added (moved from the left pane to right one).

Problem: 
Regent Award was incorrectly displaying Institutional Funds twice on the Awards Tab.

Cause: 
The same Institutional Funds had differing packaging philosophies thus causing those funds to display twice based on the packaging order.

Fix: 
Logic was modified to ensure Institutional Funds that have differing packaging philosophies are displayed once on the Awards Tab.

Testing: 
Navigate to an affected student. Package the student via MAP. Navigate to the Awards Tab and confirm Institutional Funds are displayed once for an Academic Year.