Problem:
A school configured Pell Grants to round to cents, but when students had an R2T4 resulting in a Refund amount with pennies, and the R2T4 was Finalized, Regent Award unexpectedly rounded the amount to dollars.

Cause:
The R2T4 logic incorrectly rounded reduced amounts to dollars in all cases.

Fix:
The R2T4 logic was updated to use the configured Rounding selection from Fund Setup.

Testing:
Ensure that Pell is configured to round to cents, and then navigate to a student that requires an R2T4 that will result in a refund. Complete the R2T4 and confirm that the R2T4 Refund and changed Pell amount includes cents. Finalize the R2T4. Navigate to the Academic Plan screen and click "Refresh." Confirm that the Pell amount shows the adjusted, non-rounded Pell amount including cents.

Problem:
Regent Award incorrectly calculated Direct Loan eligibility when nearing aggregate limits when National Student Loan Data System (NSLDS) had been imported.

Cause:
Regent Award incorrectly included Academic Year 0 when calculating Direct Loan eligibility that is close to the aggregate limit.

Fix:
Regent Award logic was modified to ensure the correct NSLDS data is considered when calculating Direct Loan eligibility that is near the aggregate limit.

Testing:
Navigate to a student whose Direct Loans are near the aggregate limit. Import a recent NSLDS file and package the student. Ensure the Direct Loans are calculated correctly.

Problem:
Eligible Year-Round Pell (YRP) disbursements were being canceled in error.

Cause:
YRP disbursements that already counted towards Pell Lifetime Eligibility Usage (LEU) were not being accounted for during packaging, causing Regent Award to calculate an over-award of Pell.

Fix:
Regent Award logic was modified to check that all YRP disbursements are properly accounted for during packaging.

Testing:
Navigate to a student nearing the 600% LEU limit that has been awarded YRP disbursements. Package the student and ensure the existing YRP disbursements remain awarded and that the total Pell remains under the 600% LEU limit.

Problem:
Regent Award was unexpectedly setting an incorrect Federal Award Year (FAY) for Direct Loans during the Export Student Transactions (EST) Actual process.

Cause:
Regent Award was updating manual awards with an incorrect FAY when the Nonterm Academic Year's start date was updated which was causing incorrect EST results.

Fix:
Regent Award logic was updated to lock down the FAY associated with an award regardless of the Academic Year's start date for manual awards.

Testing:
Locate a student with an Academic Year 1 start date that begins after July 1, 2019. The student should also have a paid Direct Loan. Update course data so that one of the courses begins prior to July 1, 2019. Access Modify Award Wizard and cancel the Direct Loan that previously disbursed. Run the EST process for negative transactions. Navigate to the Academic Plan and expand the award disbursement for the Direct Loan to verify the FAY remains 19-20.

Problem:
Regent Award was inadvertently moving the cents portion of a Pell Rebuild award to a different term.

Cause:
Regent Award was incorrectly rounding Pell rebuild awards when configured under Fund Setup to allow cents in the disbursement.

Fix:
Regent Award Logic was modified to ensure Pell rebuild awards maintain the cents portion when configured to round to the nearest cent under Fund Setup.

Testing:
Navigate to a student with a Pell rebuild award that includes cents in the disbursement. Package the student and confirm the cents remains associated with the rebuild Pell disbursement.

Problem:
Regent Award unexpectedly over-awarded the Ohio College Opportunity Grant (OCOG) when the award amount per payment period resulted in a calculated amount with a decimal.

Cause:
Regent Award was not correctly rounding on the disbursement level for FAY based awards when cents were returned from the OCOG calculated amounts per payment period.

Fix:
Regent Award logic was updated to ensure rounding is done at the payment period level, prior to calculating disbursements. The system truncates the values calculated per payment period so the overall award amount is not exceeded.

Testing:
Find an affected student awarded with OCOG who has enrollment resulting in a decimal award amount per payment period in multiple payment periods. Package the student. Confirm the OCOG calculated eligibility is not exceeding the expected value.

Problem:
Regent Award unexpectedly packaged the Federal Pell Grant in an Estimated status when an Active ISIR existed for the Federal Award Year (FAY).

Cause:
Regent Award was calculating the Federal Pell Grant as an estimated award when students received a scheduled Pell amount from a previous school and only the Year-Round Pell (YRP) portion was awarded in Regent.

