Problem:
Some COD response files stayed in 'Staging' status, instead of changing to 'Imported' status. The files had an error such as, 'Failed to complete post-process procedure....Subquery returned more than 1 value.'

Cause:
Some COD files had been imported more than once. The system contained rows in the database with the same, duplicated COD 'DocumentID' value.

Fix:
The COD Import validation was updated to not return the error message if multiple files have the same value for the COD Document ID. The system still prevents re-processing a duplicated file with an identical COD Document ID when that file contains records that were already processed.

Testing:
Import two duplicate COD files with identical COD Document ID values and contents. Confirm the error message does not occur. Confirm the process status changes to 'Imported' instead of 'Staging.' Confirm the first file is imported successfully. Try to process the second file. Confirm the system does not re-process the second file.

RS-21656

Problem:
At a school with a new implementation of Regent Award, whenever some term-based students were repackaged, the system created new, additional, $0 loans in Cancelled or Declined status.

Cause:
The logic for truncating loan periods inadvertently created additional, extra loans.

Fix:
The inaccurate loan-period truncation logic was updated to ensure the system no longer creates new $0 loans.

Testing:
Navigate to an affected student. Observe the student’s current loans and FAID values. Clear any blocking Documents or Tasks. Repackage the student. Confirm the system does not create additional $0 loans.

Problem:
When some COD Rebuild awards were exported to COD, the system did not include some fields that were required for the current COD schema. COD rejected the disbursements with edit code 994, Missing Content was not submitted for a required field.

Cause:
The COD Export process relied on data from the Rebuild award. The required fields were not present in the Rebuild data.

Fix:
The COD Export process was updated to not use incomplete data from COD Rebuild records. Instead, the system only uses the latest COD-Accepted data when it has all the required values: has a COD Document ID; is a Standard Response or COD Web Response (RS or WB file); is not a rebuild; and uses the same COD Schema format.

Testing:
Package an affected student, clearing any blocking Documents or Tasks. Export the student’s award to COD. Download the COD output data file from the Process Log. Open the XML data file. Confirm the required fields and values are present in the exported data file.

Problem:
When a school tried to disburse some institutional awards, the disbursements were blocked with EST-0056 (SAP Status is required for release). The funds were configured with ‘SAP Required?’ set to No.

Cause:
The disbursement rules were applying the same logic as for Title IV funds.

Fix:
The disbursement release logic was updated to check for the Fund Setup configuration.

Testing:
Navigate to an affected student who has an award from a fund that is configured with ‘SAP Required?’ set to unselected (disabled). Ensure the student does not have an SAP status for the previous term. Run an Export Student Transactions (EST) process for the student. In the Process Log, view the Students tab. Confirm the disbursement is successfully paid without any error message.

Problem:
Some students had a previous SAP review period’s SAP Status of ‘Not Calculated.’ When the Export Student Transactions (EST) process ran, the process unexpectedly paid the disbursement.

Cause:
The system did not detect that the SAP status of ‘Not Calculated' was due to a missing Reason (e.g., missing grades or missing GPA) vs. SAP not being required for the period. The system incorrectly treated the ‘Not Calculated’ SAP statuses with missing reasons in the same manner as periods that are expected to have a ‘Not Calculated’ SAP status (i.e., due to starting a new program).

Fix:
When the system calculates the effective SAP status, improved logic was added to detect when SAP should have been calculated for the previous SAP Review Period. If the student has a ‘Not Calculated’ SAP with a missing Reason, Regent uses the ‘Not Calculated’ status vs. reverting to the status for the last SAP Review period.

Testing:
On a test student with unpaid disbursements for the current term, confirm the student’s SAP Status for the previous SAP Review Period is ‘Not Calculated’ due to a specific Reason, e.g. Missing GPA. Run the EST process for the student. Confirm the EST-0057 validation error code was received for the disbursement (EST-0057: ‘SAP status prevents release’) and that the disbursement was not paid.

Problem:
For term-based programs that use an Academic Year (AY) SAP policy, the school sent Student Batch Load (SBL) data files containing the SAP node with the Cumulative GPA. However, some students still had a SAP status of ‘Not Calculated’ due to Missing Cumulative GPA.

