Key | Product Selection | Functional Area | Release Note |
|---|
RS-19697 | Regent Review | Student Portal (SNAP) | Problem:
The document requirement status was not being updated upon electronic signature on Verification Worksheet, thereby not displaying the correct action icon to allow the student to request a parent signature. Cause:
In the API call that returns the status of applications to Student Experience, it was filtering out applications that were associated with inactive questionnaires. This resulted in Student Experience assuming the status of the application was 'Needed-Not Started', thereby showing the incorrect status and not displaying the action icon needed to invite a parent to electronically sign the application. Fix:
The API method that returns the application status to Student Experience was updated to not exclude applications associated with inactive questionnaires. Testing:
Identify an affected student who has not yet received the parent signature on the application. Confirm the document status is updated to a 'Needed - Parent Signature Pending' status and the action icon to invite a parent to sign the application is present. Invite the parent to electronically sign the application and ensure the application is successfully e-signed. |
RS-19637 | Regent Award | Conversion | Problem:
A SAY trimester student had conversion data corrected using the Import Awards and Disbursements process. In the conversion wizard, when the user tried to Finalize Student Conversion, the system gave an unexpected error: Unable to create batch package. Cause:
The system started packaging the student's financial aid before another procedure had finished. The other process was still processing the course data to create the Academic Plan structure. Fix:
Regent Award was updated to run the Packaging process only after successfully completing the course data processing. Testing:
Test with a SAY trimester student who has COD Rebuild loans in all four terms including the Summer trailer term, with an incorrect end date for the award, AY, and final PP date. Load corrected IAD data that uses the correct end dates, matching the Summer term’s end date. Process the student through the conversion queue. Confirm no errors occur. Package the student. Refresh the Academic Plan. Confirm the student’s loans match the original amounts in all of the terms, including Summer. |
RS-19537 | Regent Award | SAP | Problem:
Regent Award is unexpectedly updating Not Calculated Manual SAP record to Satisfactory after SAP calculation. Cause:
Regent Award had incorrectly not updated a manual SAP record with "Not Calculated" status and applied it to the review period. Fix:
Regent Award was updated to ensure that manually provided "Not Calculated" status correctly applied as a manual SAP record. Testing:
In Regent Award open SAP wizard and set Manual SAP status to "Not Calculated". Package student. Make sure Manual SAP status "Not Calculated" is correctly saved and displayed for the student. |
RS-19527 | Regent Award | SAP | Problem:
Regent Award was unexpectedly showing the Historic SAP status as SAP for the first Term of a Program in the Awards Tab table. Cause:
Regent Award was incorrectly assigning Historic SAP status to the first Program Term. Fix:
Regent Award was updated to ensure Historic SAP is used for calculation of the awards for the first Term but is not associated with this term, as actual SAP will only be calculated at the end of the term. Testing:
In Regent Award, find a student studying in his
her first Term of first Academic Year. Create Student Batch Load (SBL) file with SAP tag, where SAP date and SAP Review Period End Date are prior to Student Term 1 Start Date. Load SBL into Regent Award and package student. Make sure SAP record loaded is not shown on Awards Tab table but only in SAP Wizard. |
RS-19524 | Regent Award | Packaging | Problem:
Some term-based students were close to their lifetime aggregate limits for Subsidized and/or Unsubsidized Direct Loans. When the students were packaged, the system unexpectedly zeroed out their existing loan awards. Cause:
The school loaded an NSLDS Financial Aid History (FAH) data file. The file's date fell in between two Academic Years (AYs). When Regent Award calculated the remaining lifetime aggregate eligibility, the system incorrectly applied the eligibility to the earlier Academic Year instead of the later AY. Fix:
Regent Award packaging logic applies the remaining aggregate eligibility to the correct Academic Year when the data's effective date falls between Academic Years. Testing:
Find an affected student who is close to their lifetime aggregate loan limits, and who had loans in current and future Academic Years. View the student's History tab and the NSLDS column, with the Aggregate Subsidized and Aggregate Unsubsidized Loan amounts. Import an NSLDS FAH data file that contains an "Alert or FAH date" that occurs between the semester dates, and which has the same Total Aggregate Outstanding Principal Balance amounts as the amounts currently on the student. Package the student. Confirm the system packages loan amounts up to the student's full remaining aggregate usage. |
RS-19516 | Regent Award | Awarding | Problem:
Regent Award was unexpectedly awarding a student with Federal Work Study (FWS) when the Fund Setup SAP Required option was enabled and the student had SIS-provided Suspended SAP status. Cause:
Regent Award had incorrectly configured business rules which disallowed the calculation engine from respecting the SAP Required option. Fix:
Regent Award was updated to ensure SAP required option affects SAP calculation. Testing:
In Regent Award, Package student that has FWS interested in ISIR and SAP status Suspended in the previous term. Make sure FWS is not awarded in the current term. |
RS-19350 | Student Experience | Student Experience | Problem:
Regent Student Experience Portal was unexpectedly showing the current Academic Year (AY) Loan amount as Accepted amount for future AY. Cause:
Regent Student Experience Portal was incorrectly applying logic that selected awards from current AY when future AY was selected. Fix:
Regent Student Experience Portal was updated to ensure that only awards from the selected AY are added into the list of awards to display. Testing:
In Regent Award, find affected student and Package. Create Student Experience account, open My Borrowing for Future AY, select any plan, and make sure only Direct Loans from selected AY are shown on the Plan screen. |
RS-19320 | Regent Award | Process Log | Problem:
Updates to student award amounts that were saved within Student Experience while packaging was being executed, resulted in a packaging process failure for the student. Cause:
Regent Award was not checking errors for singleton package runs before persisting into DB. Fix:
The new condition was added into internal procedures to not persist package processes that were failed with the errors. Testing:
Login to Student Experience. Open UnSub loan tile with accepted amount (e.g. $2100). Select 'Accept a Specific Gross Amount' option and add extra amount ($3000). Do not click Save. Run Batch Package only for the affected student. Reload Student Experience. Check Academic Plan details - > MAP. The amount should be the same as initially accepted ($2100). |
RS-19315 | Student Experience | Student Experience | Problem:
At a school with Single Sign-On (SSO), students could not download Documents from the Student Experience Portal. Cause:
The school’s SSO process created larger tokens in their requests during document downloads. The token size was larger than expected by the Student Experience Portal. Fix:
The Student Experience Portal was adjusted to allow larger requests. Testing:
Create a test student in Regent Award or Regent Review, linked to a test account at the school. In Regent, attach several Documents on the Student Documents tab. Authenticate to the Student Experience Portal using the test account and Single Sign-On. Navigate to the Documents area. Download the documents. Confirm the documents are downloaded successfully. Upload a document to the Student Experience Portal. Confirm the document uploads successfully. |
RS-19306 | Student Experience | Student Experience | Problem:
Student Experience portal showed the loan amount entered by the student, in the information message, instead of the Remaining Packaging Philosophy Amount, when a student attempted to update the accepted loan amount. Cause:
Student Experience was incorrectly using the amount the student entered when informing a student about loan restrictions. Fix:
Student Experience logic was updated to ensure that the Remaining Packaging Philosophy amount is shown in an information message when a student enters and tries to accept the Loan amount that exceeds the Remaining Loan Eligibility. Testing:
Find a student who has already selected Borrowing Plan accepted portion of Offered Loan Eligibility. In Regent Student Experience Portal open the Financial Aid page for the student. Review My Eligibility, select radio-button Increase Borrowing by this amount, enter an amount that is higher then Remaining Packaging Philosophy Borrowing Amount. Click Accept. Make sure that in an information message that appears on the top right of the screen ‘Remaining Packaging Philosophy Borrowing Amount’ is shown and not the value that the student entered. |
RS-19273 | Regent Award | COD | Problem:
At a SAY school, some students who had no enrollment in the first term in the SAY had Federal Direct Subsidized loans exported to COD with an incorrect grade level (COD Student Level Code). Cause:
The system was incorrectly setting the loan grade level based on the first term in the Academic Year, instead of the first term in the loan period. Fix:
Regent Award was updated to use the grade level from the first term with positive loan dollars in the loan period. The affected loans are fixed automatically by normal repackaging and exporting to COD. Testing:
Package an affected SAY student who does not have any loans in the first term in their Academic Year, and has a Direct Subsidized Loan with a higher grade level starting in the second or third term in that same Academic Year. Export the Subsidized loan to COD. View the COD export. Confirm the loan’s Student Level Code matches the student’s actual grade level in Regent Award. |
RS-19264 | Regent Award | Technical Design | Problem:
Time out error received upon SBL Import. Cause:
The process was getting hung up on the update for CourseData. Fix:
Created new index for SBLRecordCourseData to prevent timeouts fo the SLB Import due to different SBL course data received. Testing:
Run SBL Import process with similar course data to confirm no timeout error is received. |
RS-19189 | Regent Access | ISIR Processing/Verification | Problem:
eTASFA ISIR Format file had hidden characters (extra bytes) in the first row, resulting in errors when loading the file into SIS. Cause:
For some exceptional cases, Regent Data Exchange module was not able to process the file encoded as UTF-8 with a byte order mark. Fix:
Regent Data Exchange module config changed to encode the export file as UTF-8 without the byte order mark Testing:
Export the eTASFA ISIR Format file and load into SIS. No errors should occur upon loading the eTASFA ISIR Format file into SIS. |
RS-19185 | Regent Review | Workflow/Questionnaire | Problem:
Regent Student Portal was unexpectedly creating "2018 Spouse IRS Verification of Non-Filing Letter" document after completion of Verification Worksheet for Married Filing Jointly students. Cause:
Regent Student Portal document creation logic had an incorrect condition. Fix:
Document creation logic was updated to make sure the document is not created for the student who is filing Taxes jointly with Spouse. Testing:
Find married student with ISIR selected for Verification who's Student’s Tax Return Filing Status is Married - filed joint return. Complete the Verification Worksheet for this student and e-sign it. Make sure "2018 Spouse IRS Verification of Non-Filing Letter" is not created. |
RS-19183 | Regent Award | Packaging | Problem:
Regent Award unexpectedly zeroed out several Pell Grant disbursements. The affected students were near, but still below, the 600% Pell Grant Lifetime Eligibility Usage (LEU) limit. Cause:
The students were repackaged with new COD information in between different Export Student Transactions (EST) processes. When Regent Award calculated the remaining Pell eligibility, the LEU logic incorrectly used the higher, projected paid amount instead of the updated actual amount. Fix:
The Pell LEU calculations were updated to use the actual current disbursement amount instead of the projected paid disbursement amount. Testing:
Package an affected student who is near the 600% Pell LEU. Export the Pell Grant to COD with DRI=true. Import a COD Pell standard response with a different Pell LEU. Repackage the student. Confirm the Pell amount is recalculated to the expected remaining eligibility. |
RS-19143 | Regent Award | EST/Disbursements | Problem:
Multiple paid Pell disbursements were canceled via the EST process and new disbursements were created with the YRP indicator/ Cause:
A Regent Award internal process failed to correctly handle multiple NSLDS imports on the same day. Fix:
Regent Award logic was updated to only get the most recent record for the day. Testing:
Open the affected student. Satisfy documents and tasks. Verify the current disbursements on the Academic Plan before packaging. MAP the student. After packaging, ensure the originally paid disbursements are not canceled and no new disbursements are created. |
RS-19123 | Student Experience | Student Experience | Problem:
Regent Student Experience Portal was unexpectedly showing 0 amounts for Estimated awards on the Financial Aid Borrowing details section. Cause:
Regent Award was incorrectly providing data for displaying in Regent Student Experience Portal. Fix:
Regent Award data interface was updated to provide correct data for Estimated awards on the Borrowing details section. Testing:
Make sure in Regent Award Institution setup - Regent Plan - My Borrowing - "Display Estimated Awards" setting is set to "Yes". Find a student who has not yet selected a Borrowing Plan and who has estimated Awards. In Regent Student Experience Portal open the Financial Aid page. On any proposed Plan click View Details button. Scroll down to the Borrowing details section. Make sure Estimated Awards are shown in Student Loans for Loans or in Other Financial Aid for any other awards. |
RS-19122 | Student Experience | Student Experience | Problem:
Regent Student Experience Portal was unexpectedly not showing Resources on the Financial Aid Borrowing details section. Cause:
Regent Award was not providing individual Resources information for the Regent Student Experience Portal. Fix:
Regent Award was updated to include individual Resources information that is sent to the Regent Student Experience Portal. Testing:
Find a student who has not yet selected a Borrowing Plan, and in Regent Award, manually add or import Resource for the student. Package student. In Regent Student Experience Portal, open the Financial Aid page for the student. On any proposed Plans, click View Details button. Scroll down to the Borrowing details section. Make sure Resources are shown in Other Financial Aid Group. |
RS-19105 | Regent Award | Configuration/Setup | Problem:
Campus view widget was not loading for newly created campus in Regent Award. Cause:
The issue was caused by DB changes that were not properly patched. Fix:
New patch was created to fix the issue. Testing:
Add a campus to institution at Administration section. Update the campus information. Press Save. Click on the new campus. Campus details should display without any errors. |
RS-19041 | Regent Award | EST/Disbursements | Problem:
Some Pell Grant amounts were off by one dollar. Cause:
The Pell disbursement schedule configuration for "Disburse on Enrollment Level Units" had incorrect rounding logic when a student did not have Pell in the first term, and also had a fractional Pell disbursement amount that could not be evenly distributed across the remaining terms. Fix:
The Pell logic for "Disburse on Enrollment Level Units" correctly uses a $0 disbursement amount for a zero-dollar Pell amount, instead of assuming the first term has a fractional amount for rounding. Testing:
Package an affected student who does not have a Pell Grant for their first term, but who has Pell amounts in later terms in the same FAY. Confirm the Pell amounts are correct. |
RS-19031 | Regent Award | EST/Disbursements | Problem: Multiple paid Pell disbursements were canceled via the EST process and new disbursements were created with the YRP indicator. Cause: A Regent Award internal process failed to correctly handle multiple NSLDS imports on the same day. Fix: Regent Award logic was updated to only get the most recent record for the day. Testing: Open the affected student. Satisfy documents and tasks. Verify the current disbursements on the Academic Plan before packaging. MAP the student. After packaging, ensure the originally paid disbursements are not canceled and no new disbursements are created. |
RS-18987 | Student Portal | Student Experience | Problem:
Incorrect 'Increase' validation message popped up when an amount that exceeded the total undisbursed amount was entered for selected 'Reduce Borrowing by this amount' checkbox. Cause:
The incorrect validation message triggered when 'Reduce Borrowing by this amount' checkbox was selected. Fix:
The logic for triggering of validation message was updated according to the requirement. Testing:
Log into Student Experience. Click on 'Financial Aid' on Menu. Click on the 'Reduce Borrowing by this amount' and enter an amount that exceeds the total Sub, Unsub and Grad PLUS to trigger the validation message. The validation message should be: 'You have entered an amount that exceeds your non-disbursed total current loan amount of $X,XXX.00. Please enter a different amount.' |
RS-18957 | Regent Award | R2T4 | Problem:
Incorrect rounding rules were applied for 'Recalculated Pell Amount' and 'Amount that Could Have Been Disbursed' fields at STEP1 of R2T4 wizard. Cause:
Regent Award incorrectly applied rounding rules based on general (dollar) rounding rather than the fund configured rounding. Fix:
System logic was updated to use fund configured rounding rules when calculating Pell amounts in the STEP1 of R2T4 wizard. Testing:
Navigate to the student in question. Add R2T4 for the affected review period. Verify recalculated Pell amounts in the STEP1. The amounts should be showing as dollars and cents. |
RS-18939 | Regent Plan | Packaging | Problem:
The cost of attendance in Regent Award and the My Borrowing borrowing plan option in Student Experience portal were not updated to include manual resource adjustments. Cause:
External manual resources adjustments were not being taken into account by Regent Award and Student Experience portal during packaging. Fix:
Regent Award code was updated to include manual resource adjustments. Testing:
Log into Regent Award. Manually add resource adjustment. Map the student. The cost of attendance will be updated to include the manual resource adjustment in Regent Award. Lor into Student Experience portal. The My Borrowing borrowing plan option in Student Experience will be updated to include the manual resource adjustment. |
RS-18938 | Integration | Not Applicable | Problem:
The HTTP GET API was missing from the API ruleset for Salesforce. Cause:
An additional parameter was needed in the HTTP API GET request. Fix:
The API method was updated to accept the HTTP API GET request without an additional parameter. Testing:
Execute the HTTP API GET request. Verify that the data in the output records corresponded with the correct student data. |
RS-18924 | Regent Award | R2T4 | Problem:
Regent Award unexpectedly identified Direct Loan disbursement as "second or subsequent disbursement" and enabled Do Not Offer checkbox on R2T4 Post Withdrawal Disbursement (PWD) Tab for a loan with the first scheduled disbursement not paid, and so ineligible to be treated as the first disbursement. Cause:
Regent Award was incorrectly treating a non-originated disbursement as a first disbursement, resulting in the actual first disbursement being marked as "second or subsequent disbursement" and “do not offer” logic applied. Fix:
Regent Award was updated to identify the first Direct Loan disbursement as the first disbursement originated in COD. Testing:
In Regent Award, find a student awarded with Direct Loan in Term 1 and Term 2, where Term 1 disbursement is Canceled and was never originated at COD. Add R2T4 for Term 2, resulting in PWD with a portion of Direct Loan. Check the PWD Tab and make sure disbursement is not marked as "second or subsequent disbursement" |
RS-18911 | Regent Plan | Packaging | Problem: The cost of attendance in Regent Award and the My Borrowing borrowing plan option in Student Experience portal were not updated to include manual resource adjustments. Cause: External manual resources adjustments were not being taken into account by Regent Award and Student Experience portal during packaging. Fix: Regent Award code was updated to include manual resource adjustments. Testing: Log into Regent Award. Manually add resource adjustment. Map the student. The cost of attendance will be updated to include the manual resource adjustment in Regent Award. Log into Student Experience portal. The My Borrowing borrowing plan option in Student Experience will be updated to include the manual resource adjustment. |
RS-18900 | Regent Award | Student Experience | Problem:
A school first started using the Student Experience portal with Single Sign-On (SSO) enabled. When some students signed in, they saw incorrect information. Cause:
In the SSO integration, the system did not provide the correct updated user object to the Student Experience Portal. Fix:
The system looks up the correct user object linked to the specific student's information. Testing:
Configure the Student Experience portal to use Single Sign-On (SSO). Log in with several different students in different browsers and different sessions at the same time. Confirm each student sees the correct data. |
RS-18894 | Regent Award | Enrollment | Problem:
When lastAttended date matched startDate of the term, the system was not able to recognize the attendance correctly although all 'attended' criteria had been already met. As a result, Academic Plan showed 0 attended units. Cause:
Gaps in CE Rollup process logic, when boundary values were used in course data, caused the data for packaging to become stale and resulted in the issues with units not being consumed as expected. Fix:
System CE Rollup checks were updated to be more efficient. Logic was added to validate the execution success of all batch-related processes. Testing:
Navigate to an affected student. Open 'Courses' tab and add the same start/end date. Set 'Has Attended' as True. Make sure that course is not withdrawn, not remedial, and non-transfer. Run packaging. Review Academic Plan. The 'attended' units should not be 0. |
RS-18893 | Regent Award | Awarding | Problem:
Grade-level progression loans that started before the school's configured crossover date were assigned to the next FAY instead of the prior FAY. Cause:
When Regent Award repackaged crossover loan periods for periods less than a full academic year, the system did not create the updated loan for the correct FAY. Fix:
Additional logic was added for loan periods that are less than a full academic year. When the system repackages crossover loan periods, the system will re-evaluate the FAY and will recreate loan periods for the correct FAY. The system will only change loan periods for loans that do not have a paid disbursement. Testing:
Navigate to an affected student who has an unpaid 2020-2021 grade-level progresssion loan that starts before the configured crossover date. Package the student. Confirm the system repackages and replaces the loan in the 2019-2020 FAY. |
RS-18876 | Regent Plan | Student Experience | Problem:
In pre-release testing, a tester reported an incorrect loan offered amount for the Direct Cost plan. Cause:
N/A - The issue could not be recreated. Fix:
No new code changes occurred. Testing confirmed the issue was no longer present. Testing:
Identify a student who has not yet selected a Borrowing Plan. Click the link to 'Select My Borrowing Option.' Review the total loan amount being offered. Confirm the student is packaged and the amount is displaying accurately. |
RS-18875 | Regent Plan | Student Experience | Problem:
Regent Plan Glossary links were not working properly in the Student Experience portal. Cause:
.The Glossary links with the same text content had the same browser IDs. Each ID is required to be unique on the page. resulting in broken links. Fix:
New prefixes were added to existing IDs to avoid duplication. Testing:
Log into the Student Experience portal. Navigate to the My Plan page. Click on a configurated Glossary terminology (link). The Glossary definition configured for the Glossary terminology will be displayed. Repeat steps for the Change History section. |
RS-18860 | Regent Plan | Student Experience | Problem: Financial Aid component and Dashboard in Student Experience were missing links to My Borrowing. Cause: Regent Award was not able to set the appropriate flags for links to make them visible when determining AY information. Fix: System controllers were updated to handle flags correctly. Testing: Log in to Student Experience. Navigate to Dashboard section. Review My Borrowing and Regent Plan tiles. My Borrowing links are showing. Repeat the same steps for Financial Aid section. |
RS-18847 | Student Portal | Student Experience | Problem:
My Borrowing Remaining Eligibility Amounts were not calculated correctly. Cause:
Regent Award was not reducing the 'Accepted Amount' when the New Offer/Calculated Eligibility was reduced during repackaging for multiple loan period scenarios. Fix:
Regent Award changes made to update the award's accepted amount to the eligible amount when the award is accepted and a reduction is being processed. Testing:
Identify affected students in a multiple loan period scenario. Select the Direct Cost initial plan in My Borrowing. Add scholarship award for an amount that will reduce the Unsubsidized loan eligibility. Review the 'Remaining Eligibility' amounts on the My Borrowing tile (assuming Change My Borrowing Amount is turned on). |
RS-18846 | Student Portal | Student Experience | Problem:
When entering an amount that exceeded $9,999 for the 'Specify a Lesser Amount' on the My Borrowing Select Plan pop-up screen, all numbers were not displayed. Cause:
There was a spacing issue that did not allow for numbers greater than $9,999 to display accurately. Fix:
Additional spacing was added that allowed for numbers greater than $9,999 to display. Testing:
Click on the 'Select a Borrowing Plan Option' link to enter into the My Borrowing main page. Click Select a Plan on one of the two available plan options. Select the 'Specify a Lesser Amount' radio button and enter an amount greater than $9,999. Ensure the amount displays all numbers entered. |
RS-18839 | Student Experience | Student Experience | Problem:
Incorrect value listed for Estimated Total Costs on the My Borrowing Plan View Details section. Cause:
The field used the Total Net Costs instead of using the Total Cost of Attendance. Fix:
The code was updated to use the Total Cost of Attendance field. Testing:
Identify an affected student. Click on the 'Select a Borrowing Plan option' link to enter the My Borrowing main page. Click on the 'View Details' link for one of the two Borrowing plans displayed. Scroll to the Estimated Total Costs and review the amount for accuracy. |
RS-18809 | Regent Award | Packaging | Problem: The packaging of students was blocked due to an unexpected error in Modify Award Wizard in Regent Award. Cause:
There was an issue for Cost Items with the processing of special symbols. The bug affected the processing of the "Calendar Year" min/max date range configuration settings at Cost Setup, which resulted in the packaging error. Fix:
Regent Award logic for verification of date range configuration settings was updated. Testing:
Run BP for the site to which the affected students are assigned. No errors should occur when the process is completed. |
RS-18808 | Regent Award | EST/Disbursements | Problem:
Regent Award was unexpectedly changing the Disbursement Amount so that one dollar moved from the last Term of Academic Year (AY) to the prior one. Cause:
Regent Award had incorrectly applied rounding rules, resulting in $1 rounded value to be paid in the wrong term. Fix:
Regent Award was updated to ensure that once rounding rules are applied, the sequence of Terms that is used for paying is correct. Testing:
In Regent Award, package student with Direct Loan that is split across eligible Terms, not as a whole dollar Amount. Package student. Make sure that cumulative $1 resulted from rounding is paid in the Last Term of the AY. |
RS-18804 | Regent Award | Awarding | Problem:
The AnnualLoanLimitAmount token used in My Borrowing message incorrectly displays an amount of $4625. Cause:
The lookup table that Regent Award used to determine annual loan limits contained a value of $4,625 rather than $2,625 for an undergraduate preparatory coursework dependent student. Fix:
Updated the lookup table that Regent Award used to determine annual loan limits to the correct value of $2,625 for an undergraduate preparatory coursework dependent student. Testing:
Identify an affected dependent student taking preparatory coursework. Confirm messaging is configured with the AnnualLoanLimitAmount token for the messaging and that the amount. Ensure the messaging displays the correct amount for the {AnnualLoanLimitAmount} token in My Borrowing for the student. |
RS-18802 | Regent Award | R2T4 | Problem:
Regent Award unexpectedly created a new disbursement in Cancelled status for a Direct Loan after R2T4 finalization when the R2T4 resulted in a Post-Withdrawal Disbursement (PWD) marked as “Do Not Offer” with the reason, "Second or subsequent disbursement." Cause:
Regent Award was applying “Do Not Offer” logic in an incorrect sequence if the loan had a Post Withdrawal Disbursement (PWD) amount greater than what had already been paid. Fix:
Regent Award was updated to correctly process Direct Loan amount changes for post-withdrawal disbursements that are canceled due to being marked as “Do Not Offer,” when the PWD amount is greater than the paid amount. Testing:
In Regent Award, find a student awarded with a Direct Loan in at least two terms in the AY, Term 1 and Term 2. Ensure the Term 1 amount is already paid, and the current Term 2 amount is unpaid. Add a new R2T4 for Term 2 resulting in a PWD with a portion of Direct Loan. Review the PWD tab and make sure the Direct Loan disbursement is marked as “Do Not Offer” with the reason "Second or subsequent disbursement." Finalize the R2T4. Package the student. Confirm the preexisting Term 2 disbursement is canceled and no new disbursement is created. |
RS-18801 | Regent Award | R2T4 | Problem:
Regent Award was unexpectedly updating Disbursement Scheduled date of paid and scheduled Disbursement for the Direct Loan after R2T4 finalization when R2T4 resulted in Post Withdrawal Disbursement (PWD). Cause:
Regent Award was incorrectly updating R2T4 PWD Disbursement Scheduled dates on already paid Disbursements during R2T4 Finalization. Fix:
Regent Award is updated to ensure that R2T4 only changes the Scheduled date for non-released Disbursements upon Finalization. Testing:
In Regent Award find a student with the ongoing Term which is the first Term of the Academic Year and awarded with Direct Loan. The Loan should be Paid by two Disbursements during the ongoing term, where the first Disbursement is already paid and the second is Scheduled. Perform R2T4 resulting in PWD with a portion of the Direct Loan. Finalize R2T4 and make sure that the existing paid disbursement Date is not changed. |
RS-18799 | Regent Award | R2T4 | Problem:
Regent Award was unexpectedly not canceling "do not offer" disbursement marked as second \ subsequent disbursement. Cause:
Regent Award was incorrectly determining that the Post Withdrawal Disbursement (PWD) amount was greater than the amount already paid. As the wrong logic was applied, the disbursement was reinstated ignoring 'do not offer' option Fix:
Regent Award was updated to prevent the processing of a PWD amount that's greater than the paid amount in the scenario where the PWD disbursement should have been canceled due to being marked as do not offer. Testing:
Find the student with Direct Loan scheduled to be paid in two disbursements and one of the disbursements is already paid. Add R2T4 resulting in PWD (Step 2 should have more than 50% of Completed Enrollment). So that portion of the second disbursement is in PWD and marked as second\subsequent disbursement. Finalize R2T4 and make sure the second disbursement is canceled. |
RS-18775 | Regent Review | Documents | Problem:
Regent Award was unexpectedly updating the hypertext format link with attributes of Document Message field into a broken hyperlink. Cause:
Regent Award was incorrectly processing hyperlink tags in Message field in Document setup. Fix:
Regent Award was updated to ensure hyperlinks with attributes and more complex HTML markup would be processed by Message Field. Testing:
In Regent Award Document Setup, edit existing or create a new document and enter HTML tag with herf attribute into the Message Field. Save Document and make sure Message field is displaying hyperlink as expected. Create Document Requirement for any student with this Document. In Student Portal make sure Message is correctly displayed on Document Page. |
RS-18742 | Regent Award | Packaging | Problem:
Regent Award was unexpectedly creating overlapping Academic Years for CBE program Cause:
Regent Award had incorrectly calculated Non-Term Academic Year dates when manually assigned anticipated units are less than or equal to a half of a Program Academic Yearly Units. Fix:
Regent Award was updated to ensure new Academic Year is created without overlapping regardless of anticipated units specified. Testing:
Find affected Non-Term student and package. Make sure Academic Years don't have overlapping dates. |
RS-18705 | Regent Award | Packaging | Problem:
Some students could not be packaged due to an error, "Nullable object must have a value." Cause:
An error was identified in the code for Regent Award's Cost Items. The bug affected the "Calendar Year" minimum and maximum date range configuration settings for certain Cost Items. Fix:
The incorrect code was corrected. Testing:
Package the affected students. Confirm the students can package successfully. |
RS-18684 | Regent Award | R2T4 | Problem:
R2T4 recalculated Pell amount although Lifetime Eligibility Usage limit had been already exhausted. Cause:
Regent Award did not take into account Pell LEU values during R2T4 recalculation process. Fix:
A code change was applied to allow Regent Award to include Pell LEU values into R2T4 recalculation process. Testing:
Find the affected student. Navigate to History tab - > click 'Edit' - > manually add Pell/IASG LEU of 600.000%. Import SBL with courses (attendance before/after Census Date). Navigate to the Awards tab and add R2T4. Verify that Pell amount is not included into R2T4 as 600% limit is reached. |
RS-18682 | Regent Award | Awarding | Problem:
A school imported an award using the Import Awards and Disbursements (IAD) process. The "Offered On" and "Originally Offered On" dates did not match the imported values from the IAD data. Subsequent packaging runs also unexpectedly changed the dates. Cause:
The system incorrectly applied logic from the disbursement schedule which changed the dates. Fix:
The system preserves the originally scheduled dates from the Import Awards and Disbursements (IAD) data file. If new dates are imported, the system will update the scheduled date according to the import data. The dates will not automatically change as long as a disbursement is still scheduled for the same payment period specified by the IAD data. If Regent Award moves a disbursement, the system will update the adjusted release date. Testing:
Import an Awards and Disbursement data file with an award and scheduled disbursement for an eligible student. Package the student. On the Awards tab, confirm the "Offered On" and "Originally Offered On" dates match the dates from the imported data. View the disbursement details. Confirm the disbursement's scheduled date matches the date from the Import Awards file. Package the student several times. Confirm the dates do not change. Import a second Awards and Disbursement data file with different dates. Package the student. Confirm the Originally Offered On date does not change. Confirm the Offered date is changed to match the Offered date from the new Import Awards data file. Confirm the disbursement's date is also changed to match the date from the data file. Repackage the student several times. Confirm the dates stay the same. |
RS-18495 | Regent Review | Workflow/Questionnaire | Problem:
Regent Student Experience Portal was unexpectedly populating incorrect Marital Status Date in Verification Worksheet smart form. Cause:
Regent Student Experience Portal was incorrectly processing data received from ISIR. Fix:
Regent Student Experience Portal is updated to ensure the Marital Status Date is correctly populated from ISIR. Testing:
In Regent Student Experience, register account for a married student who's ISIR is selected for verification so that Verification Worksheet Document Requirement exists for a student. Start Application and make sure that the Marital Status Date in Family Information section is populated with the correct value received from ISIR. |
RS-18429 | Regent Award | User Interface | Problem:
The extra term was incorrectly included by Regent Award into the Loan Period of the program with Standard Term Semester period type configuration. Cause:
Regent Award persisted loan period terms (semesters and quarters) without database identifiers and tracking attributes unlike other academic plan entities (academic years, enrollments, awards, etc.). Therefore loan period terms were saved with additional terms. Fix:
A code fix was provided so that Regent Award could add all necessary information when persisting loan period terms. Testing:
Open student profile. Navigate to 'Award' tab. Select Loan Period in question. Verify Compare Awards grid (no extra terms are included). Run packaging. Navigate to 'Awards' tab. Select Loan Period in question. Verify Compare Awards grid. No extra terms are included in loan period. |
RS-18428 | Regent Award | Reports | Problem:
Regent Award was unexpectedly not showing values for a set of fields in the Wisconsin State Grant Report. Cause:
Regent Award was incorrectly not specifying Disbursement as processed on Wisconsin Grant Roster File import. Fix:
Regent Award was updated to ensure Disbursement from Roster File is correctly linked with Disbursements handled in Regent Award. Testing:
In Regent Award, import Wisconsin Grant Roster File for a student and run packaging. Generate Wisconsin State Grant Report and make sure Roster Award Amounts and Roster Spent Amounts are populated for respective Terms. |
RS-18427 | Regent Award | R2T4 | Problem:
Some term students had their enrollment levels drop to below half-time status, resulting in their loans being zeroed out. Later, the students withdrew, resulting in an R2T4. The system unexpectedly did not include the original loan amounts in the R2T4 Amount that Could Have Been Disbursed. Cause:
At the time the students had their enrollment drop to below half-time status, the school had configured a value of "No" for Institution Setup, Include Disbursements Cancelled for Below Half Time Status. Fix:
Regent Award stores the original loan amount when the loan drops below half-time status, regardless of the configuration setting at the time. However, the system still only includes the prior loan amount in the R2T4 if that configuration setting is enabled. Testing:
In Institution Setup, R2T4 tab, confirm the setting for "Include Loan Disbursements Cancelled for Below Half Time Status" is currently set to "No." Reload RNA setup as needed. Find a term student who has an unpaid loan that is already accepted at COD. Confirm the student has at least half-time status in the first term in the loan period. Package the student. Update the student's course information in that first term to drop to below a half-time enrollment level in the term. Repackage the student. Confirm the loan amount is reduced to $0 as expected. View the Activity Log. Confirm the Activity Log contains an entry that the system has updated the Cancelled Below HT Amount. Next, change the Institution Setup setting back to Yes for "Include Loan Disbursements Cancelled for Below Half Time Status" and reload RNA setup. Repackage the student. Add a new R2T4 record with enough attendance for the student to be eligible for a Post-Withdrawal Disbursement. Confirm the R2T4 Wizard, Step 1, displays the section for "Loans Cancelled for Below HT Status." View the PWD tab Confirm the loan amounts are displayed as PWD amounts. Finalize the R2T4. Package the studet. Confirm the correct loan PWD amounts appear on the Academic Plan. |
RS-18421 | Regent Award | Student Experience | Problem:
Regent Student Experience Portal was unexpectedly showing incorrect document name in E-sign step 2, supporting text for non-Smart-Form documents. Cause:
Regent Student Experience Portal was using a static document name on E-sign step 2 for non-Smart-Form documents. Fix:
Regent Student Experience Portal was updated to use a generic document name that is dynamically substituted for each document instance. Testing:
In Regent Award, add non-Smart-Form Document Requirement for a student that has E-sign option. Create Student Experience account for this student. Open Document page, upload document, and go to E-sign step 2. Make sure that supporting text is referring to this Document Requirement name. |
RS-18367 | Regent Review | Documents | Problem:
The required document uploaded via import of 'Student Documents XML' does not appear until 'birthDate' attribute is sent for the student via SBL. Cause:
Regent Award treated birthDate field as a required attribute to match to imported documents. The missing attribute resulted in student and document requirement mismatch. Fix:
The birthDate field was set as non-mandatory. The system will be able to match the student and document requirement without the mentioned attribute. Testing:
Import student SBL file without birthDate attibute. Import Student Document (XML). Navigate to 'Documents' tab. The uploaded document is showing. |
RS-18353 | Regent Award | R2T4 | Problem:
Regent Award did not include Direct Loan awards in R2T4 when Master Promissory Note (MPN) is expired and has Inactive Status at the moment of R2T4 creation. Cause:
Regent Award incorrectly ignored non-linked
non-accepted MPN records during R2T4 creation. Fix:
Regent Award logic was updated to use non-linked
non-accepted MPN records so that R2T4 processing logic wizard can use them. Testing:
Add R2T4 for a student awarded with Direct Loan who had valid MPN at the beginning of the Academic Year and which expired and is Inactive prior to R2T4 Date of Withdrawal. Make sure Direct Loan is included into the R2T4. |
RS-18262 | Regent Award | Configuration/Setup | Problem:
Regent Award was unexpectedly allowing the editing of Data Fields Flag in Document setup for incorrect Federal Award Year (FAY) scope. Cause:
Regent Award had an incorrect dependency between FAY selected in Document Scope and Fields allowed for editing for existing documents. Fix:
Regent Award was updated to ensure that for old document editing, the correct association between Scope FAY(s) and editable fields is created. Testing:
In Regent Award Document Setup, modify an existing Document with FAY Scope. When a FAY Scope value of 2020-2021 or later is selected, make sure on ISIR Assignment Tab "Student's Untaxed Pensions" fields will be grayed out (uneditable). When a FAY Scope not equal to 2020-2021 or later is selected, the "Student's Untaxed IRA Distributions and Pensions" field will be grayed out (uneditable). If all FAYs are selected as the scope value, both the "Student's Untaxed Pensions" field and the "Student's Untaxed IRA Distributions and Pensions" field will be grayed out (uneditable). |
RS-18231 | Regent Award | Reports | Problem:
'Student - R2T4' report output results did not return all students with R2T4 records. Cause:
Regent award did not include R2T4 on 'Student R2T4' report when student had Non-Term to Term-based program change. Because R2T4 belonged to a Non-term program period, the system excluded the record from the report. Fix:
UI view was fixed to include R2T4 records in spite of program changes. Testing:
Find the student enrolled in NT program. Add R2T4 and finalize it. Load SBL with program change and complete it via Program Management Wizard. |
RS-18194 | Regent Award | Awarding | Problem:
Regent Award was incorrectly prorating Direct Loans in Remaining Period of Study (RPS) when student had registration in the future term that would not be needed if student completed all the courses in the current Term. Cause:
Regent Award had incorrectly processed Direct Loan proration when student had post-program completion enrollment. Fix:
Regent Award was updated to ensure that Post Program Completion Enrollment for undergraduate programs in RPS scenario will be excluded from Loan Calculation when Fund Setup has setting Award Full Eligibility For Eligible Periods Only as false. Testing:
Find a student in RPS studying trimester program that based on current registration student would complete in Term 1 of this last Academic Year. Load SBL with at Least Half time registration in Term 2. Package student. Make sure Direct Loan amount for entire AY is not changed. The loan amount should be based only on remaining number of units required for Program Completion. |
RS-18165 | Regent Award | R2T4 | Problem:
Regent Award was unexpectedly not using Manual Pell LEU set on History Tab. Cause:
Regent Award had incorrectly processed Pell LEU when "Always Use Manual" flag was set on History Tab. Fix:
Regent Award was updated to ensure manually entered Pell LEU is used for packaging regardless of the date it was set when "Always Use Manual" flag is enabled. Testing:
In Regent Award, edit information on History Tab. Check "Always Use Manual" checkbox and set Pell LEU to 595% so it is easy to track that this amount is applied. Next day load FAH TSM NSLDS file with different Pell LEU. Package student. Make sure that Pell is calculated based on manually entered Pell LEU. |
RS-18163 | Regent Award | COD | Problem: Regent Award was unexpectedly exporting, to COD, an incorrect Grade Level for students with a Program Change. Cause: Regent Award was incorrectly calculating Grade Level for the Enrollment that belonged to the previous Program. Fix: Regent Award is updated to ensure that Transfer Units account for all relevant Enrollments and that Grade Level is calculated correctly. Testing: In Regent Award find a student who was transferred from another school with External Units enough for the Grade Level Progression. Perform substantially Equal Program Change. Make sure Grade Level for the first term of the Previous Program is not changed on the Academic plan. |
RS-18151 | Regent Award | R2T4 | Problem:
Loan disbursements were not cancelled after 'Actual Cancel Date' and 'Net Accepted amount' were set on PWD tab of R2T4 wizard. Cause:
Regent Award was not cancelling the disbursements due to locking flag from R2T4 PWD sheet. Fix:
Regent Award logic was updated to handle disbursement amounts correctly, by-passing locking flags. Testing:
Navigate to the affected student. Add R2T4 resulting in PWD. Edit PWD worksheet: set 'Actual Cancel date'as today's date and 'Net Accepted Amount' as $0 for Direct Sub loan. Save changes. Finalize R2T4. Run packaging.
Verify that PWD loan disbursements with $0 are in 'Cancelled' status at Academic Plan. |
RS-17998 | Regent Award | COD | Problem:
For some nonterm students, when Regent Award exported Loan information to COD, the Academic Year (AY) end date unexpectedly did not match the Loan Period end date for the second payment period (PP2). Cause:
Several specific scenarios were altering AY end dates. Some students had Academic Years ending during an instructional week, and Regent Award incorrectly used the end date of the instructional week. Some students had R2T4 end dates that were not properly calculated. Several students had a Payment Period closure due to being out of their program for over 180 days, resulting in an incorrectly applied end date. Fix:
Regent Award was updated to ensure that the Academic Year end date and Loan Period end dates will be correct for the reported scenarios. Testing:
Navigate to an affected nonterm student. Observe the AY dates on the Academic Plan and the Loans tab. Package the student. Review the dates on the Loans tab. Confirm the Financial Award Period and Academic Year end date are accurate. Export the loan to COD. Review the Financial Award Period and Academic Year dates in the exported data file. Confirm the dates are correct. |
RS-17883 | Regent Award | R2T4 | Problem:
Regent Award was unexpectedly rounding up Gross PWD Direct Loan amount in Post Withdrawal Disbursement R2T4 tab Cause:
Regent Award was incorrectly using Fund Setup Rounding option configured for the fund when calculating Gross PWD amounts. Fix:
Regent Award was updated to use COD truncation rules when rounding PWD Net amount that subsequently corrected calculation of Gross PWD amount. Testing:
In Regent Award create R2T4 for the student that results in PWD. Review Gross PWD Direct Loan amounts. Make sure that Gross PWD amount is calculated in whole dollars - the same as Net PWD amount (;including origination fee) |
RS-17596 | Regent Award | Configuration/Setup | Problem:
Regent Award was unexpectedly loading the Permission tree for about 2 minutes after adding the new role. Cause:
Regent Award permission cache loading caused the significant delay during the creation of a new role for the school that had multiple Institutions. Fix:
Regent Award is updated to optimize the performance when the new role is being created. Testing:
In Regent Award, Administration, Roles add new Role. Select the created Role and navigate to the Permissions tab. Make sure the Permissions tree is loaded without delays. |
RS-17577 | Regent Award | Awarding | Problem:
Regent Award was unexpectedly calculating incorrect Direct Loan eligibility when the Remaining Period of Study (RPS) for the student was equal to full Academic Year (AY). Cause:
Regent Award had incorrectly processed Fund setup setting 'Award Full Eligibility For Eligible Periods Only', resulting in Direct Loan eligibility being prorated when RPS was equal to full AY. Fix:
Regent Award was updated to ensure proration in RPS that is equal to full Academic year will not happen regardless of the Fund setup settings. Testing:
In Regent Award, find a student whose RPS is full Academic Year. In Fund Setup, enable 'Award Full Eligibility For Eligible Periods Only'. Package student. Make sure Direct Loan amounts are not prorated. |
RS-17509 | Regent Award | Awarding | Problem:
Regent Award was unexpectedly awarding a student over the Direct Loan Aggregate Limit. Cause:
Regent Award was incorrectly processing NDLDS information from FAH and TSM files. Fix:
Regent Award is updated to ensure the latest information from FAH and TSM file is used for Direct Loan calculation. Testing:
In Regent Award find affected student and Package. Make sure Direct Loans are calculated based on the latest NSLDS information and within Aggregate Limits. |
RS-17212 | Regent Award | Tasks | Problem:
'Review Unpaid Loan from Another School' froze on attempt to review task details. Cause:
Regent Award did not load task details at UI, due to empty taskHash value in DB. Fix:
UI code was fixed to load task details properly. Testing:
Find the affected students. Go to Tasks tab. Navigate to Completed Tasks tab. Click on Review Unpaid Loan from Another School task. Task details are loaded. |
RS-16616 | Regent Award | Packaging | Problem:
Regent Award unexpectedly awarded students with Direct Loans over Aggregate award limits, ignoring imported NSLDS Financial Aid History (FAH) data. Cause:
Regent Award was incorrectly comparing existing award dates in Regent with data from NSLDS FAH files so that the latest available Aggregate Limits were not applied during packaging. Fix:
Regent Award was updated to ensure NSLDS amounts and dates are applied in the correct sequence based on time received. Testing:
In Regent Award, import an NSLDS FAH file with more recent data and different lifetime aggregate loan amounts than the dates and amounts on the student's History tab. Package the student. Confirm the new amounts from the FAH file are used for packaging. Confirm the loan amounts are correct. |
RS-16598 | Regent Award | Documents | Problem:
Regent Award was unexpectedly updating document status from NEEDED to RECEIVED when assigned to a student. Cause:
Regent Award was incorrectly not creating Activity Logs for Document Requirements that have Activity Type = Document Related. Fix:
Regent Award was updated to ensure Activity Log is created for Document Requirements that have Activity Type = Document Related. Testing:
In Regent Award add Document Requirement for a student. Edit Document requirement and change Activity Type to "Document Related". In the Student Portal upload document. In Regent Award make sure Activity Log is created. |
RS-16208 | Regent Award | Configuration/Setup | Problem:
Configured dashboards were not showing on login for users with SSO authentication type. Cause:
Dashboard settings were not loaded by Regent Award during SSO authentification. Fix:
The verification step was added to check loaded dashboard setting. Testing:
Perform SSO login. Review 'Dashboard' tab. Verify that 'Task/Activity Dashboard', 'Financial Aid Dashboard' and 'Task Productivity Dashboard' are showing. |
RS-15483 | Regent Review | Tasks | Problem:
Regent Award was unexpectedly not clearing out the "Select All Tasks" checkbox in the grid on Task Tab. Cause:
Regent Award had incorrectly processed User Interface control in the grid on Task Tab once Task operation was submitted. Fix:
Regent Award was updated to ensure the "Select All Tasks" checkbox is updated appropriately once the action on the selected Task is submitted. Testing:
In Regent Award, open Task tab for any student. In Tasks grid select all tasks via checkbox in the grid header. Change Status of the Tasks Selected to "Waived" or any other Status. Submit and make sure the checkbox in the header is unchecked. |
RS-15477 | Regent Award | User Interface | Problem:
Regent Award had incorrect spelling for two EST error codes and Notification Message in Add
Modify Award Wizards. Cause:
Regent Award had typo in text description for EST errors and Notification Message. Fix:
Regent Award was updated with corrected text messages. Testing:
In Regent Award, Perform EST process so that EST-0026, EST-0038 is triggered. Make sure there are no spelling errors in EST error message description. In Regent Award, find student with enrollment after Program completion. In Add Award Wizard attempt to add award for the term that is after Program Completion date. Make sure that error message that prevents adding such award does not have spelling errors. |
RS-15409 | Regent Award | Process Log | Problem:
'Selected Parameters' for batch processes did not reflect in Process Log. Cause:
'Selection Parameters' tab was missing display entities at Process Log screen. Fix:
The missing fields were added onto 'Selection Parmaters' tab of Process log screen. Testing:
Navigate to Processes. Select Batch Package process. Execute this process with different parameters combination - verify that values of selected parameters are present at 'Process log > Selection parameters' screen. |
RS-15407 | Regent Award | User Interface | Problem:
Regent Award was unexpectedly showing incorrect loan period on Loans Tab.
If a two term loan is updated where the first term amount = $0 and the second term contains a loan amount > $0, the loan period is displayed differently on the Loans tab from other tabs with loan periods. Cause:
Regent Award was incorrectly showing Loan Period information on Loans Tab as if loans were one-term loans. Fix:
Regent Award was updated to ensure Loan Period are displayed similarly across the application. Testing:
In Regent Award, find affected student and review Loan Period information on Loans Tab. Make sure Loan Periods are the same as on Awards Tab. |
RS-14185 | Regent Award | Awarding | Problem:
Regent Award was unexpectedly packaging Pell Calculated Eligibility and showing cents in Modify Award Wizard (MAW) and COD tab when rounding was set to whole dollar. Cause:
Regent Award had incorrectly packaged Pell Calculated Eligibility, ignoring Fund Setup Rounding option for Year Round Pell (YRP). Fix:
Regent Award was updated to ensure that the Packaging process respects Fund setup Rounding option in YRP scenario. Testing:
Find student with portion of Pell awarded as YRP in ongoing term and Full time amount that would contain cents if not rounded. On Award tab edit Pell. In MAW make sure that Calculated eligibility is shown rounded to whole dollar. Export Pell to COD. Make sure COD tab is showing amount rounded to whole dollar. |
RS-12794 | Regent Award | Configuration/Setup | Problem:
Regent Award was unexpectedly did not verify the data entered in SAP Setup Maximum Time Frame (MTF) Field. Cause:
Regent Award incorrectly allowed entry of more than 150% for MTF Field. Fix:
Regent Award was updated to allow SAP Setup MTF field to be a numeric value between 100% and 150% or blank. Testing:
In Regent Award, navigate to Administration SAP Setup. Edit and enter an amount that is less than 100 or more than 150 for MTF. Make sure notification "'Maximum Time Frame' must be between 100 and 150" is shown. Note: Blank value is also allowed. |
RS-668 | Regent Award | Configuration/Setup | Problem:
Regent Award was unexpectedly not saving Street Address information on Site setup screen. Cause:
Regent Award incorrectly processed editing of Street Address that was inherited from Mailing Address. Fix:
Regent Award was updated to ensure Street Address update is properly processed and saved. Testing:
In Regent Award Administration Site setup, edit Site information where Street address has 'Same As Mailing' enabled. Update Street Address, Uncheck 'Same As Mailing' and and Save. Make sure Street Address is saved properly. Check same scenario for site where 'Same As Mailing' is already unchecked. |