28 January 2025

Submissions release notes

The release notes detail the new features, bugs, and known issues in release 2025.01.

Features

The table Features details the new features in release 2025.01.

Features

Reference

Header

Business impact

325177

Delete notifications permission

A new permission has been added to the Submissions area. This permission controls whether a role can delete notifications in the Notifications user interface.

358267

Notifications UI updates

The user interface for Notifications has been updated to allow a user, with the correct Submissions area permissions, to select notification records and delete them from the system. This cannot be undone. It is suggested that users use the download feature to create a backup of the notifications where required.

The user will be presented with a modal dialogue confirming the delete action. Users can confirm or cancel the action.

A new menu option Notifications automation, under the Submissions Settings menu, has been created to enable or disable the nightly Notifications clear-down process. Enabling this will schedule the process to run at 2 AM AEST. Customers should be aware of this timeframe in case it impacts their integrations with Submissions.

If customers want the clear-down to occur at a different time, they will need to raise a ticket and communicate the time they wish the clear-down to run. The Tribal DevOps can then run a pipeline to update the default 2:00 AM AEST time.

The following bugs have also been fixed:

  • Inconsistent naming of the grid header record when toggling the column names between a data group and then switching to the Notifications page.

  • Downloading an empty filtered result set returned a JSON error.

Bugs

There are no bug fixes in release 2025.01.

Known issues

RTP scholarship data

This known issue will be removed from all future release notes due to its age and the understanding that impacted students may have completed their studies.

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.