Cause:
Two problems were found. First, the system did not use the Cumulative GPA from the SAP node if it was being sent for students in Graduate programs. Second, the Academic Year (AY) SAP logic did not correctly mark the payment periods as needing a calculated SAP status.

Fix:
Regent updated logic to use the Cumulative GPA provided in the SBL SAP node for both graduate and undergraduate programs. The logic for an Academic Year SAP policy for a term-based program has also been updated to apply the AY SAP policy based on the ending term within the SAP Review Period.

Testing:
Confirm a student’s SAP Status for a SAP Review Period is not yet posted or was calculated with a value of ‘Not Calculated.’ Load an SBL with a SAP Date and a Cumulative GPA for the immediate past SAP Review Period. Ensure the student does not have any blocking Documents or Tasks. Package the student using Modify Academic Plan (MAP), or via Batch Packaging including the option to “Run SAP Process.” Refresh the student’s Academic Plan. View the Awards tab and SAP Wizard. Confirm the student has a SAP Status calculated for the correct SAP Review Period.

Problem:
The Student Experience Portal went down unexpectedly.

Cause:
In the Student Experience Portal, a utility process used the cache but it never released the memory. As more students accessed the Portal over time, the process consumed all available memory.
Fix:
The Student Experience Portal was updated to no longer call the problematic utility.

Testing:
Run the Student Experience Portal for several days with multiple students accessing the system. Confirm the system remains available.

Problem:
Regent Award College Financial Plan (CFP) communication was incorrectly duplicating the Institutional and State Scholarship amounts in the ‘Other Scholarships’ section.

Cause:
The CFP communication template incorrectly processed scholarship information including all scholarship-related amounts into the ‘Other Scholarships’ section.

Fix:
The CFP template ‘Other Scholarships’ section was updated to only include scholarship amounts related to this section.

Testing:
In Regent Award add the following types of scholarships to any student:

1. Scholarship, where Fund Source is Institutional.
2. Scholarship, where Fund Source is State.
3. Scholarship, where Fund Source is neither Institutional nor State.
4. Generate CFP communication.

The 'Other scholarships' section should include only the award amount, where the Fund Source is neither Institutional nor State.

Problem:
In the Process Log, on the Students tab for the 'Export Document Requirement (XML)' process, the filter for 'Has Attachment' column did not filter for any values.

Cause:
The ‘Has Attachment’ column filter was not configured to use the correct values.

Fix:
A new column filter was created and adjusted to allow filtering for values of ‘Yes,’ ‘No,’ or ‘All.’

Testing:
In a test environment, run the Export Student Documents (XML) process to clear out any students with pending Documents. Identify or create two test students who each have Document Requirements in their Student Documents tab. On the first student, edit a Document. Change some values and attach a file for the Submitted Documents, then Save. On the second student, edit the Document and change some values but do not attach a file; Save. Run the Export Document Requirement (XML) process and select the checkbox for 'Export Information about Document File Attachments.' Refresh the Process Log. View the Students tab. Confirm the first student has a value of 'Yes' in the 'Has Attachments' column. Confirm the second student has a value of 'No' in the 'Has Attachments' column. Click the funnel icon on 'Has Attachments.' Filter the 'Has Attachments' column using various criteria. Confirm the system applies the selected filter(s) and displays the matching results.

Problem:
For some students, the Student Experience Portal displayed an unexpected “Please check back later” error message when accessing the Financial Aid component.

Cause:
Some calculations to determine database field values were not protected from dividing by zero when the current aggregate loan limit could not be determined.

Fix:
The code was updated to not use the problematic values when the current aggregate loan limit has a negative value and the calculated values return as zero.

Testing:
In a test environment that has the Student Experience Portal, make sure Cache is Enabled. Package a student using Batch Packaging. Confirm the student is successfully packaged without error. View the “Advisor Assist” tab. Access the Financial Aid component or another area that packages awards. Confirm the Student Experience Portal does not display the error, “Please check back later.”

Problem:
Regent Award was incorrectly re-assessing Direct Loans after importing FAH data.

Cause:
Regent Award was incorrectly processing Direct Loan Amounts after loading NSLDS FAH data for students that are close to Aggregate limits.

Fix:
Regent Award packaging process was updated to make sure Direct Loan amounts are correctly accounted for ongoing Academic Years where some portion of Direct Loan was already paid.

