|
| RS-13626 | Regent Award | Activity Log | Problem:
ISIR related Activity Log Entries (ALE) related to the following activities did not indicate the specific ISIR that created the ALE: - Marking an ISIR for Correction
- Marking an ISIR as "Verified"
- Exporting ISIR Corrections
- ISIR Identity Verification
Cause:
The database table that holds ALE information did not provide a link to the actual ISIR that created the ALE. The database table was missing the "ISIRRecordDataID" (Regent Award internal ISIR ID) that was related to the ALEs. Fix:
Regent Award was modified to begin logging the "ISIRRecordDataID" information with each ALE. A script was created to populate the missing "ISIRRecordDataID" references. Testing:
Find a student with an ISIR. Use the ISIR Correction / Verification Wizard to provide a Verification Status for the ISIR. Run a population query and verify that the ISIRRecordDataID column has a value for the verification status update ALE. |
| RS-14117 | Regent Award | Awarding | Problem:
A user changed a Direct Unsubsidized Loan's Additional Eligibility Indicator in the Loans tab. After changing the flag value and packaging the student, the system unexpectedly returned the flag to a previous value. Cause:
If any Unsubsidized Loan for a Federal Award Year (FAY) had an Additional Eligibility Indicator with value True, it caused all Unsubsidized Loans on the same Award Period to be set True also. However, the Consolidated Origination and Disbursement (COD) information was not filtered to apply to only a specific Federal Award Year. Fix:
The Additional Unsubsidized Eligibility property code was changed to consider the Award Year. The system filters to a specific FAY when checking for an Additional Eligibility Indicator value of True. Testing:
Navigate to affected students, select appropriate Loan on the Loans tab, and change Additional Eligibility Indicator flag value and Save changes. Observe the value change. Package the student. Refresh the Loans tab. The Additional Eligibility Indicator flag should be the same saved value. |
| RS-14108 | Regent Award | Awarding | Problem:
Duplicate Loan Periods were presented within the Program Management Wizard when a user modified Academic Years. Cause:
Regent Award added duplicate loan periods during the loan period processing. Fix:
Logic was added to look for duplicate loan periods during pre and post-award processing. If duplicate loan periods are detected, Regent Award will consolidate them so that only one loan period remains. Testing:
Package a student through either Batch Packaging or the Modify Academic Plan wizard. Access the Program Management Wizard, select Manage Academic Years / Loan Periods. Select Edit for the manual AY. Confirm that the loan period is not duplicated under the Loan Period section on the Manual AY screen. |
| RS-14076 | Regent Award | Awarding | Problem:
Some term students had paid Pell COD rebuild awards. When the Summer term ended, the system changed the Pell amounts so they became over-awarded. Cause:
The Pell rebuild awards had paid disbursements. The system used incorrect amounts for the rebuild disbursements when calculating Pell awards. The system incorrectly did not adjust the awards for Year-Round Pell (YRP) eligibility. Fix:
Logic was put in place to ensure paid Pell rebuild awards are returned to their original amounts when packaging for Year-Round Pell eligibility. Testing:
Package an affected term student. Ensure the last term in the FAY for Pell is not over-awarded. |
| RS-13973 | Regent Award | Awarding | Problem:
Manual awards were originally added via Add Award Wizard (AAW) in an "Offered" or "Estimated" status. When a user later accepted the manual awards using Modify Award Wizard (MAW), the wizard incorrectly changed them to non-manual. Cause:
Recent code changes had altered the manual award logic in AAW and MAW. The wizard incorrectly identified existing manual awards as needing re-evaluation, thus clearing each award's manual flag. Fix:
Additional logic was added to check if an award has been modified to determine if the award must remain in a manual state. Testing:
Add an award via the Add Award Wizard for a student in an "Offered" or "Estimated" status. Refresh and confirm the award is marked manual. Once the award has been added, edit the award in the Modify Award Wizard. Change the award to Accepted status. Continue through MAW. Confirm the award is still marked as manual. |
| RS-13942 | Regent Award | Awarding | Problem:
Regent Award was not adhering to the Pell Formula 4 rules when packaging Pell for a shortened final Remaining Period of Study in a nonterm program. Cause:
Regent Award packaged Pell in the final payment period in a Non-Term program using actual, registered units. The registered units were greater than the number of units required to complete the program, causing an incorrect Pell calculation. Fix:
Regent Award has new logic for calculating Pell in a final nonterm payment period. Pell grants are based on the number of units required to complete the program instead of actual, registered units. Testing:
Navigate to an affected nonterm student in a Pell Formula 4 Program with a shortened final Remaining Period of Study. Package the student. Ensure Pell is packaged based on Pell Formula 4 calculations. |
| RS-13756 | Regent Award | Awarding | Problem:
A term student had a loan that did not cover all terms in the Academic Year. In Modify Award Wizard (MAW), when a user tried to adjust a payment period amount for one of the terms, MAW prevented editing the amount with the error message: This term is not included in the loan period. Cause:
The wizard prevented users from editing a disbursement outside an existing loan period. Fix:
The restriction was removed. Users can edit disbursements on terms that fall outside the original loan period dates. Testing:
Navigate to an affected student with a loan that is not on all terms in the Academic Year. Edit the loan in Modify Award Wizard. Regent Award should allow editing the Payment Period amount. The warning message should still be displayed. Continue through Modify Award Wizard. Regent Award should keep the payment period amount and allow editing of the disbursement amounts. The loan period should change to include all terms with nonzero disbursements. |
| RS-13703 | Regent Award | Awarding | Problem:
A nonterm student had a Reversed R2T4. When the student was packaged, Regent Award unexpectedly reduced the loan amounts. The affected student was in a shortened final Remaining Period of Study (RPS) Academic Year. Cause:
The system prorated the loan amounts based on the incorrect number of units. Fix:
In an RPS AY, Regent Award prorates loans in closed payment periods based on registered units. Regent Award prorates loans in open payment periods based on Anticipated units. Testing:
Navigate to an affected nonterm undergraduate student who has a finalized R2T4 and current prorated loans in an RPS AY. Reverse the R2T4. Package the student. Refresh and examine the loans. If the payment period is open, the prorated loan amounts should be based on the Anticipated units. If the payment period is closed, the prorated loan amounts should be based on Registered units. Examine the Financial Award Begin and End dates on the Loans tab. The dates should cover the full AY. The loan's FAY in the FAID should match the loan period dates. |
| RS-13589 | Regent Award | Awarding | Problem:
The user was not able to accept or cancel an award via Modify Award Wizard (MAW). MAW gave an error message, Error in XML Document. Cause:
An incompatible XML analysis library caused the issue during MAW student data loading. Fix:
Regent Award is updated with the latest XML analysis library. Testing:
Navigate to affected students and edit Direct Unsubsidized Loan in the corresponding Academic Year. The user is expected to be able to accept or cancel the award via MAW. |
| RS-13369 | Regent Award | Awarding | Problem:
A student had an unexpected XML error in some wizards: There is an error in XML document. The problem happened for Modify Academic Plan (MAP) - Step 2 Advanced Packaging; Add Award Wizard (AAW); and Modify Award Wizard (MAW). However, Basic MAP and the Program Management Wizard (PMW) still packaged correctly without error. Cause:
Regent Award was using an incompatible XML loading library service causing an error when loading the student's data. Fix:
The Regent Award XML loading library was updated. Testing:
Navigate to an affected student. Package the student using Modify Academic Plan, Advanced Packaging, and Continue through the wizard. On the Awards tab, add an award to the student using Add Award Wizard and continue. The student should package without any XML error. On the Awards tab, edit an award in Modify Award Wizard and continue. The student should package without any XML error. |
| RS-3510 | Regent Award | Configuration/Setup | Problem:
When an Administrator added or edited a Campus, Institution, or Packaging Philosophy setup, a technical error sometimes blocked changes: "There were some invalid properties in your request." Cause:
For long names for Campus, Institution, or Packaging Philosophy, the system could not save the Packaging Philosophy name. The database field length for the Packaging Philosophy name was shorter than the value the system used. Fix:
The Packaging Philosophy field size in the database was increased to 90 characters. Data View Change:
The column length of the dataExtract_PackagingPhilosophySetup_Config_View.locationName column has changed to 90 characters due to a change in the column length of the source column. Per the Data View Versioning Policy this is a non-breaking change and therefore a new version of the view was not created. Testing:
Navigate to the Administration Packaging Philosophy Setup screen. The user should be allowed to enter 90 characters in the Name field on Packaging Philosophy Setup setup screen. The user should be allowed to enter maximum 60 characters in Name field in Institution setup screen. The user should be allowed to enter maximum 60 characters in Campus Name field in Campus setup screen. The new configurations should be successfully created. |
| RS-14352 | Regent Award | EST/Disbursements | Problem:
Regent Award unexpectedly applied awards to the packaging balances twice when the student had a task that blocked packaging. This caused the Direct Loans to cancel in error. Cause:
Tasks that were not configured to restrict packaging of Federal Direct Loans were causing other funds to be applied more than once against packaging balances, thus resulting in decreased loan eligibility. Fix:
Logic was added to ensure that an award is only applied once to the packaging balances when the student has a task that is configured to restrict packaging. Testing:
Access a student record that has a task that is configured to restrict packaging for funds other than Federal Direct Loans, i.e. "Review Pell Negative Pending Amount". Package the student and ensure the Federal Direct Loans are not canceled. |
| RS-14295 | Regent Award | EST/Disbursements | Problem:
Regent Award unexpectedly returned Award Year (AY) based funds that were packaged prior to Federal Award Year (FAY) based funds, per the Packaging Philosophy, on or after 10/1/2018 when the 2018 FAY closed. Cause:
FAY based funds associated with the same award period as AY based funds were being applied first during packaging on or after 10/1/18, thus causing the AY based funds to decrease in error. Fix:
Logic was updated to ensure the Packaging Philosophy order is adhered to even when the FAY is closed, i.e. AY based funds will package prior to FAY based funds per the Packaging Philosophy. Testing:
Access a student that is/was packaged with an AY based fund that packages prior to a FAY based fund per the Packaging Philosophy. Package the student via BP/MAP and confirm that the AY based fund remains packaged on the student's Academic Plan |
| RS-14149 | Regent Award | EST/Disbursements | Problem:
Some BBAY term undergraduate students had a shortened Remaining Period of Study (RPS). The students had only one term in their final Academic Year (AY) and were enrolled at least half-time. The day after the term ended, Regent Award repackaged the students' Direct Loan amounts and unexpectedly zeroed out the loan amounts in the RPS AY. Cause:
The students were registered for more units than needed to complete their programs. The system incorrectly used anticipated units for the loan proration formula. Fix:
When term-based undergraduate students are over-registered in an RPS AY, the system calculates the remaining units to complete the program. The system uses those remaining units for prorating loan amounts. Testing:
Repackage loans for an affected undergraduate term student who has just finished their Remaining Period of Study AY. The system should calculate Direct Loan amounts based on the remaining units needed to finish the program. |
| RS-14252 | Regent Review | ISIR Processing/Verification | Problem:
Regent Award was unexpectedly displaying reject codes within the ISIR Verification Wizard that do not pertain to the ISIR selected for Verification. Cause:
Incorrect logic was in place for the use of reject codes within the ISIR Verification Wizard related to parent/student signatures. Fix:
Logic was updated to ensure the correct reject code is presented based on the verification data provided for the ISIR. Testing:
Navigate to a student selected for Verification in the 19/20 FAY. Access the ISIR Verification/Corrections Wizard. Select the Signatures Tab and update Field 154 to "Applicant." Select Continue. Confirm that only reject code 16 is displayed under Step 2 of the Verification Wizard as needing to be updated. |
| RS-14251 | Regent Review | ISIR Processing/Verification | Problem:
Regent Award was unexpectedly displaying a value of 2009-2010 for 2019-2020 ISIRs within the Compare ISIRs Wizard. Cause:
Incorrect coding was in place for the display of the 2019-2020 FAY within the Compare ISIRs wizard. Fix:
Logic was updated to ensure the Federal Award Year is displayed correctly when viewing ISIRs within the Compare ISIRs Wizard. Testing:
Navigate to a student with ISIRs from two separate FAYs are present. Select the checkbox next to a 2018-2019 and 2019-2020 ISIR. Confirm that the value for the 19/20 ISIR displays as 2019-2020. |
| RS-14249 | Regent Review | ISIR Processing/Verification | Problem:
Regent Award was incorrectly displaying duplicate values under the Verification Tracking Group Menu Bars. Cause:
Regent Award had incorrect logic in place for the display of verification group values. Fix:
Logic was updated to ensure verification group values are not duplicated when viewing an ISIR selected for verification. Testing:
Navigate to a student selected for Verification. Select the Verification Group Menu Bar and confirm the values are not duplicated. |
| RS-13810 | Regent Award | ISIR Processing/Verification | Problem:
When processing Independent students through the ISIR Verification Wizard, Regent Award users were unexpectedly presented with parent-related questions on Step 2 of the wizard. Cause:
Most causes were previously addressed in the 4.3.0.0 release. However, additional use cases, not originally considered, still caused parent questions to appear when a correction was rejected. Fix:
Logic was modified to separate Dependent and Independent Student questions, including cases where the correction was rejected. Testing:
Find an Independent student and start the ISIR Verification Wizard for an ISIR needing Verification. Ensure that parent-related questions are not presented on Step 2 of the wizard. Follow the same steps for a Dependent student and ensure that both student and parent-related questions are shown on Step 2 of the wizard. |
| RS-12803 | Regent Award | ISIR Processing/Verification | Problem:
In the ISIR Corrections Export file, some lines in the file were unexpectedly blank. Cause:
ISIR Correction records were created, but not exported, in Regent Award prior to ISIR data updates being implemented in the Regent Award database. When the record was then exported after the implementation of the updates, changed data field mapping caused some field mappings to be invalid, creating a blank data set. To summarize, the Correction records created before the system update exported as a blank line when exported after the system update. Fix:
Logic was added to update the database so that valid data mapping is maintained when the ISIR Corrections are made. Testing:
Navigate to a student needing correction. Edit values using the ISIR Verification / Correction Wizard. Mark the corrections for submission to CPS. In Processes, run Export ISIR Correction for the ISIR's FAY. Open the resulting data file from the Process Log. The data file should not have any blank lines. |
| RS-471 | Regent Award | ISIR Processing/Verification | Problem:
Regent Award calculated a different Estimated Family Contribution (EFC) for a student than the EFC calculated by the Central Processing Service (CPS). Cause:
The student's EFC was modified based on Professional Judgment (PJ). Regent Award used a similarly named field from a database table instead of the correct PJ field. The resulting incorrect PJ value miscalculated the EFC amount. Fix:
The Expected Family Contribution calculation logic was updated. Regent Award pulls the data from the correct Professional Judgement field during the ISIR Correction process. Testing:
Access a Dependent student's record and begin the ISIR Verification/Correction Wizard. Decrease the amounts in Field 46, 111, or 112 within the wizard, set Field 165 = Calculation requested. Save the changes and confirm the calculated EFC has decreased correctly based on changes made within the Verification/Correction Wizard. |
| RS-14270 | Regent Award | Packaging | Problem:
Regent Award was unexpectedly throwing a packaging error of Failed to Process. Error Msg: Specified argument was out of the range of valid values. Parameter name: weight must be > 0 after the import of the Ohio State Grant Disbursement Eligibility Query. Cause:
Incorrect logic within Regent Award was in place regarding the import of disbursements within the Disbursement Eligibility Query file that resulted in the error being presented. Fix:
Logic was updated to prevent the error message from occurring after the Disbursement Eligibility Query is imported. Testing:
Import a Ohio State Grant Disbursement Eligibility Query. Package either using Batch Packaging or MAP and confirm the error message is not given for the students listed in the Disbursement Eligibility Query file. |
| RS-14148 | Regent Award | Packaging | Problem:
A BBAY1 Term student was not awarded with the maximum eligible loan amount. Cause:
The student was enrolled less-than-half-time for the first term in the Academic Year. Two problems caused the incorrect loan amounts.
1. Regent Award's "Package to Net Costs" feature was creating an Estimated award for ineligible terms, thereby generating additional loan fees. The incorrect fees caused an incorrect amount for Unsubsidized award.
2. The truncation for the loan period did not occur due to the configured Census Date and Begin Actual Dates. The Subsidized and Unsubsidized loans remained on the two-term loan period. As a result, the system failed to correctly adjust the loan amounts based on another, Non-Title IV award. Fix:
To prevent generating high loan fees, new logic that excluded ineligible terms from estimated awards creation process was implemented. Also a new packaging rule was added to verify the Begin Actual date for the term. Testing:
Package an affected student. Verify that the Unsubsidized Loan's limit reaches to its maximum annual amount. |
| RS-14116 | Regent Award | Packaging | Problem:
When some 2018 Pell Grant awards were exported to COD, the Pell Additional Eligibility Indicator was not set to True for students eligible for Year Round Pell (YRP) funding. Cause:
The packaging engine was not checking the award's Federal Award Year (FAY) when performing the lookup for the additional eligibility amount. The 2018-2019 amount was used due to the existence of a Summer 2018 Award disbursement. Fix:
The packaging engine checks the Pell's award period FAY when setting the Additional Eligibility Flag. Testing:
Navigate to affected students with a Year-Round Pell award. Check the Additional Eligibility Indicator value for Pell Grant in the COD tab. The Additional Eligibility Indicator value should be True. Export the Pell award to COD. Inspect the export file. The file should show the Pell additional eligibility indicator as true. |
| RS-13917 | Regent Award | Packaging | Problem:
Calculated Eligibility amounts for Federal Direct Loans were updating in error when users entered the Modify Award Wizard (MAW), exited the wizard, and re-entered. Cause:
Regent Award was failing to clear the cache when awarding was completed. Fix:
Logic was added that clears the cache after awarding. Testing:
Access a student's Federal Direct Loan via Modify Award Wizard (MAW) and confirm the calculated eligibility. Exit the wizard and then re-enter the wizard. Confirm the calculated eligibility displays the original amount viewed when first entering the wizard. |
| RS-13915 | Regent Award | Packaging | Problem:
When a user edited non-Manual awards in Modify Award Wizard (MAW), Regent Award unexpectedly changed the awards to Manual. The Calculated Eligibility amounts equaled their "New Offer" and/or "Accepted" amounts. Cause:
Regent Award was marking awards as Manual whenever a user changed the "New Offer" amount, regardless of the Calculated Eligibility. Fix:
Logic was put in place to keep the Manual flag as False when an award's "New Offer" or "Accepted" amount equals the "Calculated Eligibility" amount. Testing:
Access the Modify Award Wizard for a non-manual award in Offered or Accepted status. Update the "New Offer" and/or "Accepted" amount to equal the "Calculated Eligibility" amount. Continue through MAW and finish the wizard. Confirm the award is not marked Manual. |
| RS-13903 | Regent Award | Packaging | Problem:
Origination Fees packaged towards Federal Direct Loans during Batch Packaging (BP) were being removed from the packaged loan awards after using the Modify Academic Plan wizard (MAP). Cause:
Regent Award did not clear the cache when awarding was completed. Fix:
Logic was added to clear the cache after awarding. Testing:
Run Batch Packaging and verify the student's awards. Then, run MAP for the student and confirm the award remains packaged with the Origination Fees. |
| RS-13874 | Regent Award | Packaging | Problem:
The system moved paid amounts of OCOG (Ohio College Opportunity Grant) from the Summer 2018 Payment Period (PP) to the Fall 2018 PP. Cause:
The Summer 2018 PP is assigned to the 2017-2018 Federal Award Year (FAY). However, in crossover periods, OCOG must be awarded from the latter year which is 2018-2019. Regent Award moved the OCOG award to the first PP assigned to the 2018-2019 FAY, which was Fall 2018. Fix:
Logic was changed to ensure that OCOG is properly awarded from the latter year FAY for crossover awarding, regardless of the FAY associated to the PP, and that the award will not be moved out of the crossover PP. Testing:
Navigate to the affected student and execute MAP. The system is expected to MAP student without error, and the paid Summer OCOG award will remain on the Summer term. |
| RS-13845 | Regent Award | Packaging | Problem:
For schools using the Package to Net Direct Costs feature, Regent Award was not properly applying loan fees to a Single Term Loan Period. Cause:
After Regent Award packaged the default period, there were remaining fees because both the Sub and Unsubsidized loans were awarded at their aggregate limit. Those fees were not properly considered when awarding the Single Term Loan Period (STLP). Only the fees from the disbursements associated with the term contained within the STLP can be applied to the STLP. Fix:
Logic was updated to ensure loan fees were properly accounted for when awarding the Single Term Loan Period. Testing:
Locate a student where a grade level increase occurred causing a single term loan period for additional loan eligibility. Package the student and ensure the loan amounts include the loan fees. |
| RS-13652 | Regent Award | Packaging | Problem:
"Aggregate" in the following error message was misspelled: "Adjusted award to PackageTo setup option | Adjusted award for yearly aggregate limit | Adjusted award for total aggreagate limit". Cause:
The Regent Award error message was created with an incorrect spelling of "aggregate." Fix:
The spelling of "aggregate" was corrected in the error message. Testing:
Attempt to add a Federal Direct Loan for a student who has already met their aggregate limit. Review the error message that populates and confirm the word "aggregate" is spelled correctly. |
| RS-13597 | Regent Award | Packaging | Problem:
An unexpected error message occurred on Step 2 of the Add Award Wizard (AAW) for the Federal Supplemental Grant: Accepted amount is required for awards whose status is Accepted. Please go to Step one and provided an accepted amount. Cause:
The accepted amount entered in the Add Award Wizard was changed when Regent Award tried to recalculate the award's budget. This issue only appeared for funds associated with a budget. Fix:
Logic has been added to ensure Regent Award does not recalculate the award's budget after moving from Step 1 to Step 3 of the Add Award Wizard. Testing:
Attempt to add a Federal Supplemental Grant via the Add Award Wizard. Once the user is at Step 2, ensure the error message is not presented and the FSEOG is able to be accepted. |
| RS-13339 | Regent Award | Packaging | Problem:
A user added an Unsubsidized Loan through Add Award Wizard (AAW). The Unsubsidized Loan was not added to the Academic Plan after packaging. The user had added a Subsidized loan with AAW immediately before adding the Unsubsidized loan. Cause:
The problem was caused by a timing issue when the user added two awards using AAW. If the first AAW changes had not finished saving to the database when the second award was added, then the second AAW changes were not persisted and the second award could not be saved. Fix:
A code change now waits for DEX persistence when adding awards. A user will not be able to edit data in an additional (second) Add Award or Modify Award Wizard until the current (first) changes to Add Award or Modify Award Wizard are persisted to the database. Testing:
Navigate to an affected student and add a loan via AAW, choosing appropriate Loan Period and entering the Offered amount. The loan should persist on the Academic Plan. Quickly add a second loan via AAW. Package the student using Modify Academic Plan (MAP). The second loan should persist on the Academic Plan of the student. |
| RS-14272 | Regent Award | Process Log | Problem:
The Ohio College Opportunity Grant (OCOG) Disbursement Query was failing upon import due to prior disbursements plus the current disbursements on the Disbursement Query equalling less than $0. Cause:
Incorrect logic was in place for matching of the Ohio College Opportunity Grant to a disbursement record when prior records imported were marked invalid. Fix:
Logic was updated to exclude any prior OCOG imported records that were deemed invalid when matching the disbursements during the Disbursement Query import. Testing:
Import an OCOG Disbursement query via the Import State Grant Process and ensure the import processes successfully and disbursements do not equal less than $0. |
| RS-12866 | Regent Award | Program Change | Problem:
A Non-Substantially Equal (NSE) program change resulted in a duplicate Academic Year being created in Regent Award. Cause:
Before the Program Change, Regent Award assigned an Academic Year to the new program because the student had registration after the old program's completion date. Fix:
Regent Award logic was added to verify whether the Academic Year starts prior to the new program's start date. If the AY starts before the new program, the system will assign that AY to the old program. Testing:
Import a SBL file that contains a program change. Package the student via Modify Academic Plan (MAP). Refresh the student. Process the program change as NSE via Program Management Wizard (PMW.) Confirm the dates of Academic Years are not duplicated. |
| RS-14262 | Regent Award | R2T4 | Problem:
The R2T4 wizard miscalculated Pell amounts for some term-based BBAY students. Cause:
The term was a crossover payment period. During an R2T4 Pell recalculation, the system linked the term to a different FAY than the Pell Grant award FAY. Fix:
When Regent Award recalculates a Pell grant for R2T4, the system links the payment period to the correct FAY. Testing:
Navigate to an affected BBAY term student who has a 2018 Pell award (manual or non-manual) and attendance in the crossover term. Delete or reverse any existing R2T4s. Test creating a new R2T4. Step 1 should calculate the correct Pell amount. Finalize the new R2T4. Package the student. The Pell amounts should be correct. |
| RS-14109 | Regent Award | R2T4 | Problem:
For some students, Pell Grant and Federal Supplemental Grant awards are not being included in the R2T4 calculation. Cause:
In a previous release, changes were made to Regent Award to prevent awards from being included in the R2T4 calculation if the Federal Award Year (FAY) on the Award Period and the Federal Award Year on the Payment Period do not match. Fix:
Logic was added to allow award disbursements for the payment period to be included in the R2T4 calculation regardless of whether there is a mismatch between the award period and payment period FAY value. Testing:
Process an R2T4 for a student whose Pell or FSEOG award for the R2T4 period has a different Federal Award Year than the Payment Period. Ensure that both the Pell and FSEOG awards are populated in the R2T4 wizard. |
| RS-11416 | Regent Award | R2T4 | Problem:
Some SAY term students had Direct Loans with COD Reject codes 045 and 205. The loans had incorrect Financial Award Begin and End dates. The dates were missing the Fall term and unexpectedly included the Summer term. The students had finalized R2T4s in Fall and Spring and had paid Title IV loan disbursements in only the Fall and Spring terms. Cause:
Regent Award did not correctly truncate the loan period dates when the SULA-defined loan periods were shorter than the year-long loan period, and the Title IV loans had $0 disbursements on the full-AY default loan period. Fix:
Regent Award was updated to create a truncated loan period that covers the terms with nonzero Title IV loan disbursements. The loans are linked to the shorter loan period. Testing:
Package an affected SAY student who has finalized R2T4s for both Fall and Spring, has nonzero Title IV loan disbursements in Fall and Spring and has $0 loan disbursements in the Summer term. Inspect the Loans tab, Financial Award Begin and End dates. The Financial Award dates should include all terms with nonzero disbursements, and should not include Summer. Export the loan to COD. Inspect the export file. The Financial Award Begin and End dates should cover the correct terms. |
| RS-8664 | Regent Award | R2T4 | Problem:
Regent Award was unexpectedly throwing an error during R2T4 processing that stated "The Active ISIR transaction has not been packaged" Cause:
Regent Award was preventing the creation of R2T4's within the R2T4 Wizard when the Active ISIR had not yet been packaged, even though this ISIR was not used to package the awards related to the R2T4. Fix:
Logic was updated to ensure the ISIR associated with the awards in the R2T4 period is used when processing the R2T4. Testing:
Navigate to an affected student. Move to the Awards tab, select "Perform R2T4" and add an R2T4 or Modify an existing R2T4. The R2T4 should be successfully updated/created without receiving an error message regarding the latest ISIR transaction has not been packaged. |
| RS-14114 | Regent Award | Reports | Problem:
Social Security Number (SSN) masking in the ISIR-Unmatched report was unexpectedly not respecting the "Full SSN Always Unmasked" permission. Cause:
The ISIR-Unmatched report was utilizing incorrect conditions regarding SSN masking. Fix:
Logic was updated to ensure the ISIR-Unmatched report properly utilizes the SSN masking permission. Testing:
Enable the permissions for View full SSN via "View Full SSN" icon" and "Full SSN always Unmasked." Run the ISIR-Unmatched Report and verify that the SSN is unmasked. |
| RS-13695 | Regent Award | Reports | Problem:
The Task Status Report Summary Grid was not properly reflecting the total number of tasks in each queue/status. Cause:
The query that generates the report was using an incorrect database column for obtaining the Task Status. Fix:
The Task Status Report query was corrected to use the correct database field in order to count the total number of tasks in each queue/status. Testing:
Run the Tasks Status Report and confirm the total number of tasks in each queue/status is reflected correctly in the report Summary. |
| RS-13534 | Regent Award | Reports | Problem:
The Disbursement Information Report was not including non-Title IV funds in the output. Cause:
Incorrect logic in the report unexpectedly joined Common Origination and Disbursement (COD) data and non-Title IV awards. Fix:
The report view was corrected with improved logic for COD data and non-title IV awards. Testing:
Run the Disbursement Information Report for non-Title IV funds and confirm data is populated. |
| RS-13172 | Regent Award | Reports | Problem:
The user saw different paid amounts of Federal Supplemental Grant (SEOG) in Academic Plan and in Award Information Report. Paid amounts did not match. Cause:
The Award Information report contained duplicated data. The duplicate records caused the inaccurate amount of disbursements. The duplicated records appeared because a stored procedure did not correctly link them to fund budget data. Fix:
The report's stored procedure is updated to link correctly with the disbursements. Testing:
Navigate to affected students and compare their paid amount in Award Information Report. The report amount should be the same as in the Academic Plan. |
| RS-12464 | Regent Award | Reports | Problem:
Student SAP report provided student data that was inconsistent with selected parameters for 'Include Historic SAP' and 'NonStandard Term' term type. Cause:
Incorrect data selection criteria were being used by Regent Award to collect SAP records. Fix:
Logic was updated to ensure the data selection criteria collects the requested SAP records based on the parameters selected in the Student - SAP report. Testing:
Run the Student - SAP report with the parameter "Type" = "Non-Standard Terms" and "Include Historic SAP" = "No". Ensure Non-Standard Term student records are provided in the report output. |
| RS-14119 | Regent Award | Runbook | Problem:
Only a subset of students included in NSLDS TSM and FAH data files were being processed when the file was imported into Regent Award. Cause:
Certain symbols in the text in positions 11 through 57 of the NSLDS TSM and FAH data files caused Regent Award to stop parsing the file. Fix:
The import process was updated to allow for any character in positions 11 through 57 within the NSLDS TSM and FAH data files. Testing:
Import an NSLDS TSM and FAH data file using the Import Process. Confirm the entire file is processed and there is not a warning message regarding parsing of the file. |
| RS-13662 | Regent Award | Runbook | Problem:
A school ran Batch Packaging (BP) as a scheduled process to package all students. The Process Log entry showed "Process Active Students Only" set to No. However, Inactive students were not packaged. Cause:
Whenever the system ran Batch Packaging, two separate processes were created. The first process saved the initial process parameters, but did not display them. The system then created an additional, second process when persisting the Batch Packaging data. The Process Log entry displayed results from the second process, which could show different parameters. Fix:
The Process Log entry displays the original process and its associated parameters. Regent Award uses that process for Batch Packaging. The system no longer creates an additional, new process after packaging. Testing:
Locate an Inactive student who has no packaging blockers. Run Batch Packaging as a scheduled process with "Process Active Students Only" = No. The system should package the Inactive student. Review the Process Log entry. The Total records value should reflect packaging for Active and Inactive students. The system should show the correct values for the BP Selection Parameters, including "Process Active Students Only" = No. |
| RS-13380 | Student Portal | Student Portal (SNAP) | Problem:
In the Student Portal, when some students tried to complete their 2018-2019 Verification Worksheet (VWS), they saw an unexpected error: The page you navigated to is no longer required since your answers to previous questions have changed. Please click the menu to the left and navigate to a previous section and click through the process to complete
your application. Cause:
The system did not correctly auto-populate and save some hidden fields, located in a separate tab and not visible to the end user. Fix:
Regent Award has improved the logic for displaying and hiding relevant fields based on questionnaire data. In addition, the system will automatically populate values for hidden fields, if the field is configured to pre-populate, when a student first creates an application. Testing:
Navigate to an affected Dependent student with a 2018-2019 ISIR needing verification, and a Verification Worksheet assigned. Create the student's Portal account. Step through the Verification Worksheet in the Student Portal. The system should allow completion without error. |
| RS-13158 | Student Portal | Student Portal (SNAP) | Problem:
At an Active Acceptance school, in the Student Portal, a student tried to accept an Offered loan at its full current amount. However, a validation message prevented the student from accepting the full amount. The amount in the error message was the Calculated Eligibility. Cause:
The award was a manual award that did not have the "Override Eligibility Rules" selected when it was awarded to the student. The Portal's validation unexpectedly checked for the calculated eligibility instead of the current amount on the award. Fix:
The portal validation was corrected to check for the current amount of the award for a manual award that did not have "Override Eligibility Rules" selected during awarding. Testing:
Use a student with an affected manual Offered loan in a current award period, with the loan's current amount higher than the calculated eligibility and with the "Override Eligibility Rules" checkbox unselected/unchecked. Create a test account for the student on the Student Portal. Log in and navigate to the loan. Try to accept the loan at its full amount. The Portal should allow the loan to be accepted at the full amount. The student should not see any validation error for a different amount. |
| RS-12995 | Regent Review | Student Portal (SNAP) | Problem:
The Drug Conviction Worksheet did not persist the document and update the document status upon the completion of the Verification Worksheet Smart Form. Cause:
Smart Form logic was not reading documents that are not configured as a Smart Form type. Fix:
Updated the Smart Form logic to persist the document and update the status for documents that are not configured as a Smart Form type. Testing:
Navigate to an affected student. Ensure that the Drug Conviction Worksheet/C Code document pre-populated for the student upon ISIR import into Regent Award. Complete and E-sign the Verification Worksheet Smart Form. Confirm the Drug Conviction Worksheet/C Code document persisted and that the document status was updated to a 'Received' status. |
| RS-12651 | Regent Review | Student Portal (SNAP) | Problem:
The Student/Parent Income and Tax Data page of the ISIR Verification worksheet had incorrect wording: "I will not file and are not required to file" Cause:
A text misprint occurred at Student/Parent Tax and Income page. Fix:
The wording was corrected to say "I will not file and am not required to file" Testing:
Find a student who has a Verification Worksheet. Login to the Student Portal. Open 2018-2019 Verification Worksheet. Proceed to Income & Tax Data section. Verify that Nontax Return Filters block contains the correct wording. |
| RS-14014 | Regent Award | Tasks | Problem:
Batch Packaging generated a higher than expected number of Review Eligibility Change tasks. Cause:
The Year Round Pell code omitted some situations where Pell should have had different calculated eligibility amounts. The system generated extra Review Eligibility Change tasks, based on incorrect amount calculations. Fix:
The Year Round Pell calculations were improved to better consider AY0/R2T4s, reducing Pell to calculated payment period amounts, and applying Pell Lifetime Eligibility Usage limits. The new logic calculates more accurate Pell amounts. The corrected amounts reduce the number of unnecessary Review Eligibility Change Tasks. Testing:
Run Batch Packaging and confirm the Review Eligibility Change Tasks number is not increased by a significant amount. |
| RS-14297 | Regent Access | User Interface | Problem:
The "Recent Activity" section on the Student Summary Tab was unexpectedly not providing any data. Cause:
Changes made to enhance Activity Log entries caused the "Recent Activity" section on the Student Summary Tab to no longer reflect any information. Fix:
Logic was updated to ensure the "Recent Activity" section displays the most recent information from the Activity Log. Testing:
Access a student and review the "Recent Activity" section at the bottom of the Student Summary Tab. Confirm data is provided in the section. |
| RS-14294 | Regent Award | User Interface | Problem:
Users could not access the Academic Plan tab, Awards tab and Student Details tab with Academic Information section for some students. Cause:
An error in the code did not properly account for cases where a term was deleted from a student's academic plan, but only in those cases where the deleted term was designated as "Completed SAY?" = true in Term Setup. Fix:
The logic was modified to properly account for the deleted terms for the affected scenario. Testing:
Navigate to an affected student. The system will load the Academic Plan tab, Awards tab and Student Details tab with Academic Information section. |
| RS-12372 | Student Portal | Workflow/Questionnaire | Problem:
When a student opts out of the e-signature process, the option for the parent to e-sign is still displayed and the parent is still allowed to e-sign. Cause:
The e-signature button was displaying for the parent when a student paper-signed their application/document. Fix:
Logic was updated to ensure the e-signature button does not display for the parent when a student paper-signed the application/document. Testing:
Find a dependent student, selected for Verification and complete the Verification Worksheet Smartform as the student. Ensure that the student paper-signs the application/document and the option for parent to e-sign does not display. |