The release notes detail the new features, bugs, and known issues in release 2024.10.
Features
The table Features details the new features in release 2024.10.
|
Reference |
Header |
Business impact |
Affected topics |
|---|---|---|---|
|
402937 |
TFN Verification - Permissions |
A new permission TFN verification has been added to Submissions. This allows a user holding that permission to trigger a TFN verification with TCSI and the ATO. It is recommended that this permission is granted only to users that understand the impact of triggering a verification after the notification has been received that the TFN verification period has ended. |
|
|
441937 |
Delete notifications permission |
A new permission Notifications delete has been added to the Submissions area. This permission enables users to delete notifications in the Notifications UI. |
|
|
402938 |
Student UI - Trigger TFN verification |
The UI for the student data group has been updated to support a new button Send for TFN verification. Permissions are needed to use the button. If the correct permission is held, selecting one or more records results in the button being enabled with a count of selected records. Selecting the button results in a confirmation. The user can cancel the action if required or continue with the action. Continuing results in the TFN verification process being triggered within TCSI and the ATO. Customers should use this process when they receive a notification that the TFN verification process has expired or the student has subsequently informed them the ATO has been updated with the correct information. Note that the confirmation modal includes a validation on the student records submission state. Those records in error, pending update, pending delete or processing states cannot be sent to TCSI and the ATO for TFN verification. Those updates or states must be resolved first. Records matching these states are called out in the confirmation panel. Attention.
To avoid issues or unnecessary data verification errors, use a filter or search to ensure that only appropriate record submissions states can be included in the process. Note that users cannot send records for verification by filter. Individual records must be selected to ensure that the user is fully aware of their action and the expected outcomes. If the number of records that cannot be processed exceeds the size of the confirmation panel, a vertical scroll bar appears. This does not provide the best user experience. However, it is important to note the above regarding using filters to ensure only records that have been submitted successfully or are in warning can be selected. There are no performance implications expected as it is anticipated this will be a moderately used feature given the time it takes for some students to respond to TFN activity, including working with the ATO to have issues updated. |
|
|
402939 |
Student UI API |
The API has been changed to support triggering the B2G PATCH API call to start a TFN validation. |
Not applicable |
Bugs
There are no bug fixes in release 2024.10.
Known issues
RTP scholarship data
Issues with historical RTP scholarship data were found to cause issues with data migration. The root cause appears to be when RTP Scholarships in HEPCAT are created against reporting periods that are then migrated to TCSI as follows:
-
Reporting period one migrated as E609: 01/01/YYYY and E610: 30/06/YYYY.
-
Reporting period two migrated as E609: 01/07/YYYY and E610: 31/12/YYYY.
Problems have been found when attempting to match student management system data to the TCSI data due to the following:
-
Submissions RTP scholarships data migration not partially matching as expected (resolved in 2021.08 under AMS 850891).
-
Major discrepancies in the way that pre-TCSI RTP scholarship data is recorded in the student management system and then sent to Submissions. For example, the student management system has one RTP scholarship with a start date of 02/04/2017 and an end date of 30/10/2019; this record covers six reporting periods and cannot easily match to any of the RTP scholarships migrated from HEPCAT to TCSI.
-
Instances where Submissions has matched incorrectly to a TCSI RTP scholarship. For example, if a UID exists against an RTP scholarship but the attempted PATCH has resulted in a 10376 or 10430 error, the match will need to be removed by the Tribal support team before any remedial work can take place on the student management system data.
Note that it is possible to re-attempt the migration of the RTP Scholarship record once the parent Course admission has already been migrated. This should only be attempted where the TCSI data matches what has been sent to Submissions by the student management system to avoid the above issues.