Testing:
Find a student who is close to the Aggregate Limit and has a portion of the Loan paid in ongoing Academic Year. Import FAH NSLDS data that already has this paid portion included. Package student and make sure that award amounts are not changed.

Problem:
'Process command failed' error occurred, when clicking either 'Save, but do not run EST for AR' or 'Save and Run the EST for AR' button at COD WB Reconciliation Process screen.

Cause:
The issue was in POST request code and low amount of key/value pairs, configured to send data from browser to server.

Fix:
The threshold was increased from 15000 to 1000000 at configuration file to avoid fails during the execution.

Testing:
Navigate to ‘COD WB Reconciliation Process'. Select 'Enterprise' as Strategic Education, Inc. Select 'Institution' as Strategic Education. Check 'Select all for Authorized disbursements'. Click 'Save, but do not run EST for AR' button. Green notification should be received: 'Process submitted successfully’. The process will start and will be shown in the Process Log.

Then, go to Processes > COD WB Reconciliation Process: Options. Select ‘Strategic Education, Inc' in ‘Enterprise' dropdown/Select ‘Strategic Education' in 'Institution' dropdown. Check 'Select all for Authorized disbursements' checkbox OR select some student(s), authorized as 'YES’). Click 'Save, but do not run EST for AR' button. The process should be submitted successfully

Problem:
'Process command failed' error occurred, when clicking 'Save, but do not run EST for AR' button at COD WB Reconciliation Process screen.

Cause:
The issue was in POST request code and low amount of key/value pairs, configured to send data from browser to server.

Fix:
The threshold was increased from 15000 to 1000000 at configuration file to avoid fails during the execution.

Testing:
Navigate to ‘COD WB Reconciliation Process'. Select 'Enterprise' as Strategic Education, Inc. Select 'Institution' as Strategic Education. Check 'Select all for Authorized disbursements'. Click 'Save, but do not run EST for AR' button. Green notification should be received: 'Process submitted successfully’. The process will start and will be shown in the Process Log.

Then, go to Processes > COD WB Reconciliation Process: Options. Select ‘Strategic Education, Inc' in ‘Enterprise' dropdown/Select ‘Strategic Education' in 'Institution' dropdown. Check 'Select all for Authorized disbursements' checkbox OR select some student(s), authorized as 'YES’). Click 'Save, but do not run EST for AR' button. The process should be submitted successfully

Problem:

Error during packaging due to incorrect anticipation of AYs even after 180-day student’s absence.

Cause:
Invalid starting Course Enrollment Number.

Fix:
New validation code check was done to prevent the error in future, the data cleanup script from RS-14643 was used to fix the incorrect data for existing students.

Testing:

MAP an affected student. Modify any existing award through MAW. Do batch packaging. Verify AY dates. Student shall be successfully packaged and AY dates re-calculated. Repeat for any other affected students.

Problem:
Regent Award was unexpectedly calculating Direct Loans amounts after importing FAH data for Previous Loan Period.

Cause:
Regent Award was incorrectly used NSLDS FAH data, when packaging a student.

Fix:
Regent Award is updated to ensure that NSLDS information for Previous Academic Years is properly accounted for ongoing Loan Period

Testing:
In Regent Award find student with FAH NSLDS imported last time prior to payment made in previous Loan Period. Package student and make sure Direct Loan amount in past and ongoing Loan Periods are not changed.

Problem:
After completion of the eAccess Smart Form, the eAccess ISIR Formatted file could not be imported into the school’s Student Information System (SIS) due to an invalid Parents’ Legal Residence Date.

Cause:
Incorrect data format settings in the system specification.

Fix:
The data format settings and metadata used to create the eAccess export were updated.

Testing:
Complete eAccess Smart Form as a student. Execute the eAccess ISIR Export Process. Upload the created eAccess ISIR file into SIS. The file should upload with no errors.

Problem:

Single Packaging or Batch Packaging process runs were blocked for multiple students with “A disbursement was not found in the student context which marks it for deletion; however, it cannot be deleted due to its current state as a mustNotDelete object” error message

Cause:
The application incorrectly deleted an award and its disbursements, created by "Cancel&Recreate" process, and marked it with "mustNotDelete" flag, if the award was restricted with ‘Unsatisfied’ document requirement.

