Page Properties | ||||
---|---|---|---|---|
|
Executive Summary
Regent Education is pleased to announce Regent 6.8.1.0, the latest release of the Regent Enterprise Financial Aid Management System.
The release includes enhancements listed in the 'Enhancements' section below and further defined in the Product Brief. This release also addresses product defects as listed in the 'Bugs' section below.
New/Updated Configuration Options
Expand |
---|
The following configuration options were added or updated in release 6.8.1.0: N/A |
Admin and User Guide Updates
Expand |
---|
As part of Regent 6.8.1.0, the following Admin and User Guide pages were added/updated. |
Enhancements
The following enhancements are included in this release:
Key | Product Selection | Functional Area | Release Note | ||||
---|---|---|---|---|---|---|---|
Regent Award | Communications | Title: Update the SAP Warning and SAP Suspended Communication Filters to Support Text Messaging Tickets: RS-28339; RS-28340; Description: | |||||
Regent Award/Review/Access | ISIR Processing/Verification | Title: ISIR Corrections: Updated Export File Content for 2024-2025 Changes Tickets: RS-27991; RS-28211; RS-28035; Description: | |||||
Regent Award | AwardingPackaging | Title: New Data Views Created for Unmatched Import Student Documents Update the Maximum Number of Units Allowed for the Registered Units and Quality Points fields for Courses Tickets: RS-28195; RS-2807728093; Description: A new Data View 'dataExtract_UnmatchedImportStudentDocuments_View' was created to identify students that are imported from the Florida Master Eligibility List (MEL), where the imported record did not match to an existing student record in Regent. | Regent Award | Packaging | Title: Update the Maximum Number of Units Allowed for the The Registered Units and Quality Points fields for Courses Tickets: RS-28093; Description: | ||
Regent Award | COD | Title: Add COD Message Class for CRCS25OP to Message Class Setup Tickets: RS-27920; RS-28035; Description: The ‘2025Credit Status Change Acknowledgement’ Message Class, CRCS25OP, has been added to SAIG Mailbox Integration in Regent for 2024-2025. See Customer Zone Knowledge Base topic Message Classes Supported by Regent Award. | |||||
Regent Award | Awarding | Title: Update FWS Management Display Tickets: RS-27754; RS-27514; RS-27968; RS-27969; RS-27969; RS-27970; RS-27971; Description: The Federal Work Study tab on the student record in Regent has been updated to display earnings by Calendar Year, by FAY, and by Payment Period, based on filter selections. | |||||
Regent Award | COD | Title: Change Rounding Procedure in Federal Work Study COD Export Tickets: RS-28035; RS-27103; RS-28171; Description: |
Bugs
The following bugs are resolved in this release:
Key | Product Selection | Functional Area | Release Note |
---|---|---|---|
Regent Award | Packaging | Problem: Cause: Fix: Testing: | |
Regent Fund | Packaging | Problem: Cause: Fix: Testing: | |
Regent Award | Account Management | Problem: Two SAP communications targeted for different review periods are generated within the same SAP review period. The SAP communication from the previous SAP review period (Fall 2023) is generated together the SAP communication of the current SAP review period (Spring 2024) that causes the confusion among students Cause: The system was incorrectly generating multiple communications for students with different statuses in their records. This happened because both the SAP Warning and SAP Suspended communications were being triggered at the same time when a student's status was updated, even if it didn’t apply to both statuses. Fix: The logic of the system was updated to ensure that SAP communications are only sent when a student's status matches the specific criteria for that communication. Going forward, SAP Warning communications will only be sent if the status is updated to "Warning," and SAP Suspended communications will only be sent if the status is updated to "Suspended" or "MTFSuspended." Testing: Find the affected student. Review the communications. There should not be multiple SAP communications in one review period | |
Regent Award | Configuration/Setup | Problem: Error received in Regent Award, in Modify Academic Plan Wizard: Failed to Process. Error Msg: Supplemental file [file name] was not found. Cause: References remained to 2025+ SuppEx file that did not exist. Fix: Replaced references to non-existant SuppEx file. Testing: Find affected student. Confirm MAP runs without errors. | |
Regent Award | Awarding | Problem: Regent Award reduced the eligibility of ‘HU Military Appreciation Grant - 10% fund’ both for paid and scheduled awards for unknown reason. Cause: Regent Award incorrectly applied package to ‘% of additional COA’ logic to the custom funds. Fix: The logic was improved to manage the fund’s eligibility properly with ‘% of additional COA’ option. Testing: Find the affected student. Run packaging. Make sure that the custom fund is awarded to the % of additional COA requirements. | |
Regent Award | Packaging | Problem: Batch Packaging failed with error “Failed to load student data while reading "Course Enrollment" record set.” Cause: Issue was caused by a bug in the logic that loads CE data into Regent’s packaging engine. Fix: Regent was updated to only consider courses that relate to a CE when loading CE data into Regent’s packaging engine, and also to not load data for programs where the program change was skipped, to fix gap with assumption that all packaging processes are under the same Institution, and to ensure the CE data returned to the packaging engine is distinct. Testing: Run Batch Packaging for impacted student. Confirm error is not received. | |
Regent Award | Awarding | Problem: In Overlapping Academic Years (OAY) terms, Regent cancelled and recreated Federal Direct Subsidized Loan after each packaging. Cause: Regent took into account enrollments which were prior to anchor. Fix: The code fix was applied not to take into account enrollments that are prior to anchor so that Regent will package students having OAY with eligible loans' amounts. Testing: Navigate to affected student, package and make sure that students are packaged with eligible loan amount. Packaging should be done two times due to the incorrect award being process prior to the correct OAY. | |
Regent Award | COD | Problem: Regent Award unexpectedly exported to COD a Direct Loan Cost of Attendance amount lower than the calculated COA. Cause: COA was not calculating if the field already had a value and the award amount did not change. Fix: Added condition to calculate COA if the current value is 0. Testing: Find the affected student. run COD export Make sure that the Direct Loan Cost of Attendance is not 0. | |
Regent Award | Packaging | Problem: Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: | |
Regent Award | ISIR Processing/Verification | Problem: Cause: Fix: Testing: | |
Regent Award/Review | ISIR Processing/Verification | Problem: Cause: Fix: Testing: | |
Regent Award | Packaging | Problem: When the ‘Package Using Actual Loan Fees’ setting in Institution/Campus Setup is enabled, Regent Award did not calculate fees for Title IV loans and fees did not display in COA when there were multiple Title IV funds set up with the same Official Fund Type. Cause: When ‘Package Using Actual Loan Fees’ is enabled, the system-generated cost items for calculating actual loan fees should correspond to each of the four Title IV Loans. When there was more than one Title IV fund of the same type, a Cost Item was created for only one of the funds of that type. Fix: A script will create a Cost Item in Cost Group ‘Calculated Title IV Loan Fees’ for each Title IV fund for the client, where more than one Title IV fund with the same Official Fund Type exists. Testing: Run script for this ticket. Verify Cost Group ‘Calculated Title IV Loan Fees’ includes cost items that correspond to each Title IV fund in Fund Setup. Find the affected student and run packaging. Make sure Loans fees display in COA. | |
Regent Award | Student Experience | Problem: Cause: Fix: Testing: | |
Regent Award | Student Experience | Problem: For a 2024-2025 Regent Access application, the SAI was missing for a Dependent student, both on the PDF of the application and in the generated Communication email (the system unexpectedly omits the SAI sentence in the email output.) Cause: When determining whether EFC/SAI calculation should be suppressed or not, Regent Award pulled the wrong user record and that caused incorrect display in the email output. Fix: The logic was updated to pull correct user info for SAI display, Testing: Complete a 24-25 Access application for the affected student. Review the PDF prior to signing. Review the incoming “Application Submitted” email. Confirm SAI is shown. | |
Regent Award/Review | Packaging | Problem Some students the system did not package it resulted withith error: “Unable to package student (RNA.PackageStudent): Failed to Process. Error Msg: Sequence contains no elements“. Cause The system was checking the awards disbursement and rounding the amount but for the reported students there were no disbursed awards and it caused the error. Fix A code fix was applied so that now the system will not give an error. Testing Navigate to affected students and ensure that they are packaged without error. | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: | |
Regent Award | Student Experience | Problem: In the 2024-2025 Regent Master Access Smart Form, Student Spouse Financial Information section was not displayed when the student indicated in the Student Financial Information section that they did not file a tax return for 2022. Cause: Dependency expressions for Student Spouse Financial Information section were set to check incorrect values. Fix: Updated dependency expressions to check valid values. Testing: | |
Regent Access | Student Experience | Problem: The 'Sign' button was not visible on the Document in the parent portal, for the parent of two students, if the same email was entered for the second student when sending a signature request invitation to the parent. Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: The user gets an error in Regent when trying to redistribute the already paid award budget within the terms. Cause: Regent Award was adding Processing Messages to the Award when the Budget Amount was not higher than the Award Amount, despite not needing any additional money from the Budget. Fix: Updated conditions to let Regent Award continue awarding when we don’t need to pull any more money from the Budget. Testing: Find the affected student. Open MAW. Update the fund amounts within the terms. No issues should occur. | |
Regent Access | Workflow/Questionnaire | Problem: Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: Regent Award unexpectedly did not display the remaining budget in Add Award Wizard and did not allow scholarship award to be added due to budget error, although budget amount was sufficient to cover the award. Cause: The application incorrectly processed budget transactions. Fix: Regent Award is updated to correctly process budget transactions and allow award to be added in AAW up to the available budget amount. Testing: Review Budget for fund in Fund Setup to ensure the remaining budget is not $0. Navigate to AAW and add fund into 23-24 FAY. Confirm no errors occur. | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: Cause: Fix: Testing: | |
Regent Award | Packaging | Problem: When the ‘Package Using Actual Loan Fees’ setting in Institution/Campus Setup is enabled, Regent Award did not calculate fees for Title IV loans and fees did not display in COA when there were multiple Title IV funds set up with the same Official Fund Type. Cause: When ‘Package Using Actual Loan Fees’ is enabled, the system-generated cost items for calculating actual loan fees should correspond to each of the four Title IV Loans. When there was more than one Title IV fund of the same type, a Cost Item was created for only one of the funds of that type. Fix: A script will create a Cost Item in Cost Group ‘Calculated Title IV Loan Fees’ for each Title IV fund for the client, where more than one Title IV fund with the same Official Fund Type exists. Testing: Run script for this ticket. Verify Cost Group ‘Calculated Title IV Loan Fees’ includes cost items that correspond to each Title IV fund in Fund Setup. Find the affected student and run packaging. Make sure Loans fees display in COA. | |
Regent Award | Student Experience | Problem: Cause: Fix: Testing: | |
Regent Access | Student Experience | Problem: For a 2024-2025 Regent Access application, the SAI was missing for a Dependent student, both on the PDF of the application and in the generated Communication email (the system unexpectedly omits the SAI sentence in the email output.) Cause: When determining whether EFC/SAI calculation should be suppressed or not, Regent Award pulled the wrong user record and that caused incorrect display in the email output. Fix: The logic was updated to pull correct user info for SAI display, Testing: Complete a 24-25 Access application for the affected student. Review the PDF prior to signing. Review the incoming “Application Submitted” email. Confirm SAI is shown. | |
Regent Award/Review | Packaging | Problem Some students the system did not package it resulted withith error: “Unable to package student (RNA.PackageStudent): Failed to Process. Error Msg: Sequence contains no elements“. Cause The system was checking the awards disbursement and rounding the amount but for the reported students there were no disbursed awards and it caused the error. Fix A code fix was applied so that now the system will not give an error. Testing Navigate to affected students and ensure that they are packaged without error. | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: | |
Regent Access | Student Experience | Problem: In the 2024-2025 Regent Master Access Smart Form, Student Spouse Financial Information section was not displayed when the student indicated in the Student Financial Information section that they did not file a tax return for 2022. Cause: Dependency expressions for Student Spouse Financial Information section were set to check incorrect values. Fix: Updated dependency expressions to check valid values. Testing: | |
Regent Access | Student Experience | Problem: The 'Sign' button was not visible on the Document in the parent portal, for the parent of two students, if the same email was entered for the second student when sending a signature request invitation to the parent. Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: The user gets an error in Regent when trying to redistribute the already paid award budget within the terms. Cause: Regent Award was adding Processing Messages to the Award when the Budget Amount was not higher than the Award Amount, despite not needing any additional money from the Budget. Fix: Updated conditions to let Regent Award continue awarding when we don’t need to pull any more money from the Budget. Testing: Find the affected student. Open MAW. Update the fund amounts within the terms. No issues should occur. | |
Regent Access | Workflow/Questionnaire | Problem: Cause: Fix: Testing: | |
Regent Award | Awarding | Problem: Regent Award unexpectedly did not display the remaining budget in Add Award Wizard and did not allow scholarship award to be added due to budget error, although budget amount was sufficient to cover the award. Cause: The application incorrectly processed budget transactions. Fix: Regent Award is updated to correctly process budget transactions and allow award to be added in AAW up to the available budget amount. Testing: Review Budget for fund in Fund Setup to ensure the remaining budget is not $0. Navigate to AAW and add fund into 23-24 FAY. Confirm no errors occur. | |
Regent Award | Awarding | Problem: Cause: Fix: Testing: | |
Regent Access | Student Experience | Problem: 24-25 Regent Master Access Smart Form allowed user to skip a required question, resulting in '0' value on generated PDF of application. Cause: In cases where a list type question value is prepopulated from the previous application, and this prepopulated value does not match any of the existing options, processing library erroneously treated the prepopulated value as a valid answer. Consequently, validation errors were bypassed. Fix: Student portal Smart Form processing library was enhanced to validate list type question values against prepopulated value. If there is no match, the system will not prepopulate it and will promptly raise any validation errors that occur. Testing: |
Scripts
The following scripts relate to this release:
Key | Functional Area | Release Note |
---|---|---|
Scripts | Purpose of Script:
Data Changed by the Script: How to Access the Script: How to Test the Script: |
Data Views
The following data views relate to this release:
Key | Functional Area | Release Note | RS-27016Functional Area | Release Note | |
---|---|---|---|---|---|
Data Views | Title: New Work Study Data View Created Tickets: RS-27016; RS-28035; Description: Data View ‘dataExtract_WorkStudyWithEarnings_View_v001’ has been created to provide visibility to additional Work Study data. | ||||
Data Views | Title: New Work Study Data View Created for Unmatched Import Student Documents Tickets: RS-2701628195; RS-2803528077; Description: A new Data View ‘dataExtract'dataExtract_WorkStudyWithEarningsUnmatchedImportStudentDocuments_View_v001’ has been created to provide visibility to additional Work Study data' was created to identify students that are imported from the Florida Master Eligibility List (MEL), where the imported record did not match to an existing student record in Regent. |