|
| RS-13315 | Regent Award | Awarding | Problem:
Students with Year-Round Pell (YRP) awards were unexpectedly awarded $1 over their 150% maximum amounts. Cause:
The Year-Round Pell amounts were unexpectedly rounded up instead of truncating. Fix:
Regent Award now has additional logic to check for rounded values in Year-Round Pell maximum amounts. The system ensures the amounts do not exceed 150.000% of the student's annual maximum. Testing:
Navigate to an affected student who has a current maximum Year-Round Pell award. Clear any packaging blockers. Repackage the student. Regent Award will repackage the Pell amount to not exceed 150.000% of the student's annual Pell limit. |
| RS-13272 | Regent Award | Awarding | Problem:
In the first term of a two-term Academic Year (AY), a term student had a paid loan disbursement, then the student later dropped to Less Than Half Time (LTHT) enrollment in the term. The student still had half-time (HT) or greater enrollment in the second term in the AY. A user edited the loan in Modify Award Wizard (MAW). After editing in MAW, the loan still had a nonzero disbursement for the LTHT payment period. However, the system unexpectedly did not include the LTHT term in the Financial Award Begin and End dates (Loan Period dates) shown on the Loans tab. The system also unexpectedly did not include the LTHT term when reporting the loan's Financial Award Begin and End dates to COD. Cause:
The system had moved the loan off of the first term in the AY (the LTHT term) and on to the second term of the AY (the HT or greater term). The loan was now on a Single-Term Loan Period for the wrong term. Because of the student's LTHT enrollment in the first term, the system did not change the loan period dates to include the LTHT term. Fix:
Additional logic was added for evaluating a loan's Financial Award dates. When sending loan data to COD, the system now includes a payment period in the Financial Award Begin and End dates whenever the payment period has either a positive loan amount, or the payment period has a positive paid amount. Testing:
Navigate to a student with a paid loan disbursement on a LTHT term. Use the Program Management Wizard (PMW), if needed, to create a loan period that includes the LTHT term. Edit the loan in MAW and ensure the loan still has a nonzero loan disbursement on the LTHT term. Continue through MAW. Refresh the Loans tab. Inspect the loan's Financial Award period dates. The Financial Award dates should include the LTHT term. Export the loan to COD. Inspect the exported data. The loan should export to COD with the correct dates, including the LTHT term with the nonzero loan disbursement. |
| RS-12991 | Regent Award | Awarding | Problem:
In Modify Award Wizard (MAW), when a user edited a student's award and selected the "Override Eligibility Rules" checkbox, the wizard unexpectedly did not continue to Step 2. Instead, an error was displayed: Failed to Process. Error Msg: Sequence contains no matching element Cause:
The student had a shortened manual Academic Year that contained only one term instead of the normal two terms. The resulting Loan Period was a single-term loan period. When the loan was edited in MAW, and the "Override Eligibility Rules" checkbox was selected. Regent Award unexpectedly tried to calculate an amount for two terms: the term in the single-term loan period, and also the following term. The second term should not have been included, as it was neither in the loan period nor in the manual AY. Fix:
When an award is edited in MAW, and a user selects "Override Eligibility Rules," Regent Award does not try to calculate payment period amounts for any payment periods outside the loan period. Testing:
Navigate to an affected student. Edit an affected award using Modify Award Wizard. Select the "Override Eligibility Rules" checkbox, and enter Notes and a New Offer amount. MAW should continue without error. The adjusted award should successfully package. |
| RS-11924 | Regent Award | Awarding | Problem:
For some nonterm students close to their NSLDS aggregate loan limits, Regent Award calculated incorrect amounts that were twice the expected eligible amounts. Cause:
Regent Award miscalculated the running aggregate totals for Subsidized and Unsubsidized loans. The system incorrectly excluded loan periods with past end dates. The resulting remaining balances were incorrect. Fix:
Regent Award was updated to calculate combined aggregate amounts using loan periods from the past as well as current and future loan periods. Testing:
Navigate to an affected nonterm student who has aggregate loan amounts close to the maximum aggregate limits. Edit the student's loans in the Modify Award Wizard (MAW). Examine the Calculated Eligibility amounts. The eligible amount for each loan should not cause the student's loans to exceed the aggregate total limits. |
| RS-12914 | Regent Award | Configuration/Setup | Issue:
Students with a Less Than Half Time enrollment in the first term of their Academic Year (AY) and a Half-time or greater enrollment in the second term of their AY require a Single Term Loan (STL) to be packaged for the second term of the AY. In these cases, students were over-awarded by the amount of their Direct Loan origination fees. Cause:
In some cases, when a student had a STL in the second term of the AY, Regent Award did not correctly consider the student's loan origination fees when packaging funds subsequent to Direct Loans in the Packaging Philosophy order. Fix:
Regent Award was corrected to appropriately consider the Direct Loan origination fees when awarding students with STLs in the second term of the AY. Testing:
Repackage an affected student. The Direct Loan origination fees should be appropriately considered when packaging the student and any over-awards should be resolved. |
| RS-12554 | Regent Award | Documents | Problem:
When an administrator made changes to the Document Setup, General tab, the screen un-selected the checkbox for "Assign by SBL" on the SBL Assignment tab. Cause:
A bug in the Document Setup screen accidentally changed the checkbox selection when the checkbox should have been disabled or read-only. Fix:
If the "Assign by SBL" checkbox is disabled or read-only, then the system will not save any changes to the "Assign by SBL" checkbox value. Testing:
In Document Setup, edit the SBL Assignment tab, and select/check the checkbox for "Assign by SBL." Click Save. Go to the General tab. Make a change on the General tab and Save. Go back to the SBL Assignment tab and refresh. Examine the "Assign by SBL" checkbox. The "Assign by SBL" checkbox should keep its saved value. |
| RS-12268 | Regent Award | EST/Disbursements | Problem:
A term-based school was configured as "Allow Packaging to Move Paid Disbursements" equal to "No." R8 blocked packaging for students with a packaging error, Error validating plan - the payment period on paid disbursement...was moved from the original pp (Removed Payment Period Id[])... Cause:
When Regent Award checked to see which terms should be included in the Academic Plan, some terms were removed. The disbursements referenced in the error message were linked to those removed terms. Fix:
The code was updated to allow Regent Award to restore a term to the Academic Plan if the term has a paid disbursement. Testing:
For a school configured to not allow Regent Award to move paid disbursements (on Instituiton Setup, "Allow Packaging to Move Paid Disbursements" is set to "No."), repackage the students who previously had the Batch Packaging error. The students should now package without error. The paid disbursements should stay on their original terms. |
| RS-8738 | Regent Award | EST/Disbursements | Problem:
The EST Process Report showed extra, invalid, Payment Period records for some students. Cause:
The query that produced the output of the EST Process Report included Course Enrollment records from the Regent Award database that did not have an associated Payment Period on the student's Academic Plan. Fix:
The report query was updated to include only those Course Enrollment records that are linked to a corresponding valid Payment Period on the student's Academic Plan. Testing:
Run the EST Process Report and verify that only valid records are not included on the output. |
| RS-8753 | Regent Review | ISIR Processing/Verification | Problem:
The ISIR Verification/Correction Verification Wizard prevented users from re-editing fields that had already been changed, back to the original values. Cause:
An incorrect validation rule blocked the update of ISIR fields back to the initial/original value. The system ignored all new values that were the same as the initial one. Fix:
The validation rule applied to the field was corrected to allow the field to be updated to all applicable values. Testing:
On an affected student, go to ISIR tab, select any ISIR and click the 'Start ISIR Verification/Correction Wizard' button. Select the ISIR field number to be edited. Notice the original/default value of the field. Perform an update to the associated 'Corrected value' field. Click 'Continue.' Move to Step 2 and click 'Finish'. The field will update with a new value. Run 'Start ISIR Verification/Correction Wizard' again and change the new value back to the original/default one. Click 'Continue.' Move to Step 2 and click 'Finish.' 'Corrected for transmission on this ISIR' column should show the original field value. |
| RS-13342 | Regent Award | Packaging | Problem:
When Regent Award packaged a student, an unexpected error resulted: Failed to Process. Error Msg: Value cannot be null. Parameter name: indices Cause:
The student had an award with an extra, $0 disbursement that would not be processed. Regent Award tried to schedule the $0 amount using the Disbursement Schedule. The system could not properly apply the Disbursement Schedule weights for the disbursement, and threw an unexpected exception. Fix:
When Regent Award is distributing proportional amounts according to the Disbursement Schedule, and a disbursement would not be processed (such as a cancelled disbursement), the system applies a zero weight to that disbursement. Testing:
Package the affected student. The student should successfully package without error. |
| RS-13341 | Regent Award | Packaging | Problem:
A school was configured for a Standard Academic Year (SAY) with an anticipated optional Summer Header semester. When Regent Award packaged some students who had no Summer registration, their Academic Years (AYs) unexpectedly contained the Summer and Fall terms. The AYs should have been only the Fall and Spring terms. Cause:
The affected students had a non-enrolled, Autowithdrawn Summer term. When Regent Award checked to see if the Summer term should be processed as an optional header or trailer, the system unexpectedly treated Summer as a regular (non-optional) term. Fix:
When Regent Award adjusts enrollments in Academic Years, new logic was added to correctly process terms that are optional SAY header or trailers. Testing:
Navigate to a SAY Semester student who has no enrollment in the Summer header term. Repackage the student using the Modify Academic Plan wizard (MAP), Basic Packaging. The student's Academic Year should consist of the Fall and Spring terms only. Navigate to another student who is enrolled in the Summer term. Package that student using the MAP wizard. The Academic Year should include Summer, Fall, and Spring semesters. |
| RS-13301 | Regent Award | Packaging | Problem:
When a user edited a loan in Modify Award Wizard (MAW) and continued through Step 3 "Adjust Disbursements," Regent Award unexpectedly canceled and zeroed out the existing disbursements. Cause:
MAW unexpectedly zeroed out disbursements and set them to a "Canceled" status if the payment period was inside the loan period. Fix:
MAW preserves nonzero payment period amounts from Step 2 to Step 3. Testing:
Edit a loan in Modify Award Wizard. Continue to Step 3. The existing disbursements should keep their original amounts. Those existing disbursements should not be Canceled. Continue through the wizard and Finish. Refresh. The loan amounts should be correct. If the loan was not previously manual, then it should stay in a non-manual status. |
| RS-13276 | Regent Award | Packaging | Problem:
A fund was awarded eligibility based on a Satisfied Document. When a student had a final Academic Year (AY) in a shortened Remaining Period of Study (RPS), the system unexpectedly awarded the fund on both the RPS term and a non-enrolled term after the program ended. Cause:
When Regent Award confirmed eligibility based on a Satisfied Document, the system did not consider the payment periods' enrollment levels past the program completion in a shortened RPS Academic Year. Fix:
Regent Award now checks enrollment levels when awarding funds based on a Satisfied Document. Logic was added to consider the program's completion in a shortened RPS Academic Year. The system only awards funds onto eligible payment periods with anticipated or actual registration before the program is complete. The system does not award funds onto non-enrolled payment periods past the program's completion. Testing:
Navigate to an affected student in a shortened Remaining Period of Study final AY. Award a fund to an RPS AY by assigning a Document and setting the Document status to 'Satisfied.' Package the student, such as by using the Modify Academic Plan wizard. Regent Award should only award the fund on payment periods with anticipated or actual registration. Regent Award should not create any disbursements from the fund on the non-enrolled payment periods after the program ends. |
| RS-13274 | Regent Award | Packaging | Problem:
A school had some FAY-based funds that were configured in Fund Setup and do not use a Regent custom ruleset. The funds were configured to round to cents. However, when Regent Award packaged the funds, some amounts were unexpectedly missing the cents. Cause:
The funds were configured with the distribution option, Divide Evenly Across PPs in FAY, Not to Exceed Cost per PP. When Regent Award calculated the amounts for each payment period, the system did not use the proper rounding settings when distributing the payment period amounts. Fix:
Regent Award was corrected to apply the configured rounding setting when amounts are distributed across payment periods. Testing:
Navigate to an affected student who has a non-Title IV award with an incorrectly rounded amount in a current award period. Package the student. Refresh the Awards screen. The awards should show the correct expected amounts, including cents. |
| RS-13235 | Regent Award | Packaging | Problem:
When trying to package a student, an unexpected packaging error occurred: Error validating plan for Student [#]: The number of disbursements was attempted to be increased on a paid Pell Rebuild award in a closed enrollment. Cause:
The system caused a validation exception when recalculating a COD Rebuild Pell award with Year Round Pell (YRP) disbursements in a past payment period. Fix:
The validation was corrected to allow updates to YRP disbursements in past payment periods. Testing:
Navigate to an affected student. Package the student. The student should package successfully without error. |
| RS-13110 | Regent Award | Packaging | Problem:
A student had two overlapping PLUS loans, one for the full Academic Year and the other a single-term loan. Regent Award calculated an unexpectedly high "Calculated Eligibility" amount for the single-term PLUS loan. Cause:
The loan in the full AY Loan Period had the full offered amount. However, the student had only accepted part of that offered amount. When Regent Award calculated Unmet Cost for the single-term loan, the system only reduced the single-term loan's costs based on the overlapping loan's accepted amount. Fix:
Regent Award calculates each loan's total maximum eligibility, independent of accepted amounts in overlapping loan periods. The system does not exceed each loan's maximum eligibility amount. Testing:
Navigate to an affected student who has multiple, overlapping, current PLUS loans, including a single-term PLUS loan. Package the student. Check the PLUS calculated eligibility amounts. The PLUS calculated eligibility on the single-term loan should not exceed the term's cost of attendance (COA). None of the PLUS loans should be overawarded above COA and other resources, for the single term PLUS as well as the full-AY PLUS. |
| RS-13106 | Regent Award | Packaging | Problem:
Regent Award was incorrectly awarding students who were eligible for less than the $1000 annual minimum Wisconsin Grant (WG-PNP). Cause:
Student's eligible for the Wisconsin Grant must be eligible for an annual minimum award of $1,000. If the student is eligible for any less, the student does not receive the award. Regent Award was not honoring this rule. Fix:
The missing minimum annual award check was added to the WG-PNP Formula. Testing:
Repackage students whose annual Wisconsin Grant is below the annual minimum award amount ($1000) and ensure that the student does not receive the Wisconsin Grant during any term of the FAY. |
| RS-13017 | Regent Award | Packaging | Problem:
A student had an institutional award created by a "Satisfied" document. Later, the document was changed to a status of "Needed" and the award canceled as expected. However, when the document was later changed back to a "Satisfied" status, the award unexpectedly remained Cancelled. Cause:
The student had a Less-Than-Half-Time (LTHT) enrollment. Regent Award unexpectedly failed to reinstate the canceled award due to unexpectedly applying Federal Direct Loan truncation logic to the institutional award. Fix:
Regent Award now reinstates canceled non-Title-IV disbursements on LTHT enrollments if a student regains eligibility and no other blockers exist for that enrollment. Testing:
On a student with LTHT enrollment, assign a document and set it's status to "Satisfied" in order to award an institutional fund. Package the student. The institutional fund should award full eligibility. Change the document to a status of "Needed" and repackage the student to cancel and zero out the institutional award. Change the document back to "Satisfied" status and repackage the student. The institutional award should be reinstated at the full amount. |
| RS-12992 | Regent Award | Packaging | Problem:
When some students are packaged, an unexpected message occurs, similar to: Failed to Process. Error Msg: Federal Direct Unsubsidized Loan has an already-released or paid disbursement #1 paid $200 on 1/23/2018 in Spring 2018. Fund Setup disallows increasing paid disbursements on this Fund. Please correct the Import Award data. Some additional students had another error message with the same root cause: Non-unique disbursement number(s) detected in Award. Cause:
Two issues were found. First, Regent Award did not properly apply the configuration setting for "Attempt to Keep Paid Disbursements Unchanged" on imported COD Rebuild awards with multiple, paid disbursements. The problem affected single-term COD Rebuild loans with multiple, nonzero, paid disbursements. In another similar issue, Regent Award unexpectedly failed to correctly reduce some paid disbursements for 150% Year Round Pell when the payment periods had multiple paid disbursements. Fix:
The "Attempt to Keep Paid Disbursements Unchanged" logic was applied to imported COD Rebuild Awards and Year Round Pell disbursements with nonzero paid disbursement amounts. Testing:
Navigate to an affected student who had the packaging error, and has an affected single-term COD Rebuild loan with multiple, nonzero paid disbursements. Package the student, such as by using Modify Academic Plan wizard. The student should package successfully without error. Examine the disbursement amounts. The disbursement amounts should be correct. Navigate to another affected student who was giving the error for a Pell award with nonzero paid Pell disbursements. Package the student, such as by using Modify Academic Plan wizard. The student should package successfully without error. Examine the disbursement amounts. The disbursement amounts should be correct. |
| RS-12978 | Regent Award | Packaging | Problem:
Regent Award calculated new, lower eligibility amounts for some already-paid Institutional awards. However, the award amounts unexpectedly did not change on the Academic Plan. The lower amounts also did not result in refunds in the Export Student Transactions (EST) process. Cause:
When the awards were originally imported, they had overpaid amounts for some payment periods. When the system calculated new total amounts for each payment period, the system could not determine which overpaid disbursement should be changed. Fix:
Regent Award's logic was improved to better handle awards with multiple overpaid disbursements. The system calculates the difference between the paid amount and the eligible amount. Regent Award then evaluates each individual disbursement's amount and adjusts each disbursement as needed. Testing:
Navigate to an affected student in a current award period. Repackage the student. Confirm the award amounts correctly adjust. Execute the EST process for the student. The EST process should produce a negative transaction for the difference between the overpaid award and the new award amount. |
| RS-12973 | Regent Award | Packaging | Problem:
When Regent Award packaged some students, packaging failed with an unexpected error: Error validating plan for Student [#]: Non-unique disbursement number(s) (7) detected in Award [#] Cause:
When Regent Award was reducing a paid amount and also adding a scheduled disbursement on an award, the scheduled disbursement number was unexpectedly not incremented. For example, if a Pell award was reduced by R2T4, and already had an existing disbursement number 7, the system may have added a new Year-Round Pell disbursement with number 7. Fix:
When Regent Award calculates the next disbursement number, when adding scheduled disbursements, the system checks for the highest disbursement number on an award. Testing:
Navigate to an affected student. Package the student. The student should successfully package without error. |
| RS-12962 | Regent Award | Packaging | Problem:
The FAY-scoped awards were not packaging the amount per Payment Period correctly. Cause:
The award amount was not being limited by the remaining balance of the configured packaging "target" amount for the Payment Period. This "target" amount is configured by "Additional COA Requirements" on the Fund Setup. The full amount of the configured "Additional COA Requirements" total for the Payment Period was being used instead of the remaining balance after packaging prior awards. Fix:
Updated Regent Award to use the "Additional COA Requirements" remaining balance for the payment period when packaging the award. Testing:
Repackage the students with the FAY-scoped awards and verify that the per payment period award amounts are correct. |
| RS-12910 | Regent Award | Packaging | Problem:
For students with a historic Academic Year (AY0), the Wisconsin Grant disbursement for the last term in the FAY was reduced to $0 even though the student's eligibility did not change. Cause:
During the recalculation of the Wisconsin Grant award, the AY0 award amount was treated as an overage, which in turn caused a reduction/cancellation of latter disbursements inf the FAY (last disbursement typically). Fix:
Updated the overage calculation logic to properly account for AY0, as well as the logic related to the configured FAY maximum limit. Testing:
Repackage the student with Wisconsin Grant awards including AY0 and verify the award amounts are correct and the last term's award is not $0. |
| RS-12907 | Regent Award | Packaging | Issue:
Regent Award calculated additional Subsidized Loan eligibility due to a grade level increase. Since the additional Subsidized Loan was not yet accepted by the student, the Unsubsidized Loan incorrectly awarded above the annual limit by the total amount of the Unsubsidized Loan origination fees. Cause:
Regent Award was not properly accounting for the additional 'Offered' amount of Subsidized Loan when calculating the student's Unsubsidized Loan amount, but was instead using the current Subsidized Loan award amount (prior to the acceptance of the increased eligibility due to the grade level increase) and therefore, attempting to add additional origination fees to the Unsubsidized Loan. Fix:
Regent Award was corrected to calculate the student's maximum annual loan limit using the student's Subsidized Loan eligibility, instead of the actual current Subsidized Loan award amount at the time of packaging. Testing:
Repackage an affected student. The Subsidized Loan should now be offered at a gross amount of $4,500, and the Unsubsidized Loan should be limited to the student's maximum annual Unsubsidized Loan eligibility. |
| RS-12683 | Regent Award | Packaging | Problem:
Some BBAY term students had past loans for a single term. In an older version, Regent Award unexpectedly packaged the students with incorrect Financial Award Period dates. The incorrect dates unexpectedly matched the full Academic Year's (AY) dates. Because the loans now had award periods ending in the past, the system would not automatically change the dates for those past loans. Staff edited the past loans in Modify Award Wizard (MAW), to trigger the system to repackage the loans with corrected loan period dates. Regent Award automatically fixed the loan period dates on the edited loans, as expected. However, the next time Regent Award repackaged the loan in another process such as Batch Packaging, the system unexpectedly reverted the loan period date changes to incorrectly match the full AY. Cause:
When staff first corrected the loan in MAW, a new, shorter loan period was added by the system but it was only temporary. The next time the student was batch packaged or otherwise repackaged, Regent Award unexpectedly removed the new loan period, and moved the loan back to the full AY loan period dates. Fix:
When staff edit a loan using Modify Award Wizard, and the system updates the loan period dates, Regent Award now preserves the new loan period dates when the student is later repackaged in other processes. Testing:
Navigate to a student with an affected loan. Edit the loan in Modify Award Wizard. Continue through MAW, making no changes, and click "Finish." Review the loan period dates, displayed as the Financial Award Begin and End dates, on the Loans tab. Package the student again in another process. Refresh and view the Loans tab. The Financial Award Begin and End dates should still only include terms that have loan dollars. The Financial Award Begin and End dates should not include any terms with only $0 in loan disbursements. |
| RS-11965 | Regent Award | Packaging | Problem:
When a student in a nonterm program missed or did not complete several courses, Regent Award recalculated both Academic Year and Loan Period start/end dates for the program. As a result, non-transfer courses that were attended after the program start date were incorrectly marked as internal transfer courses by the system. Cause:
Due to the manual update of Loan Periods and Academic Year dates via the Student's BBAY Modification, the system incorrectly applied the program start date when calculating the Academic Year, Enrollment, Payment Period, Loan Period inadvertently ignoring the student's BBAY modification results. Fix:
Regent Award was updated to calculate AY and Loan Period dates using the Student BBAY Modification changes. Testing:
Package an affected student. Review the Academic Plan tab and check the dates for the AY in question. The dates should be the same as they are in the associated Student BBAY Modification. Go to the Courses tab and confirm that "Conversion Calculated Internal Transfer" is "No" on the courses in the affected AY. |
| RS-427 | Regent Award | Packaging | Problem:
A user incorrectly processed Program Changes on some term students as Not Substantially Equal. A data-cleanup script fixed the student's active programs. However, when a user packaged the student using the Modify Academic Plan (MAP) wizard, Advanced Packaging, the Academic Plan showed the incorrect program linked to the student's terms. Cause:
MAP Advanced Packaging unexpectedly linked the terms to the incorrect programs. Fix:
MAP Advanced Packaging links the correct, active programs to each term. Testing:
Navigate to an affected student who has already had programs corrected via a data-cleanup script. On the Academic Plan screen, click Modify Academic Plan, then Advanced Packaging. Continue through the wizard and finish. Refresh the Academic Plan screen. The program information for each term should be accurate. |
| RS-13275 | Regent Award | Program Change | Problem:
An undergraduate term student was in a shortened final Academic Year (AY) Remaining Period of Study (RPS). The student registered for more units than the program completion units. A user edited the program's required units with a Program Units packaging override. When Regent Award repackaged the student's Direct Subsidized and Unsubsidized Loans, the system unexpectedly prorated the loan amounts using the originally anticipated units in the term. Cause:
When Regent Award prorated the loan amounts, the system always used the Program's defined number of units, even when a Program Units packaging override was present. Fix:
If a student has a Program Units packaging override, Regent Award will use those override units when prorating loan amounts. Testing:
Navigate to an affected student who has loans in a shortened RPS AY. Change the student's required Program Units using the Program Units packaging override. Repackage the student. Inspect the loan amounts. The loan amounts should be prorated based on the adjusted remaining units in the program. |
| RS-3607 | Regent Award | R2T4 | Problem:
On attempt to update student via MAP/MAW/PMW/SAP wizards, the user received an error. Manual SAP Record cannot be assigned to any payment period, which prevented the student from further processing. Cause:
Because the student did not attend the Academic Year (AY), the AY was removed from the student's Academic Plan. However, the manual Student SAP Records associated to that AY were not removed and therefore became invalid since the system could not load the removed Academic Year. Fix:
A cleanup script was added to remove the Student SAP records related to the deleted Academic Years. Testing:
After executing the cleanup script, select any affected student. Package the student or make adjustments to the student using one of the system wizards. No SAP related errors should occur. |
| RS-3564 | Regent Award | SAP | Problem:
The SAP Wizard screen did not display SAP records with an identical 'SAP Date' and 'SAP Review Period End Date' in the correct hierarchical order based on SAP precedence rules: - If a school chooses a “Manual” SAP policy – that is the ONLY SAP status that Regent Award is to ever use. If a SAP status is imported on the SBL, the system will not use it.
- If multiple manual SAPs are provided for a single SAP Review Period, the system will always use the SAP status with the latest SAP date.
- If a school chooses a “Calculated” SAP policy – that is the ONLY SAP status that Regent Award is to ever use UNLESS a “Manual” SAP status is entered via the SAP wizard – in which case the Manual entry overrides the calculated SAP status. If a SAP status is imported on the SBL, the system will not use it.
- If the SAP status is calculated more than once for a student for a given period, the system will use the SAP status with the latest SAP date (but a Manually provided SAP status would override a Calculated SAP status with the same SAP Date).
- If a school chooses a “SIS” SAP policy – that is the ONLY SAP status that Regent Award is to ever use UNLESS a “Manual” SAP status is entered via the SAP wizard – in which case the Manual entry overrides the SIS provided status. Regent Award should never attempt to calculate any portion of SAP in this scenario.
- If multiple SAPs statuses are imported on the SBL for a single period, the system will always use the SAP status with the latest SAP date (but a Manually provided SAP status would override a SIS provided SAP status with the same SAP Date).
Cause:
Calculated SAP records were being displayed ahead of Manual SAP record entries. This is incorrect because a Manual SAP record for the same SAP Date and SAP Review Period would override a Calculated SAP record. Fix:
Regent Award was updated to use the correct sort order when displaying SAP records on the SAP wizard. Now when the SAPDate and SAP Review Period are the same, the Manual entry overrides anything that was Calculated, thus the records are displayed based on precedence rules. Testing:
Go to the Awards tab and click the 'Calculate SAP' button. If SAP records have the same SAP Date and SAP Review Period, the SAP records with a Manual source should be displayed prior to the Calculated SAP records. |
| RS-11678 | Regent Review | SBL | Problem:
When an SBL file was imported, Regent Award failed to load the file and gave an unexpected error: Error while processing the data file: Index and length must refer to a location within the string. Parameter name: length Cause:
When the file's size in Kilobytes was converted to Megabytes for logging, the error was triggered if the resulting file size did not have at least four decimal places. The problem occurred when a file's size in bytes, divided by 1048576.0, resulted in a number with less than three significant digits. Fix:
The logging error checks were adjusted to not require four significant digits. Testing:
Use or create an SBL file with a size that would cause the error, such as exactly 1048576 or 1310720 bytes. Confirm the file size in bytes by viewing its Properties in Windows Explorer. Import the file. The file should successfully import without error. |
| RS-12718 | Regent Access | Student Portal (SNAP) | Problem:
In the Student Portal, whenever a student tried to access a 2017-2018 application, an unexpected error occurred: Could not find stored procedure 'snap_Application_GetMaxTransactionNumber'. Cause:
The application was missing a stored procedure, snap_Application_GetMaxTransactionNumber. Fix:
The missing stored procedure was added to the database. Testing:
Log in to Regent Access as a student or test student account. Access a 2017-2018 application. The system should display the saved application without error. |
| RS-12017 | Student Portal | Student Portal (SNAP) | Problem:
A Regent Access file import failed due to an unexpected error, "Duplicate Transaction ID." Cause:
In the Student Portal, if a user double-clicked or otherwise retriggered a Smart Form button quickly (multiple times within 1 second), the system failed to increment the transaction ID. Fix:
The Smart Form button was updated to prevent users from triggering the transaction multiple times. Additionally, a cleanup script was created to remove the extra, duplicated transactions. The Transaction ID logic was also improved to use an internally calculated Transaction ID instead of depending on the Smart Form button click. Testing:
In a Student Portal Smart Form, double-click or quickly click the buttons multiple times for Start, Edit, and Re-submit. The system should only create one transaction. |
| RS-13273 | Regent Award | User Interface | Problem:
When some loans were edited in Modify Award Wizard (MAW), MAW Step 1 gave an unexpected error: Accepted Amount is required for awards whose status is Accepted. Please go to Step 1 and provide an accepted amount. However, the loans already had an Accepted amount. Cause:
When some manual loans were edited, Regent Award did not correctly add the total of the disbursement accepted amounts. Fix:
When Regent Award calculates manual awards, the Accepted amount totals are correctly set to the sum of the disbursement amounts. Testing:
Navigate to a student who has an affected manual loan in Accepted status. Edit the loan in Modify Award Wizard and continue from MAW Step 1 to Step 2. The wizard should not present the error message. Cancel MAW, then edit the loan again. Clear out the Accepted Amount and attempt to continue past Step 1. The wizard should still give the error if the Accepted Amount is blank. |
| RS-11252 | Regent Award | User Interface | Problem:
Regent Award did not assign fund-specific Documents during packaging. Cause:
The Funds were configured with a blank "Institutional External Fund ID" field in Fund Setup. Regent Award did not have an identifier to link the funds to the Documents. Fix:
The school configured the funds with non-blank, unique values for Institutional External Fund ID. Regent Award then assigned the documents correctly. In addition, help text was added to the field in Fund Setup:
Institutional External Fund ID This field needs a non-blank value, unique within the Institution, for packaging to assign Documents specific to this fund. Testing:
Configure Document Setup to assign a Document for a specific fund. In Fund Setup, configure the fund with a non-blank value that is unique within the Institution, for Institutional External Fund ID. Mouse over the informational icon and view the Help text. Package the student. Regent Award should assign the fund-specific Document. |