Fix:
Regent Award logic was updated to cancel awards and its disbursements without deleting them during "Cancel&Recreate" process, if restricting "MustNotDelete" flag is present

Testing:
Package the affected student via Modify Academic plam. Open Process Log and analyze for no errors. Repeat the step for the other affected students and then run Batch Packaging for all students. BP shall have a status COMPLETE.

Problem:
For a Scheduled Academic Year (SAY) student, the Academic Year (AY) unexpectedly shifted after a mid-AY Program Change. The student was not enrolled in the Fall term of their previous program, and they had a Program Change in a Spring term with no course registration in the new program. The system unexpectedly did not mark the Fall term as Historic for the new Program.

Cause:
The system did not assign the initial, historic SAY term to the new program after a Program Change.

Fix:
The code change was applied so that the system recalculates the first AY, and assigns initial Historic SAY terms to the new program after a mid-AY SAY Program Change.

Testing:
Create a test student in a SAY program, with the program’s start date of the Spring term and no registered courses. Package the student, such as by using the Modify Academic Plan wizard (MAP). Observe that the student is packaged in the program with a historic Fall term. Load an SBL with a program change to a new program that also starts with the Spring term’s start date and has no course registration. MAP. Complete the Program Change as Substantially Equal. MAP. Confirm the SAY AY dates are correct and include the unenrolled Fall term. Confirm the student is active in the new Program.

Problem:
When R2T4 was finalized with manually modified 'Net Amount Accepted' having cents at PWD worksheet, the Direct Loans at Academic Plan grid were unexpectedly updated to the amount containing cents, instead of rounding to the nearest dollar basing on fund's setup.

Cause:
The fund rounding configuration was not properly applied to a PWD net amount during R2T4 finalization. The disbursements were set using the calculated PWD amounts instead of fund's configured rounding rules

Fix:
For Finalized R2T4 PWD amounts, the system uses the Rounding configured in Fund Setup and applies that Rounding to the PWD net amount.

Testing:
1) Create or open an R2T4 that results in a PWD. On the PWD Worksheet, provide a Net Amount Accepted value containing Cents. Enter the PWD Response Date. Save the PWD Worksheet. Finalize.
2) Package the student. Review the Academic Plan. Confirm that loan amount on the Academic Plan is rounded to dollars, per the configured Rounding option at Fund Setup.
3) Export the PWD disbursement to COD. View the COD Export File. Confirm the amount in the COD Export file is rounded to the nearest dollar and does not use cents. Make EST for AR. Open Academic Plan > Disbursement details. Gross, Net and Paid disbursement amounts are rounded to nearest dollar

Problem:
The previous Federal Award Year is not shown in the available FA Years list.

Cause:
The Document Setup incorrectly starts FAYs with a current year, so restricting an addition/update of a document for a previous year.

Fix:
The Document Setup was edited to enable selection of a previous year in the available FAY list.

Testing:
In Regent Award, go to Administration -> Document Setup -> Add Document -> Non ISIR Assignment Scope (Scope: Federal Award Year) -> Available FA Years. A previous year should be visible.

Problem:

After packaging, the Eligible Regular Pell Award amount is reduced for $1 at Academic Plan for the paid disbursement.

Cause:
The application incorrectly processed imported NSLDS Federal Award Year data that caused reducing Pell awards.

Fix:
The code was updated for the application to process the imported NSLDS FAY data correctly.

Testing:

Navigate to an affected student. Go to the Academic Plan tab and review the student’s Pell award amounts. Package the student. The application should have the award amounts rounded with no 1$ reduction. Repeat the steps for any other affected students.

Problem:
Regent Award was unexpectedly setting Payment Period Start Date in Overlapping Academic Year to be Academic Year start date from the previous school resulting in COD Reject.

Cause:
Regent Award was incorrectly Payment Period Start Date for Overlapping Academic Year containing one Payment Period to match the Academic Year Start date.

Fix:
Regent Award logic was updated to ensure for the single Payment Period dates are defined by Course Enrollment and match the Abbreviated Loan Period dates.

Testing:
In Regent Award find a student with Overlapping AY from the previous school. Package student and make sure Payment Period Start date matches with the earliest start date of Registered courses.

Problem:
The Regent Student Experience Portal did not display "Go to FAFSA on the Web" as a hyperlink in the Verification Worksheet.