Fix:
Regent Award logic was updated to award Pell Grant in an Accepted status when the award consists of only the YRP portion.

Testing:
Find a Pell-eligible student with 100% or more Pell awarded at a previous school for the same FAY. Confirm an ISIR is on the student record for the same FAY. Package the student and ensure the Pell Grant is packaged in an Accepted status.

Problem:
Award amounts were adjusted down to $0 for withdrawn courses after the COA freeze date for two institutional funds.

Cause:
Regent Award ignored courses having attendance when they were withdrawn after COA Freeze date, during the award amounts and enrollment level calculations.

Fix:
New logic was added to prevent the cancelation of enrollments in a payment period for withdrawn courses after the COA freeze date.

Testing:
Find the affected student. Upload an SBL with six attended units, with the date of withdrawal after the COA Freeze date. Run packaging. Verify that the two funds are awarded.

Problem:
Direct Loan awards were not repackaged after the registration was reinstated for the current term that was previously withdrawn.

Cause:
Regent Award was not able to detect an enrollment level change after the registration was reinstated for the current term.

Fix:
Regent Award logic was modified to ensure Direct Loans are reevaluated when registration is reinstated for the current term that was previously withdrawn.

Testing:
Find a student with withdrawn courses for the current term. Import courses on the SBL to reinstate registration for the term. Package the student and ensure Direct Loans are repackaged correctly based on the student's current enrollment level.

Problem:
Regent Award incorrectly packaged Federal Supplemental Educational Opportunity Grant (FSEOG) for terms where students had fully withdrawn.

Cause:
Regent Award considered terms eligible for FSEOG when there was no enrollment due to withdrawal.

Fix:
Regent Award logic was updated to cancel FSEOG when a student withdrew from all courses for a term.

Testing:
Find a student in the current term. Withdraw all courses for the term. Package the student and ensure FSEOG is canceled.

Problem:
The Regent Award Reprocess Process for Entrance Counseling (EC) and Master Promissory Note (MPN) COD Response files was not matching to student records once they were created via Student Batch Load (SBL).

Cause:
The database flag to match students during the Reprocess Process was not being set accurately.

Fix:
The database flag was modified to ensure it is set correctly when matched with student records.

Testing:
Run the Reprocess Process and ensure the EC and MPN COD Response file records are accurately matched up to student records.

Problem:
A user was editing an AY0 loan using Modify Award Wizard (MAW). The user changed the loan from a three-term loan to a two-term loan. However, the loan period unexpectedly remained a three-term loan period. When the user imported the COD WB data with the shorter loan dates, the COD Web Response Review Queue showed the award with a date mismatch warning.

Cause:
The system did not apply GEN13-13 loan period truncation logic to loan periods in AY0 years.

Fix:
Regent Award will apply GEN13-13 loan period truncation to AY0 years when the user is editing the loan in Modify Award Wizard.

Testing:
Navigate to an affected student who has a three-term loan in AY0, with unpaid disbursements in the third term. Click on the loan's amount to view the loan period dates and loan period ID. Edit the loan in Modify Award Wizard, zeroing out and canceling the amount in the third term. Finish MAW and click "Refresh." Click the loan amount to view the Disbursement Details. Confirm that the system displays the new Loan Period dates and new Loan Period ID. Import a COD WB file for the AY0 loan, with the WB data covering the shorter, two-term dates. View the updated award in the COD Web Response Review Queue screen. Confirm that the "Message" column does not show any errors and the "Action" flag is set to 'No.'

Problem:
Regent Award ignored the Cumulative Units configuration in Cost Setup, causing multiple cost items to be assigned into one payment period.

Cause:
Regent Award was skipping the evaluation of the Cumulative Units at the payment period level for nonterm scenarios. That resulted in multiple cost items assigned into one payment period.

Fix:
The Cumulative Units' evaluation was added to the payment period level for nonterm scenarios.

Testing:
Find the affected student. Run packaging. Verify packaging results. Confirm the Cost Items are assigned into payment periods based on the cumulative units range filters configured in Cost Setup.

Problem:
Direct Loans for Undergraduate students were not respecting the enrollment level needed to disburse within the Disbursement Schedule Setup.

Cause:
Regent Award was not accurately handling the Disbursement Schedule Release Unit Type when determining if a disbursement can be made.

