| | | |
---|
RS-24908 | Regent Award | Communications | Problem: The ‘Missing Information’ Standard Communication filter unexpectedly did not find students meeting the selection criteria. Cause: The filter logic had an additional, extra check that used an unrelated table in the database. Fix: The unnecessary check was removed. Testing: Confirm a student meets the criteria for the ‘Missing Information’ filter. Configure the ‘Missing Information’ Communication as Active. Navigate to Processes → System → Generate Communications. Select the ‘Missing Information’ Communication Template and Generate. Review the Process Log, Students tab. Confirm the student is selected. |
RS-24816 | Regent Award | Packaging | Problem: After a COD Export and Import, when a school ran the ‘Export Student Transactions’ (EST) process, almost all students were prevented from disbursing with an error, EST-0059, The student is queued for packaging and disbursements cannot be determined at this time. Cause: The system interpreted the COD Response File import as a change that required the students to be repackaged. Fix: Regent’s logic was adjusted to not mark a student as needing repackaging after importing a COD Common Record Response (RS file type), when the student had no other changes to data. Testing: In at test environment, package a student with one or more unpaid, past scheduled COD disbursements. Export the disbursements for EST with DRI=True. Export to COD. Mock a simulated COD response acceptance, using the COD file from the Process Log. Import the mocked COD response. Export disbursements for EST for Accounts Receivable (EST for AR). Confirm the disbursements are exported without the EST-0059 error. |
RS-24791 | Regent Award | Packaging | Problem: Student was blocked for packaging due to 'Leaner has remaining reconciliation Academic Year with communicated awards' error. Cause: Regent Award failed to correctly reuse AY in reconciliation validation. Fix: The logic was updated to check for and match to an Academic Year prior to the creation of a new Academic Year. Testing: Find the affected student. Run packaging. No errors should occur during the packaging process. |
RS-24756 | Regent Award | EST/Disbursements | Problem: A disbursement schedule required attendance. For some students, the Export Student Transactions (EST) process unexpectedly exported students who did not have attendance in the term. Cause: A recent code change had referenced an incorrect table, which prevented logging the EST validation errors and surfacing the error messages. Fix: The code was corrected and the EST validation errors are preserved. Testing: Test with a student who has a scheduled past disbursement and no attendance in a term, using a fund and disbursement schedule that need to have attendance for disbursement. Run the EST process. Review the Students tab or the test student’s Activity Log, or view the Disbursement Details pop-up errors tab. Confirm the error messages appear as expected. |
RS-24742 | Regent Award | Workflow/Questionnaire | Problem: The 2023-2024 Verification Worksheet (VWS) questions for non-tax-filers referred to the 2020 tax year filing requirements instead of the 2021 tax year filing requirements. Cause: The non-tax-filer text updates were missed in the annual updates list for 2023-2024. Fix: The tables and text were updated for the non-tax-filer questions for the Student, Spouse, and Parent questions in the 2023-2024 VWS. Testing: In a test environment, load the updated Verification Worksheet for 2023-2024 and ensure it is Active. Find two non-tax-filer students, one Dependent, and another Independent with a spouse, who need Verification. Confirm the students have the Verification Worksheet Student Document Requirement in Needed status. Create a test account for the students on the Student Experience Portal. Navigate to the Student Documents area. Click through the VWS to the Income & Tax Data section. Confirm the VWS displays the 2021 Filing Requirements Chart for Most Taxpayers. |
RS-24732 | Regent Award | Packaging | Problem: The system unexpectedly awarded some Subsidized and Unsubsidized loans above the student’s maximum aggregate limits, for students who had recent loans that were partially paid. Cause: The system incorrectly processed some NSDLS data and Regent loans when calculating the aggregate amount usage. Fix: The application correctly calculates aggregate amount usage during packaging. Testing: Test with a student who is near their Subsidized or Combined lifetime aggregate limits, has some recent loans that are partially paid but not fully paid, and also has projected half-time or greater projected future enrollment for several future Academic Years. Load NSLDS FAH data or use a most recent data source with an effective date dated within an AY when some loans are partially but not fully paid. Clear all packaging blockers. Package the student such as by using the Modify Academic Plan wizard (MAP). View the History tab, General sub-tab. Confirm the Regent column displays the aggregate values. MAP the student. View the student’s Academic Plan. Confirm the student is awarded with Subsidized and Unsubsidized loans to their aggregate limits for current and future years. Confirm the student is not awarded with any extra loans exceeding the student’s maximum aggregate limits. |
RS-24728 | Regent Award | Packaging | Problem: The system unexpectedly ignored some user-entered ‘Loan Override Aggregate Amount’ values in the ‘Loan Aggregate Detail’ in the History tab. Cause: In some cases, the system bypassed the Override amounts when adjusting student-level aggregate amounts for awarding. Fix: The system was corrected to always apply the Override amounts. Also, the system will not make additional adjustments for Pending Disbursements for loans with a value for the Loan Override Aggregate Amount. Testing: Test with a student who is near their Subsidized or Combined lifetime aggregate limits, and has projected half-time or greater projected future enrollment for several Academic Years. Clear all packaging blockers. Package the student such as by using the Modify Academic Plan wizard (MAP). View the History tab, General sub-tab. Confirm the Regent column displays the aggregate values. In the History sub-tab for Loan Aggregates, edit the ‘Loan Override Aggregate Amount’ column and enter several override values. Save. MAP the student. View the History tab, General sub-tab, and Refresh. Confirm Regent is using adjusted totals. View the student’s Academic Plan. Confirm the student is awarded with Subsidized and Unsubsidized loans to their adjusted aggregate limit. |
RS-24671 | Regent Access | Student Experience | Problem: Regent was not accurately rendering some special characters in the Spanish Translation Instructional text. Cause: Regent was using ASCII encoding of string to bytes for publishing settings. Fix: The Student Experience Portal is updated to use UTF encoding instead of ASCII. Testing: In a test environment, configure the Dashboard Settings, Instructional message text with text including the Spanish translation text. Publish the configuration. Create a test account and log into the Student Experience Portal. Confirm the Instructional Text is displayed correctly. |
RS-24668 | Regent Award | ISIR Processing/Verification | Problem: After upgrading, the system unexpectedly downloaded all active message class types from the Student Aid Internet Gateway (SAIG). The system did not apply the Saved Parameter sets that normally limited downloads to only specific Message Class types configured as Active. Cause: A user interface change in the 6.1.0.0 release, intended for the Pell Multiple Reporting Record (MRR), accidentally caused the system to not apply any saved parameter sets for SAIG files. The system did not check the configuration for active SAIG message classes. Instead, it downloaded all Message Classes. Fix: The problematic change was reverted and replaced with improved code. The new logic also re-added the Pell MRR as a supported process type similar to other SAIG message classes. Testing: In an environment connected to SAIG (preferably a SAIG test mailbox), confirm the SAIG Parameter Set is configured. Download the files. Confirm the system does not automatically download any extra Message Classes that are not configured as Active. |
RS-24665 | Regent Award | EST/Disbursements | Problem: Regent Award unexpectedly paid 0.01 Pell disbursements a few months after scheduled date. Cause: Regent Award incorrectly calculated amount verified for EST DRI when the disbursement schedule had "Incrementally Disburse on Enrollment Level By Unit Type = Attended Census PA Units" option. Fix: The logic was updated to correctly calculate the amount verified for EST DRI in this case. Testing: Find the affected student with scheduled disbursements at current term. Make sure that no blocking tasks/documents are assigned. Run EST-for-DRI. All disbursements should be picked up for EST. |
RS-24620 | Regent Award | R2T4 | Problem: Regent Award was incorrectly calculating the amount of Plus Additional amounts to Return and the Total Amounts to Return in R2T4. Cause: Regent Award was incorrectly calculating R2T4 Step 6 "Additional amount to return" fields based on the period disbursements. Fix: Regent Award is updated to correctly calculate R2T4 Step 6 "Additional amount to return" fields. Testing: Complete R2T4 for a student where Step 1 should have a Net Amount Disbursed value and Net Inadvertent Overpayments = $0. In Step 6, Plus Additional Federal Unsubsidized Direct Stafford Loan to Return should not be affected by the Net Inadvertent Overpayments because it is $0. |
RS-24548 | Regent Award | Packaging | Problem: Regent Award unexpectedly updated existing Loans after adding Manual AY with single term Loan Period in Program Management Wizard. Cause: Regent Award incorrectly packaged a new manual loan period added by a user before the existing default one. That caused creation of new loans and canceling/decreasing of the existing loans in the default loan period. Fix: Regent Award is updated to ensure the packaging of the default loan period before a new one. Testing: Attempt to add a one-term loan period using Program Management Wizard in Regent Award, then check loan amounts. |
RS-24473 | Regent Award | Awarding | Problem: Add Award Wizard did not allow adding specific Awards for students. Students were receiving an error that stated, “Fund (Fund name) is not available for Program (Program name)." The program listed in the error was a previous program and not the student’s current active program. Cause: The Program was not associated to a specific Fund, so that system did not allow adding manual funds to students. Fix: The code fix was applied so that it will be possible to add Manual Awards in such a case. Testing: Navigate to an affected student. Add the Award. Confirm the error does not occur. |
RS-24456 | Regent Award | Packaging | Problem: Regent Award incorrectly calculated the remaining units in the latest Academic Year. Cause: Regent Award was incorrectly applying the ProgramApplicableOverageUnits to the Anticipation calculation twice. Fix: Regent Award is updated to remove redundant ProgramApplicableOverageUnits addition. Testing: In Regent Award, search for a student who has completed more than anticipated units for the first term of AY. Check anticipated units for the next term, which must be in the last AY. |
RS-24360 | Regent Award | Awarding | Problem: Regent Award was incorrectly calculating Pell when an award year transformed from 2 PPs into 1 PP. Cause: Regent Award incorrectly used academic year weeks from Program Setup instead of registered ones in Pell Formula 4 when a student had fully registered in a single PP AY. Fix: Regent Award is updated to use the registered weeks in this case. Testing: In Regent Award, package a student with Pell who has Award Year transformed from 2 PPs into 1 PP. |
RS-24279 | Regent Award | R2T4 | Problem: The Declined loan is not set back to Declined status when the R2T4 is reversed in Regent Award. Cause: Regent Award was not saving Award Statuses prior to R2T4 Finalization. Fix: Regent Award is updated to add a new Award property, PreR2T4AwardStatusCode, for saving the Award's status before R2T4 Finalization and using it when R2T4s are Reversed. Testing: In Regent Award, reverse R2T4 for a learner who returned in a non-term program and has Declined loans before R2T4. |
RS-24206 | Regent Award | Packaging | Problem: Regent unexpectedly created 2 subsequent Academic Years with the same start/end dates when NSE program change took place. Cause: Regent award duplicated Academic Years due to unexpected non-term to term NSE program change processing results. Fix: Logic added to prevent the duplication of AYs at academic plans for term-based programs. Any duplicated terms on the plan and terms that are subsequent will be moved to reconciliation to allow the plan to rebuild out properly. Testing: Find the affected student. Perform NSE program change. Run the packaging. Verify Academic Plan structure. No duplicate AYs should be present. |
RS-24166 | Regent Award | EST/Disbursements | Problem: Regent award was not able to link the disbursement schedule to manually added award in 'PAID' status. As a result, negative EST-for-AR transaction failed with EST-0066 error code for manually added Golden State Teach Grant although the disbursement schedule was present. Cause: Regent Award failed to properly assign disbursement schedule ID for Golden State Teach Grant. Fix: System checks were updated to prevent the creation of empty disbursement schedule IDs. Testing: Find the affected student. Reduce the award and disbursement amount via MAW for Golden State Teach Grant and afterwards process that reduction via EST-for-AR. No EST-0066 override code should occur. |
RS-24137 | Regent Award | Awarding | Problem: Regent Award unexpectedly did not prorate undergraduate loans in a Final AY for several Scheduled Award Year (SAY) students who would graduate before the end of the AY with a shortened remaining period of study (RPS). Cause: Regent Award calculated the annual-limit proration using the units from an incorrect Loan Period. Fix: Regent Award is updated to ensure to allow the awards to be processed on the correct eligible terms in the correct Loan Period. Regent calculates the correct proration of the annual limit amount using the units in the Loan Period only. Testing: In Regent Award package the affected students with current or future loans. Confirm the annual limits are applied with prorated amounts. If any students have prorated Subsidized loan amounts that were also limited due to Aggregate usage, confirm the system also awards the Unsubsidized loans to the prorated annual limit total. |
RS-24135 | Regent Award | Communications | Problem: Regent Award was unexpectedly unable to load Student SAP data, causing SAP Warning and Suspended Email Communication process to fail. Cause: The Historical Student SAP records are simulating ones. We do not have Historical SAP detailed information and we tried to load this from the database which caused an issue. Fix: Regent Award is updated to skip including Historical SAP records to the Communication Templates for now. This gap will be fixed in upcoming releases. Testing: In Regent Award generate Communication - SAP Warning and Suspended Email process. Make sure there are no students with Student Failed: Unable to load Student SAP data. |
RS-24067 | Regent Award | Configuration/Setup | Problem: Some user roles with the ‘View Communications’ permission could not see student Communications. Cause: The user interface for the Student Communications tab had a run-time error in the code for the ‘View Notifications’ permission. Fix: The code was corrected. Testing: Sign into Regent using an account with a User Role that has permissions enabled for ‘View Student Communications Tab’ and ‘View Notifications,’ where the Role does not have the permission enabled for ‘Generate Notifications.’ Navigate to a student who has at least one past Communication. View the Communications tab, Notifications sub-tab. Confirm the Communications are visible. |
RS-24036 | Regent Award | User Interface | Problem: Regent Award did not allow removing a Fax Number from Institution, Campus, or Site levels. Cause: Regent Award was incorrectly passing null as a store procedure parameter when a user removed a fax number. Fix: Regent Award is updated to ensure that a null check is added in a stored procedure. If there is a null value then use blank to update a value. Testing: Remove a Fax Number, save changes, and refresh tab in Institution Setup, Campus Setup or Site Setup tab. |
RS-23979 | Regent Award | Packaging | Problem: Regent Award unexpectedly updated students where a SAY program starts in 2021 or 2022 but the Academic Plan incorrectly updates to start with Winter 2009. Cause: Regent Award incorrectly processed terms of the old program after a program change and sometimes added them to the plan. Fix: Regent Award is updated to correctly process terms of an old program. Testing: In Regent Award add a SAY program to a student and then package the student. |
RS-23918 | Regent Award | R2T4 | Problem: Regent Award incorrectly included a Subsidized Loan amount that was increased after course drop in “Could Have Been Disbursed” amount for R2T4. Cause: Regent Award incorrectly considered paid LTHT periods as eligible and awarded them with paid and unpaid disbursements. Fix: Regent Award has been updated to cancel unpaid disbursements for LTHT periods. Testing: In Regent Award, package a LTHT student with an increased Subsidized Loan amount after the drop of their first course. Perform R2T4. |
RS-23875 | Regent Award | R2T4 | Problem: A nonterm student had an R2T4 with higher than expected ‘Could Have Been Disbursed’ amounts in Step 1. Cause: The application used the current eligible amount instead of the COD Accepted Amount when the "Date used to consider non-rebuild loans as originated" setting was "COD Initial Export Date." Fix: The application uses the COD Accepted Amount for Step 1 when the "Date used to consider non-rebuild loans as originated" setting is "COD Initial Export Date." Testing: Create an R2T4 for the affected student. Review the Step 1 amounts for ‘Could Have Been Disbursed.’ Confirm the amounts are calculated as expected based on the COD Accepted Amounts on the loans. |
RS-23833 | Regent Award | Awarding | Problem: Add Award Wizard (AAW) Step 1 was unexpectedly offering only the current and future loan periods. The previous loan periods in the FAY were missing from the loan period selection menu. Cause: Regent Award only allowed adding a new award for the current or future loan period. Fix: Regent Award was updated to ensure that a new award may be added to a past loan period if the loan period is still for a current FAY. Testing: Testing may need a time machine, with the server set to a date (such as mid-June) that is after the end of a previous term, but before the end of the FAY (June 30). In Regent Award, Awards tab, use Add Award Wizard. Select a past loan period that ended before the server date, but within the same FAY as the server date. Confirm the loan can still be added successfully. |
RS-23806 | Regent Award | COD | Problem: Regent Award incorrectly exported Pell to COD with cents when the rounding was to 'Dollar' at Fund Setup. Cause: Regent Award didn't round the R2T4 PWD gross amount according to the fund setup when the fund had no fees (like Pell Grant). Fix: The system's logic was updated to properly round the R2T4 PWD gross amount and the disbursement gross/net amounts according to the fund setup. Testing: Make sure that Pell fund has Rounding set to 'Dollar'. Find the affected student having R2T4 with PWD result code. Finalize R2T4. Run packaging. Review award amounts on AP. The dollar amounts should be showing. Make COD Export. Review exported Pell amount. Pell should not be showing cents but only dollars as per fund setup. |
RS-23774 | Regent Award | Packaging | Problem: When a nonterm student was Batch Packaged, the student’s Academic Plan unexpectedly shifted to put their Substantially Equal Program Change to have the new program start in an incorrect payment period in the following AY, AY2. When staff used Modify Academic Plan wizard (MAP), the Academic Plan was corrected to start the new program in AY1. Cause: The sort of courseenrollments was incorrectly nondeterministic in reconcileacedmicplan method, causing changes in the order in which they were processed between different package runs. Fix: Regent Award is updated to add an additional ordering by CEP.ProgramStartDate when CEP.ActiveOnDate is the same between two different CEPs. Testing: Navigate to the affected student and confirm the student has no packaging blockers. Package the student using Batch Packaging. View the Academic Plan and Refresh. Confirm the Academic Years are correct. Confirm the student’s new Program starts in the payment period matching the new program’s start date. Use Modify Academic Plan wizard. Confirm the student still has the expected Academic Years and program start. Repackage the student several times using Batch Packaging. Confirm the student’s Academic Plan is still as expected. |
RS-23712 | Regent Award | COD | Problem: Single Term Loans unexpectedly caused COD 205 & 222 Rejects if awards were once multi term but had been reduced to single term due to R2T4 or accelerated program completion. Cause: Regent Award incorrectly referenced the table in the COD Export code. Fix: Table reference in the COD Export code has been corrected. Testing: Process COD export and send file to COD after a previously two-term award is reduced to one term in Regent Award. |
RS-23602 | Regent Award | Packaging | Problem: Regent Award was unexpectedly awarding additional disbursements to some terms with Direct Loans and Less Than Half Time (LTHT) enrollment levels. Cause: Regent incorrectly allowed an eligible amount to be increased for a LTHT enrollment that had a previously paid disbursement. The issue occurred for some scenarios when enrollment changed in other later terms on the award, and Regent tried to move amounts into the LTHT term, and the fund was configured to “Award Full Eligibility for Eligible Periods Only.” Fix: Regent Award is updated to ensure a limited eligible amount of the gross amount of the paid disbursements on the payment period for a LTHT term. The change prevents an increase of eligibility on the LTHT payment period. Testing: Test in an environment configured with Subsidized and Unsubsidized loans as ‘Award Full Eligibility for Eligible Periods Only’ = True. In Regent Award, package an affected student with a current active loan in a LTHT term. Or, alternatively, use a student who has a current or future loan with some paid disbursements paid in an earlier term, and has future terms with unpaid disbursements; change the test student’s course data to less-than-half-time enrollment for all the terms. Package the students. Confirm the system does not increase the existing loan amounts in LTHT terms above the paid amounts. Confirm the system zeroes out amounts in future, unpaid, LTHT terms. |
RS-23529 | Regent Award | R2T4 | Problem: Regent Award didn't auto-populate the Net Amount Accepted for Pell in R2T4 PWD Tab. The amount was $0. Cause: Regent Award was not setting the PWD Accepted Amount or the PWD Total Accepted fields for Pell on the PWD tab. Fix: Regent Award is updated to set the Pell values for the PWD Accepted Amount and the R2T4 PWD Total Accepted fields. Testing: In Regent Award, find a student with a Pell grant that is not fully paid. Complete an R2T4 resulting in a PWD. Check the Net Amount Accepted for the Pell. Confirm the system displays the amounts. |
RS-23344 | Regent Award | Awarding | Problem: Regent Award was unexpectedly receiving an error, "Object cannot be cast from DBNull to other types." The error occurred in the Adjust Resource Wizard for one student who had resources that were imported. Cause: An imported resource had a null (empty) value. Regent Award was returning the null data from the database in the Amount field, which was not allowed by the system. Fix: Regent Award is updated to allow a null value in the Amount field in the database. A separate data-cleanup script resolves the affected student. Testing: Find the affected student who had a resource that was imported with a null value in the Resource’s Amount field. In Regent Award, navigate to the Adjust Resource Wizard. Confirm the Resources can be added and edited successfully. |
RS-22965 | Regent Award | Awarding | Problem: 21-22 FAY loans Declined by the student were moved to Cancelled status after the R2T4 was Finalized, and moved to Offered after R2T4 was reversed Cause: The Reversed R2T4 changed the loan status back to the fund’s initial status of Offered. Fix: The system saves a Declined award’s Declined status when the R2T4 is Finalized. When a user Reverses the R2T4, the system has additional checks for the fund being a Title IV award and also checks the flag for ‘Auto Cancel Excluded Title IV Disbursements for R2T4.’ The system keeps the award in Declined status. Testing: Find an affected student with a Declined-status loan and an Open R2T4. Process the R2T4 and Finalize it. Run packaging. Verify the loan status. The Status should remain as Declined. Reverse the R2T4. Run packaging. Verify the loan's status. The loan should stay in Declined status. |
RS-22809 | Regent Award | Packaging | Problem: YRP was not awarded at eligible Summer 2022 term. Cause: Regent Award incorrectly calculated YRP amount when there was an external Pell award and LEU close to 600%. Fix: The system logic was updated to handle Pell amount properly when LEU is close to 600% Testing: Find the affected student. Run packaging. Review term YRP amounts. When 100% of Regular Pell is packaged the system should award additional YRP without any issues. |
RS-22350 | Regent Award | Reports | Problem: The ‘Student - Activity’ report did not display. The screen said “Loading….” but remained blank. Cause: The report had a parsing issue and had a problem displaying fields when some additional data was loaded from the database. Fix: The code was updated to correctly parse the data and process the fields. The report displays as expected. Testing: Navigate to the ‘Student - Activity’ report. Select the parameters. Confirm the report is displayed as expected. |
RS-17471 | Regent Award | User Interface | Problem: Regent’s Quick Search unexpectedly showed a ‘Failed to get reader’ error when a user clicked in the student Quick Search box, the first time the user logged into Regent during each session. Cause: Regent was looking for data from the Dashboard Recent Activity data and the student Watch List for populating the Quick Search results. Fix: Regent is updated to better handle the Dashboard Recent Activity data and the Watch List without error. Testing: Access Regent using an affected user account that can search for students. Click on the Quick Search box in the top right corner. Confirm the ‘Failed to Get Reader’ error does not occur. Confirm the user can successfully find students using Quick Search, without error. |
RS-16237 | Regent Award | Awarding | Problem: Regent Award was unexpectedly packaging Academic Plan with two payment periods in remaining period of study for a student with remaining units for Program completion of less than half of Program defined AY units. Cause: Regent Award was incorrectly marking anticipated AY as isPostProgramCompletion and incorrectly anticipated the PP2, which is not required. Fix: Regent Award is updated to ensure that, when processing AY/Enrollments on prior years, anticipated AY being set as post-program completion stops when remaining units = 0 and that there is no call to calculate anticipation. Logic check also added into createNTpaymentperiods when PP1's CE has enough progression to complete program and no CE exists for PP2. Testing: In Regent Award, package a student with remaining units for Program completion of less than half of Program defined AY units. |
RS-24790 | Regent Fund | Packaging | Problem: Processing Delays after enabling Regent Fund/Enable Real-Time Data Update Cause: Inefficiencies in real-time cache logic. Fix: Updates were made to the caching process to mitigate performance issues. The logic was updated to be more efficient when: Inserting new Cache Data batches Updating Cache Data batches Closing failed Cache Data batches Closing out the log for sets of students where data was cached or an error occurred while caching data
Testing: Enable Regent Fund/Enable Real-Time Data Update. Ensure process delays do not occur. |
|
|
|
|