Cause:
The hyperlink style was not applied to the "Go to FAFSA on the Web" link.

Fix:
The hyperlink style was applied to the "Go to FAFSA on the Web."

Testing:
Log into the Student Experience Portal using a test student account with a Verification Worksheet that includes the “Complete IRS Data Retrieval Tool (DRT)” page. Navigate to that page. Confirm the “Go to FAFSA on the Web” link is displayed as a hyperlink.

Problem:
2021-2022 Support of Dependent(s) Worksheet pdf file had wrong verbiage at HOUSEHOLD INFORMATION > Number of Adults in Household section.

Cause:
Incorrect wording in the Verification Worksheet questionnaire .

Fix:
The VWS was updated with a correct wording.

Testing:

In the student portal, open the Support of Dependent(s) Worksheet. It should ask: 'How many adults, not including yourself, currently live at your address?'

Problem:
At a school configured to Assume Attendance, when a user packaged a student using the Modify Academic Plan wizard (MAP), the Last Attended Date (LAD) was unexpectedly not updated to today’s date for the current open Payment Period (PP).

Cause:
The system did not check if the Course Enrollment rollup process was needed to be run before MAP.

Fix:
The code change was applied so that in MAP, the system will check if the Course Enrollment rollup process is needed to be run. If the CE process needs to run, the system will run it. The resulting LAD value will update to today's date in the open PP, and all other course data is updated for packaging the student.

Testing:
Navigate to Institution Setup and ensure that Assume Attendance field has a value of True. Reload RNA Setup if needed. Find the affected student. Filter by the Last Attended date in the Courses tab in an open PP. Observe the most recent course’s Last Attended Date. Perform MAP. Confirm the system updates the course LAD with today's date.

In the field ‘Parent income and Tax data’ in SNAP or StudentX, the hyperlink: ‘Request your tax transcript online’ redirects user to https://www.irs.gov/help/tools instead of redirecting to https://www.irs.gov/individuals/get-transcript .

Cause:
Hyperlink destination was not correct.

Fix:
Hyperlink destination was corrected.

Testing:
Open Parent income and Tax data in SNAP or StudentX. Press ‘Request your tax transcript online’. The hyperlink should redirect to https://www.irs.gov/individuals/get-transcript

Problem:
Styдes were missing for the links at 2020-2021 Verification Worksheet form at StudentX

Cause:
Hyperlink style was not applied to the ‘Request your tax transcript online’.

Fix:
Hyperlink style was applied to the ‘Request your tax transcript online’.

Testing:
At StudentX open VWS -> PARENT INCOME & TAX DATA -> IRS Tax Transcript/Tax Return Form section. 'Request your tax transcript online’ should be a blue hyperlink not a plain text.

Problem:

When clicking 'Select All' at Home > Tasks and Student > Tasks screens, all tasks in queue were selected, instead of selecting tasks visible only on the current page (20 items).

Cause:
A checkbox functionality bug occurred after upgrading the application from the previous release.

Fix:
The code is fixed to update the system behavior so that, when 'Select All' checkbox is clicked at Home > Tasks and Student > Tasks screens, only tasks visible on current page are selected.

Testing:
Navigate to any task queue with greater than 20 open tasks.

1. Apply the checkbox in the header of the task queue.
2. Apply a change to those tasks.

The change should only be applied to the first 20 items (the items on the first page or only the visible items).

Problem:
Term students had Pell disbursements that were unexpectedly refunded.

Cause:
The students had completed their original program and had a Program Change to a new program. The application incorrectly updated the Pell Grant for the old completed program.

Fix:
New code was added for the application not to update Pell Grants after completing the old program.

Testing:
Package the affected student. Run EST-for-AR. Verify that negative EST is not triggered

Problem:

Student Need Analysis Portal shows a 504 timeout error, when trying to upload questionnaire via an admin section.

Cause:
Questionnaire SQL import process required upgrading to avoid timeout problem.

Fix:
Questionnaire SQL import process was updated to increase efficiency of the questionnaire update procedure.

Testing:
Login to Student Portal with a user that has an administrator role. Import Questionnaire, make sure no timeout error occurs and the questionnaire is successfully deployed.

Problem:

The eTASFA application did not allow users to enter a negative value for the Adjusted Gross Income field.

Cause:
The application incorrectly allowed entering positive numbers only.