Fix:
Regent Award logic was modified to ensure Direct Loans will not disburse unless enrollment has been established at least Half-Time per the Disbursement Schedule Setup.

Testing:
Ensure the Direct Loan Disbursement Schedule Setup is configured to disburse for Half-Time or greater enrollment. Navigate to a student in an undergraduate program that has attended Less Than Half Time in the payment period. Run an Export Student Transaction (EST) process to disburse the Direct Loans and confirm the disbursement is not processed due to Less Than Half Time (LTHT) enrollment.

Problem:
Regent Award unexpectedly updated a disbursement's scheduled date to future date for a paid award when a student withdrew from courses in the previous module.

Cause:
Regent Award was updating a disbursement's scheduled date to a future date when a student had registration in future modules but withdrew from the starting course in the current module.

Fix:
Regent Award logic was updated to ensure that a disbursement's scheduled date remains intact paid disbursements when a student's enrollment changes.

Testing:
Find a student registered in Module 1 and Module 2 of a term, the term has not yet started and a portion of any the federal aid has already disbursed. Withdraw the student from the Module 1 courses. Package the student and make sure the disbursement's scheduled date for paid disbursement did not change.

Problem:
Some students with a Wisconsin State Grant had amounts displayed on the Awards tab with cents that did not add up to the total amount value in dollars. The fund has specific rounding rules to round amounts to whole dollars in each term.

Cause:
When the award amount had an odd-numbered value, and the amount was split across multiple terms, the system sometimes did not correctly account for all the partial-dollar amounts.

Fix:
The logic was corrected to ensure the per-term amounts will always add up to the total grant amount.

Testing:
Navigate to an affected, eligible student who has a Wisconsin Grant amount resulting in an amount value not divisible by two or three. Package the student. Examine the amounts on the Academic Plan, Disbursement Details, and Awards tab. Confirm all amounts are in whole dollars and do not display cents. Confirm the sum of the amounts matches the student's total grant amount. Pay a disbursement via Export Student Transactions. Confirm the paid amount does not have any cents.

Problem:
Some students with a Wisconsin Grant had unexpected per-term amounts. The affected students had fewer than three semesters of remaining eligibility. The amounts appeared to change during repackaging.

Cause:
The logic that checks for the maximum number of terms was miscalculating the number of terms used in prior years.

Fix:
The system logic was corrected for calculating the student's number of terms already used for the grant. The system adds the number of past and current terms when calculating the total terms used by the student.

Testing:
Navigate to an affected, eligible student who has actual registration for three terms in Federal Award Year 2020. Load a Wisconsin Grant Roster File for 2020 with a semester count of 8 or 9 and amounts in all three terms. Package the student several times. Confirm the grant amount is only awarded for the eligible terms.

Problem:
Regent Award was incorrectly calculating the Guild Walmart Tuition Benefit Fund when a Program Change occurred.

Cause:
Regent Award was incorrectly queuing the Guild Walmart Tuition Benefit Fund during packaging causing inaccurate fund amounts.

Fix:
Regent Award packaging queue logic was modified to ensure the Guild Walmart Tuition Benefit Fund is packaged appropriately after completing a Program Change.

Testing:
Navigate to a student eligible for the Guild Walmart Tuition Benefit Fund and also has a Program Change. Process the Program Change and ensure the Guild Walmart Tuition Benefit Fund is accurately packaged for the new program.

Problem:
Regent Award was inadvertently creating an Academic Plan (AP) with inaccurate Academic Year (AY) dates resulting in COD rejects when a student began a Standard Academic Year (SAY) program after the expected header term of Summer or Fall.

Cause:
Regent Award did not add "historic" header term(s) to an AY when a student began their program after the header term dates had already passed.

Fix:
Regent Award logic was updated to add "historic" header terms to an AY when a student begins a SAY program after the anticipated header term dates.

Testing:
Create a student that starts the quarter SAY program in the Winter term. Make sure that the Summer and Fall terms are created on the Academic Plan and marked as "historic".

Problem:
Regent Award was inadvertently prorating Direct Loans for Graduate programs in a final period of study.

Cause:
Regent Award was incorrectly counting the term after program completion when packaging Direct Loan amounts for a final Academic Year (AY).

Fix:
Regent Award logic was updated to exclude terms that fall after the program completion when packaging Direct Loans for Graduate programs.

