Notifications are generated by Submissions and TCSI to provide the following information:
- Submissions
- Notifications from Submissions provide information on the status of various processes and may include messages relating to problems with data.
- TCSI
- Notifications from TCSI are generated when TCSI needs to call on other systems, such as the ATO, to verify or perform completeness checks on submitted data.
Notifications are updated automatically every five minutes. However, you can manually refresh the notifications to retrieve the latest notifications at any time. You can download notifications to Excel files for distribution, reporting, error correction, and so on.
Notifications detail updates regarding student loan validations, problems with students TFNs, and so on.
-
CHA category notifications are no longer issued to providers. The logic to retrieve a student's record and update the CHESSN on the student record has been removed.
-
CHESSN is no longer reported in Submissions. For further information on the ending of CHESSN reporting, go to the TCSI Support website.
Notification also details TCSI outages, such as planned maintenance, and system errors from Submissions. You can use the information in these notifications when logging issues with Tribal Support.
For error and warning messages, you may also receive near real-time error or warning messages from TCSI if your submitted data is either incorrect or inconsistent with information already submitted. Error and warning messages are displayed on the records of data groups and are not notifications.
You can sort and filter the notifications to view the notifications of interest. For example, you can display all notifications for load adjustments by filtering notifications on the Category by LRJ.
The image Notifications page illustrates the layout of the notifications page after you log in to Submissions.
Delete notifications
If you have the permission Notifications delete, you can delete notifications. Deleting notifications cannot be undone. However, if required, you can download the notifications to create a backup. For more information, go to Submissions permissions.
The image Delete notifications
Clear down notifications
Notifications can be scheduled to automatically clear down nightly based by enabling Notifications clear down in the Settings menu. Enabling this will schedule the process to run at 2 AM AEST. You must consider how this timeframe impacts integrations with Submissions.
The notification delete logic, described below, generalise the clear-down process. However, it is important to note the logic changes around CHESSN, SIS and S2E notifications.
Notifications delete logic
For every notification in Submissions Notifications table:
- If notification category = SIS or S2E or CHE or CHA
-
- If date added greater than 7 days?
-
Delete the notifications from Submissions Notifications table.
If any of these appear in the user interface and are known to have been resolved, you can manually delete them.
- Otherwise
-
Issue a B2G / notifications / <uid> call to retrieve the latest version of the notification.
- If response = 404
-
Delete the notification from Submissions Notifications table as the notification has been removed from TCSI.
- If response = 200
-
- If the status = EXPIRED or RESOLVED or COMPLETED
-
Delete the notification from Submissions Notifications table.
- Otherwise
-
Update the notification in the Submissions Notifications table if differences exist.
- If any other response from TCSI
-
Log the issue ensuring that the request URL, header, request JSON, response and response JSON can be sent to TCSI Support.
Overall impact
The overall effect of the overnight clear down is that the Notifications user interface contains only outstanding notifications and closely aligns with the TCSI Live Notifications report. If you observe significant differences between the TCSI Live Notifications report and the Notifications listed in the user interface, raise a ticket with Support.
An example test run in a test tenant with 3.5 million notifications resulted in clearing down to six notifications in total in the user interface, all generated within the last two days.
Tribal have raised the lack of notification status updates on a given notification. For example, a TFN notification does not maintain its lifecycle as depicted in the TCSI Notification documentation. As such, the notifications status is not maintained. TCSI Renewal Project have been informed of our requirement for adequate maintenance of a given notification status so that the solution can track the validation of TFN and USI moving forward.
This issue directly impacts the TFN verification status work being undertaken within Submissions and future USI verification status work.
If you wish to support the request for Notification status being accurately maintained against TFN and future USI notifications, raise a TCSI Support ticket requesting the status be maintained moving forward.
Example: TFN reporting and notifications
The diagram TFN reporting scenarios illustrates the reporting flow from when the TFN is recorded in the student management system, reported in Submissions, submitted to TCSI, then sent to the ATO. The diagram also illustrates when notifications are sent from TCSI to the ATO for verification, and when the TFN passes and fails verification.