Fix:
The code was updated to allow negative values to be entered in the AGI field yet treat the negative value as zero in the EFC calculation.

Testing:

Register a new student. Start the Texas Application for State Financial Aid (TASFA). In the Student Income & Tax Data section, enter a negative value for the ‘Student's & Spouse's Combined AGI from Income Tax Return’ question. Confirm a negative value is able to be entered without an error message. Confirm the export file accurately lists the value in the correct format for negative numbers (e.g. see EDE Technical Reference for more information).

Problem:
Regent Award was unexpectedly recalculating R2T4 Pell amount $1 instead of $0 for the term where Pell is Year Round Pell (YRP) and enrollment is Less Than Half Time (LTHT).

Cause:
Regent Award was incorrectly rounding the R2T4 Pell amount in the Federal Award Year's last payment period.

Fix:
Regent Award logic is updated to ensure the R2T4 Pell amount in the FAY's last payment period was truncated to prevent incorrect rounding.

Testing:
In Regent Award find a student who has 100% of Pell already paid in current FAY and ongoing term could only be awarded by YPR portion of Pell. The student should have LTHT Enrollment for Pell Recalculation. Add R2T4 and make sure Pell Recalculated amount is $0

Problem:

The packaging via Modify Academic Plan wizard was blocked by the error message: “Failed to Process. Error Msg: Packaging error. Non-unique disbursement number(s) (9, 10) were detected in Federal Pell Grant [Internal Award ID XXXXXXXXX].”

Cause:
Regent Award was incorrectly assigning the disbursements numbers

Fix:
The code fix was added make correct assignment of disbursement numbers. The duplicate numbers will be re-enumerated if they have not been sent to COD

Testing:
Run EST-for-DRI the reported students. Observe no EST-005 override error. EST process should get 'Completed' status. Run packaging, no blocking errors should occur at Modify Academic Plan wizard

Problem:

Regent Award was unexpectedly showing the error message: “Sequence contains more than one matching element“ blocking the Advanced Packaging in the Modify Academic Plan (MAP) Wizard.

Cause:
Regent Award was incorrectly processing the Course Enrollments Program (CEP) after the A-B-A Program Change.

Fix:
Regent Award was updated to ensure CEP that belongs to Active Program is used.

Testing:
In Regent Award find a student with A-B-A Program Change. Navigate to the Academic Plan, MAP, Advanced Packaging. Proceed to Step 3 and make sure no error message appears.

Problem:
For some nonterm students, Regent Award was unexpectedly showing incorrect Anticipated Units and Weeks.

Cause:
Two problems were found. Regent Award incorrectly processed the first Payment Period (PP1) end date when a student did not have any registration on the second Payment Period (PP2). For some students, Regent also incorrectly set the Anticipated Units value to manual using the Modify Academic Plan Wizard, Advanced Packaging.

Fix:
Regent Award sets a nonterm PP1 end date regardless of the PP2 registration. Additionally, Regent ensures nonterm programs are not using manual Anticipated Units.

Testing:
In Regent Award, find an affected student. Repackage the student via Batch Packaging or Modify Academic Plan Wizard (Basic Packaging). Confirm the Anticipated Units, Anticipated Weeks, PP1 and PP2 end dates, and the Academic Plan structure are all correct.

Problem:
The 'SAP status' value in the SAP Wizard was not consistent with 'Current SAP status' value on Summary and Awards tabs.

Cause:
The application used different SAP status sources to display SAP status on Summary and Awards tabs--status imported from SBL records OR from Academic Plan records, ordered by SAP date.

Fix:

Code was updated for Regent Award so that SAP status will be selected from either source based on priority: First from the Academic Plan record(s), and then from the imported SBL records if there is no Academic Plan record(s).

Testing:
Add manual SAP status 'Satisfactory' at SAP wizard -> Run SAP. Verify that the status is updated at 'Summary' and 'Awards' tabs to 'Satisfactory'. Delete manual SAP. Import SBL with 'FA Probation' SAP status. SAP status should be consistent within 'Summary' tab, 'Awards' tab, and SAP Wizard.

Problem:
For a nonterm undergraduate student, Regent Award unexpectedly prorated the Pell Grant amount based on Registered Units when the student was not in a Shortened Remaining Period of Study (RPS) AY.