Testing:
Navigate to a student in a Graduate program in a final period of study. Package the student and ensure the Direct Loans are packaged appropriately.

Problem:
Regent Award was incorrectly packaging Direct Loans from the next Federal Award Year (FAY) during a crossover period instead of the current FAY.

Cause:
Regent Award was not correctly evaluating the loan period's crossover dates when packaging Direct Loans.

Fix:
The logic was modified to ensure crossover loan periods are evaluated properly to ensure Direct Loans are packaging with the current FAY loan eligibility.

Testing:
Navigate to a student whose first nonterm payment period is a crossover period. Package the student and ensure Direct Loans are packaged with the current FAY period.

Problem:
Regent Award unexpectedly over-awarded a student by the amount of manual Gift Aid after a Substantially Equal Program Change.

Cause:
Regent Award did not incorporate a manual award from a completed term into the Unmet Cost re-calculation for this term when the Substantially Equal Program Change was completed in the second or subsequent term of the Academic Year.

Fix:
Regent Award logic was updated to include all manual awards into the calculation regardless of the award eligibility for a new program when a Program Change is completed.

Testing:
Find an Academic Year scoped fund that is eligible for a term-based Program A, but not eligible for a term-based Program B. Find a student in Program A who is eligible for federal loans, having total loan limits higher than the Cost of Attendance for the term. The first term of the student's current Academic Year should be completed (term's end date is in the past). Award the student in the completed term with the fund that is only eligible for Program A. Prepare an A to B Program Change between the two programs. Perform the Program Change to Program B as Substantially Equal. Package the student. Confirm the student does not have a negative Unmet Cost for the completed term.

Problem:
Nonterm students were progressing to the second Payment Period (PP) but did not have enough completed Progression units to fill the first PP.

Cause:
Regent Award was not excluding units that were completed but did not have progression when building the nonterm academic plan.

Fix:
A new approach was implemented, using the calculation of (Registered units - Completed units + Progression units). Regent Award applies the new calculated amount of units when determining whether a nonterm student should fall into slow progression logic.

Testing:
Navigate to the affected students and check the number of Progression Units on the Academic Plan. Package the student using the Modify Academic Plan wizard. Confirm that when the number of Progression Units is less than half of the Units in the Academic Year definition, the student continues in the first Payment Period.

Problem:
Regent Award inadvertently presented a packaging error stating "fund already has a released or paid disbursement and Fund Setup disallows the increase of paid disbursements."

Cause:
Regent Award incorrectly allowed the increase of paid disbursements when determining eligible disbursement amounts across an entire award.

Fix:
Regent Award logic was updated to prevent the increase of paid disbursements when Fund Setup is configured to disallow the increase of paid disbursements. Regent Award will create a new disbursement for the award period when additional eligibility is determined and the previous disbursement has already paid.

Testing:
Under Federal Pell Grant Fund Setup, configure "Allow Auto Adjustment of Paid Disbursements" to "Yes" and under Campus Setup configure “Attempt To Keep Paid Disbursements Unchanged” to "Yes." Navigate to a student in a current term where Pell has already disbursed. Import an SBL to increase Pell eligibility. Package the student and ensure a new Pell disbursement is created instead of packaging an increase to the existing paid disbursement.

Problem:
Regent Award unexpectedly created an Academic Year with both term and nonterm Payment Periods. The student could not be awarded in the Academic Year.

Cause:
The affected student had program change data for multiple programs, with a mix of term and nonterm programs. One of the programs was missing its Program Completion Date. Regent Award did not correctly load data for one of the inactive programs having a pre-start program change.

Fix:
Regent Award logic was updated to properly load data for inactive programs during a program change.

Testing:
Perform a term (A) to term (B) to nonterm (C) Program Change. A to B Program Change data should be loaded and processed prior to Program B start. Program Change data for program C should be loaded prior to program B's start. B and C Program Start Dates should be equal. Perform the term (B) to nonterm (C) Program Change after program C's start date. Process the student through the Program Management Wizard, selecting nonterm program C. Confirm no program B terms appear in the first Academic Year of nonterm program C.

Problem:
Regent Award was unexpectedly creating incorrect Academic Years (AY) after completing a Nonterm to Term program change that occurred during the middle of an AY.