Cause:
Regent Award was applying the Manual Units from the Modify Academic Plan Wizard.

Fix:
Regent Award ensures the correct number of units for awarding Pell Grants.

Testing:
In Regent Award, find a nonterm student currently studying in Payment Period 2 of the Academic Year. Ensure the AY is not a shortened Remaining Period of Study, and the total registered number of units in Payment Period 1 and 2 are less than the required units in the Academic Year as defined in Program Setup. Package the student. Confirm the Pell Grant is awarded without proration.

Purpose of Script:

This on-demand data-cleanup script for nonterm students resolves a specific data scenario that can result in incorrect AY and PP1 start dates. The list-only version of the script identifies nonterm students who have a first non-transfer course in an AY PP1 where that course ends in a later PP2, resulting in an incorrect (later) date value for the AY and PP1 start dates. The update script corrects the start dates to match that initial course’s start date.

Data Changed by the Script:

The update version of the script will update the affected students' Course Enrollment (CE) records to start with the start date of the first non-transfer course in the Academic Year. The script also records an Activity Log Entry. When the students are repackaged, the AY and PP1 start dates will also change to match the corrected date values.

How to Access the Script:

Regent Award schools with nonterm students may open a CZ ticket and work with their Account Manager to run the script on demand. The root cause is fixed in 5.4.1.0.

How to Test the Script:

Before upgrade, in a test environment with nonterm students, run the list-only version of the script to identify any affected students. If any students are found, view the Academic Plan for an example student. Open the Program Management Wizard (PMW) and expand and view the Course Information. Observe the student has an initial, starting course that is earlier than the start date on the CE PP1 group. Close the PMW. Upgrade the environment to 5.4.1.0. Run the update script for the targeted students. View the script output results and confirm the student was processed successfully. Refresh the Academic Plan. Package the student. Confirm the Academic Year and Payment Period 1 dates are successfully changed to match the first actual course in the AY.

Purpose of Script:

This one-time data-cleanup script corrects the Academic Year (AY) dates for students who should have started a new Academic Year (AY) after their previous AY ended, and the students later had a Program Change into a new nonterm program. The affected students had duplicated AY dates in the new program, that incorrectly matched the AY dates from the old program.

Data Changed by the Script:

The script runs the Course Enrollment (CE) process to correct the linkage on the starting Course Enrollment number in the nonterm program. The system sets the new program’s first AY Start Date to the correct CE start date for the nonterm program. Upon repackaging, the system will correct the Academic Year dates for the affected students.

How to Access the Script:

Regent Award schools with nonterm students may open a CZ ticket and work with their Account Manager to run the script on demand. The root cause is fixed in 5.4.1.0.

How to Test the Script:

Before the upgrade, in a test environment with nonterm students, run the list-only version of the script to identify any affected students. View an affected student and observe the incorrect Academic Year dates. Upgrade the test environment to 5.4.1.0. Open the Program Management Wizard (PMW) and step through the PMW, making no changes. Refresh the Academic Plan screen. Confirm the Academic Year dates are not duplicated. Confirm the new AY starts with the Program Start Date for the new program.

Purpose of Script:

This build script ensures Regent Award is using updated course data for all students upon upgrade. In some cases, resource conflicts at the database level might have caused deadlocks and stopped the Course Enrollment Rollup (CE Rollup) process from completing. Some students might have had pending data changes, such as new course information from the Student Batch Load (SBL) process. For the affected students, the system could not update information such as total unit values.

Data Changed by the Script:

The script identifies any students that have course data changes or other SIS-provided data that was loaded but was not yet fully processed. The script then runs the Course Enrollment Rollup (CE Rollup) process for those students. The CE Rollup process updates the unit totals and other information.

How to Access the Script:

The script is included in the deployment of the 5.4.1.0 release. Each customer will receive this script update automatically when they upgrade to the 5.4.1.0 release.

How to Test the Script:

Before upgrading, find an affected student who had SBL data loaded in a failed CE Rollup process, where the student’s current course data do not match the unit totals on the Academic Plan screen. Package the student using the Modify Academic Plan wizard (MAP). Perform the upgrade. Refresh the Process Log. Confirm the Process CE Rollup process is Complete. View the affected student. Repackage the student using MAP. Refresh the Academic Plan screen. Confirm the total units match the course data.