Cause:
Regent Award was not calculating a full-length AY including "historic" terms when a student changed from a Nonterm to a Term program during the middle of an AY.

Fix:
Regent Award Logic was updated to ensure "historic" terms are created when calculating accurate AY lengths after completing a Nonterm to Term Program Change that occurs mid-AY.

Testing:
Perform a Mid-Year Non-Susbstatially Program Change from a Nonterm program to a SAY program and confirm Academic Years are correctly calculated.

Problem:
Academic Year dates were not correct when a Non-Term to a Term Program Change was completed.

Cause:
Standard Academic Year (SAY) pre-enrollments were not correctly packaging during the Program Change causing incorrect Academic Year (AY) dates to be packaged.

Fix:
Regent Award logic was modified to ensure SAY pre-enrollments are packaged during a Non-Term to Term Program Change.

Testing:
Navigate to a student with a Non-Term to Term Program Change. Complete the Program Change and ensure the AY dates are correct.

Problem:
Regent Award was not accurately closing the "Review Program Change" task after processing the Program Change through the Program Management Wizard (PMW), thus preventing the Program from updating on the Academic Plan.

Cause:
Regent Award was incorrectly using information from a prior instance of the same program to update information for the new instance of the program during the Program Change process.

Fix:
Regent Award logic was updated to ensure that program validation checks are based on the specific instance of a program when multiple instances of the same program exist for the student.

Testing:
Find a student with a pending A-B-C-B (or a similar version) Program Change. Process the Program Change through the PMW. Ensure the Program Change task is completed and the new program populates on the Academic Plan.

Problem:
A SAY Summer Trailer student had a Substantially Equal (SE) Program Change after the Spring term, with a new program starting in the Fall. Later, the student added enrollment in the Summer term. The system unexpectedly put the Summer in a separate, single-term Academic Year (AY) instead of attaching it to the previous AY.

Cause:
For SAY programs with a summer trailer term, the system incorrectly created a new Academic Year after a SE Program Change if the other terms in the new program were all following the trailer term.

Fix:
The logic was updated for SAY summer trailers. When a student has a prior Academic Year other than an AY0, and that AY does not already contain a summer term, the system will add the summer trailer term to the previous AY.

Testing:
Navigate to an affected student with a new, SE program starting in the Fall term and no Summer courses. After the program change has been processed, add actual enrollment for the Summer term in the new program. Package the student. Confirm that the Academic Plan shows the student's Summer term as part of the previous Academic Year. View the student on the Student Portal. Confirm that the Student Portal shows the Summer term as part of the previous Academic Year.

Problem:
Regent Award inadvertently ignored Direct Loans that should have been included as "Could Have Been Disbursed" within the Return to Title IV (R2T4) calculation.

Cause:
Regent Award was incorrectly calculating Post Withdrawal Disbursements (PWD) when there are multiple awards for the same fund included in the same payment period.

Fix:
Regent Award logic was modified to ensure all funds are accounted for in an R2T4 calculation when there are multiple awards for the same fund in the same payment period.

Testing:
Navigate to a student eligible for multiple Direct Subsidized Loan funds in the same payment period that has originated but has not disbursed. Import an SBL with an R2T4 node. Run Batch Packaging (BP) to execute the Automated R2T4 process. Ensure the Direct Subsidized Loans are included in the R2T4 as "Could Have Been Disbursed" funds and the R2T4 is not closed as "Not Required."

Problem:
Eligible Federal Pell Grant Post Withdrawal Disbursement (PWD) disbursements were returned in full incorrectly when there was an eligible portion of the disbursement to be retained.

Cause:
Regent Award was not accurately updating the PWD disbursement amount based on the calculated eligibility within the PWD Wizard.

Fix:
Regent Award logic was modified to ensure the Accepted PWD amount accurately populates in the PWD Wizard.

Testing:
Navigate to a student that needs a Return to Title IV (R2T4) completed and has multiple Pell disbursements present for the R2T4 period. Process the R2T4 that results in a PWD and ensure the Pell PWD disbursements are accurately calculated on the PWD tab. Finalize the PWD and confirm the disbursement amounts reflected on the Academic Plan are accurate.

Problem:
Regent Award incorrectly divided disbursement amounts on the Return to Title IV (R2T4) Post-Withdrawal Disbursement (PWD) Tab.

Cause:
Regent Award attempted to split the PWD eligible disbursement amounts across all available disbursements for the award.

Fix:
Regent Award logic was modified to ensure that a single PWD eligible disbursement is not split into multiple disbursements on the PWD Tab.

Testing:
Navigate to a student with multiple disbursements of a single fund that must have an R2T4 completed. Complete the R2T4 resulting in a PWD where only the first disbursement is considered an eligible PWD. Ensure the single disbursement is not split into multiple disbursements when displayed on the PWD Tab.

Problem:
Regent Award incorrectly calculated a Return to Title IV (R2T4) as "Not Required" when there was attendance present for the R2T4 period.

Cause:
Regent Award did not accurately account for course attendance information when determining if an R2T4 is required.

Fix:
Regent Award logic was modified to ensure attendance is accounted for when determining whether an R2T4 is or is not required.

Testing:
Ensure R2T4 Automation is turned on at the Institution Level. Navigate to a student needing an R2T4 calculation and ensure there is attendance present for the R2T4 period. Import a Student Batch Load (SBL) with an R2T4 node present. Run Batch Packaging (BP) to execute the R2T4 Automation process and ensure the R2T4 is not closed as "Not Required" due to no attendance.

Problem:
Regent Award incorrectly calculated the Scheduled Payment Period (PP) End Date on automated R2T4s when utilizing the R2T4-only Extrapolation Method.

Cause:
Regent Award logic was unable to appropriately update the Scheduled PP End Date with the calculated extrapolated date on automated R2T4s.

Fix:
R2T4 logic was modified to ensure the Scheduled PP End Date is set correctly.

Testing:
Navigate to a nonterm student with an R2T4. Process the R2T4 and ensure the calculated Scheduled PP End Date is accurate.

Problem:
Regent Award was incorrectly rounding Post Withdrawal Disbursement (PWD) Loan amounts by $1 when completing a Return to Title IV (R2T4).

Cause:
Incorrect rounding was occurring during the PWD finalization when Regent Award determined the gross loan amount.

Fix:
Rounding logic was resolved during PWD finalization.

Testing:
Complete an R2T4 that includes an eligible Direct Loan PWD. Finalize the PWD, MAP the student, and ensure the Loan amount offered on the Academic Plan is packaged correctly.

Problem:
Regent Award unexpectedly presented the following error in the Satisfactory Academic Progress (SAP) Wizard: Student has some SAP records and SAP Review Periods that are not covered by a SAP policy. Please contact your administrator. SAP Setup needs a configuration change to include those dates in the SAP policy.

Cause:
Regent Award incorrectly calculated SAP review periods after a Program Change, where the last Academic Year of the previous program had a historic Payment Period.

Fix:
Regent Award logic was updated to include Academic Years' historic payment periods into the SAP calculation.

Testing:
Find a SAY student with a pending Program Change that has no registration in the current term. Perform Non-Substantially Equal Program Change that would result in the previous program term becoming historic. Open the SAP Wizard and confirm the SAP Wizard screen is displayed without any errors.

Problem:
Batch Packaging (BP) was unexpectedly failing to process when the Institution Setup configuration setting to "Delay SAP Calculation Due to Missing Grades" is enabled.

Cause:
Regent Award was not accurately including the Institution Setup configuration option to "Delay SAP Calculation Due to Missing Grades" when processing Batch Packaging.

Fix:
Regent Award logic was modified to ensure the "Delay SAP Calculation Due to Missing Grades" configuration option is included in the Batch Packaging process.

Testing:
Enable the Institution Setup configuration option to "Delay SAP Calculation Due to Missing Grades." Run Batch Packaging and ensure BP does not fail to process due to the "Delay SAP Calculation Due to Missing Grades" setting.

Problem:
The E-signature designation within the Regent Award User Interface (UI) inaccurately reflected a value of "No" when students uploaded document requirements via the portal after successfully completing the E-signature Process.

Cause:
Regent Award was not accurately setting the E-signature value within the UI for document requirements.

Fix:
Regent Award logic was modified to ensure the E-signature value is properly set when documents are uploaded via the Student Portal after the student E-signature Process is completed.

Testing:
Navigate to a student with documents in a "Needed" status that must be provided via the Student Portal. Access the student's Portal account, upload the "Needed" documents and complete the E-signature Process. Access the UI and navigate to the Documents Tab. Confirm the E-signature value is set to "Yes" for those documents uploaded via the Student Portal.

Problem:
The Statement of Understanding (SOU) section within the Student Portal was still being presented after the student confirmed understanding the responsibility of accepting Direct Loans thus preventing students from fully accepting their award package.

Cause:
Statement of Understanding documents that were previously deleted caused the SOU section to continue to be presented in the Student Portal.

Fix:
SOU documents that were previously deleted will now be ignored when determining whether the SOU section should be presented to the student in the Student Portal.

Testing:
Navigate to a student portal account where the SOU section has already been acknowledged. Access the Awards Portlet and confirm the SOU section is no longer presented.

Problem:
The 'Nontax Return Filers' section of the PDF version for the Verification Worksheet showed incorrect verbiage, referring to a spouse for a dependent student.

Cause:
Some question options in the 'Nontax Return Filers' section had identical values in the description that resulted in a verbiage mismatch when the PDF version of the Verification Worksheet was processed.

Fix:
The internal verification flow was updated to get the option descriptions by identifiers instead of by values when the PDF version of the Verification Worksheet is generated.

Testing:
Log in to the Student Portal as a dependent student. Complete the 2018-2019 Verification Worksheet. Review the verbiage at the 'Nontax Return Filers' section in the PDF version of the document. Confirm the text is 'I did not file and am not required to file.'

Problem:
Regent Award QA environments were not accurately displaying the red banner that differentiates the User Interface (UI) from Production environments.

Cause:
Regent Award was not accurately setting the red banner for QA environments.

Fix:
Regent Award logic was modified to ensure all QA environments display the red banner.

Testing:
Login into the QA environment. Make sure the red QA banner is shown on top of the browser page.

Problem:
The permissions for the Program Management Wizard and Modify Academic Plan Wizard referred to the features as "screens" instead of "wizards."

Cause:
The permission names were not an exact match to the feature names.

Fix:
The names of the permissions and permission groups were corrected.

Testing:
Log in using a role that allows you access to the Roles area of Administration. Browse to Roles and expand the permissions tree for Enterprise Permissions > Student Permissions > Academic Plan tab. Confirm that the permissions for the Program Management Wizard, Access Program Management Wizard, and Access Modify Academic Plan Wizard have the word "Wizard" in their names.

Problem:
On the Student Documents tab, users could not delete their own uploaded attachments.

Cause:
The screen was not displaying the Delete button for attachments added by the logged-in user.

Fix:
The screen displays the Delete button for attachments added by the logged-in user.

Testing:
Log in with a user account having permissions to "Edit Documents," but not having permissions enabled for "Delete Document Attachments" and "Delete Attachments Regardless of Status." Navigate to a student's Documents tab. Select a Document that has attachments uploaded by the student or other users. Edit the Document. Add an attached file and Save the Document. Refresh and Edit the Document again. Try to delete the attachments. Confirm the system allows deleting only the file added by the logged-in user, but not the files added by the student or other users. Add a Note to the document, save it, and refresh the screen. Confirm the deleted file is no longer available.

Problem:
Regent Award presented slow processing when Course Override updates were made.

Cause:
Course Override processing caused the Regent Award User Interface (UI) to experience a significant decrease in performance.

Fix:
Regent Award logic was modified to prevent performance issues from occurring when Course Overrides are utilized.

Testing:
Complete a Course Override for a student. Package the student and confirm that no performance issues occur, i.e. Academic Plan updates, screen loading, etc.

Problem:
Regent Award was unexpectedly slow when attempting to search for a student.

Cause:
User Interface (UI) performance issues were causing slow processing.

Fix:
UI performance logic was adjusted to provide consistent and efficient performance.

Testing:
Navigate to the UI and attempt to search for a student. Confirm the slow performance issues are not presented.

Problem:
The Verification Worksheet did not allow a student/parent to select 8 children for the "Number of Dependents" question.

Cause:
The Verification Worksheet did not include an option to allow more than 8 children in the drop-down menu for the "Number of Dependents" question.

Fix:
The Verification Worksheet was corrected to include the option to select 8 children in the drop-down menu.

Testing:
Navigate to an independent student that is selected for Verification. Access the Verification Worksheet as the student and confirm that the option to select 8 children from the "Number of Dependents" drop-down menu is present.