The release notes detail the new features, bugs, and known issues in release 2025.05.
Features
The table Features details the new features in release 2025.05.
|
Reference |
Header |
Business impact |
Affected topics |
|---|---|---|---|
|
533157 |
Enhanced PRODA logging - Support can log your PRODA device error |
Enhanced logging was recently added around TCSI API interactions so that better data can be provided to the TCSI Support team at a customer's request, or pro-actively by the Tribal Support team. Since then, it has come to our attention that customers have been receiving 500 errors when Submissions interactions with PRODA. PRODA uses a different set of URLs to:
Given the different URLs, our enhanced logging did not capture these failures in the logs. This has now been catered for by this fix. Customers receiving any sort of PRODA error in Submissions should raise a ticket with Tribal Support. Support will extract the relevant information, raise a TCSI Support ticket, and upload the extracted data to the TCSI Secure FTP server. |
|
|
570660 |
B2G API interaction batch size change |
Careful logging of TCSI B2G responses has revealed an issue with batch POST sizes. Currently, Submissions has a default batch size of 10. For example, if 100 new Unit enrolments were recorded, the Submissions service bus processing would split them into 10 batches of 10 Unit enrolments each to POST to the B2G API. However, it has been observed through the logging that TCSI will sometimes respond with an Analysis of these failures, which appear to be mostly associated with Unit enrolments, shows that typically seven of the records will be processed OK, but subsequent records in the batch fail. Therefore, the POST batch size will be reduced to six to avoid the TCSI B2G API timeout. Although, we have raised this with TCSI multiple times, a proactive approach has been decided and implementation of the change in Submissions to support our customers avoiding errors. |
Not applicable |
Bugs
There are no bug fixes in release 2025.05.
Known issues
There are known issues for the criteria builder, download records, and notifications.
Criteria builder
The known issues for the criteria builder are detailed below.
- URL length for bookmarking
-
URLs containing filter strings are limited to approximately 2,000 characters. Realistic scenarios suggest that a search with eight criteria creates a URL with around 1,000 characters. Complex criteria can be built, but customers should monitor URL lengths manually as the criteria builder does not currently track this. The message that the browser might return is The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
- Criteria 'is one of' and spaces
-
Avoid spaces when entering multiple criteria values. For example, entering a, b, c will only return results for a. Therefore, enter criteria without spaces a,b,c to correctly return results for all values. The team is addressing this issue to remove spaces automatically.
- Toggling element numbers clears filters
-
If a filter has been applied and the user toggles the element numbers on or off, the filter is cleared. This is because the fields in the criteria builder need to be refreshed based on the element number needing to be displayed.
Attention.This issue will not be addressed and customers will need to ensure the element number has been toggled correctly before creating a filter.
Download records
The download is limited to 10,000 records due to HTTPS timeout of 30 seconds.
Notifications
The known issues with notifications are detailed below.
- Notification status
-
TCSI notifications do not maintain a lifecycle status as documented by the TCSI website. As such, some notifications may not be deleted automatically. Examples of this are the SVE and VER notification categories, where during our testing these notifications were not updated or deleted. This could be due to the extensive age of the data.
If resolved notifications are still present in the Notifications user interface, then users with the Delete Notifications permission can manually select and delete them permanently to complete the tidy up of the outstanding list of notifications. If the manual deletion of some of these categories is problematic, please raise it as a concern.
If you manage these types of notification categories using integration and internal reporting, the clear-down process can be updated in a manner similar to CHE, CHA, S2E, and SIS notifications. That is, remove the notifications automatically once the notifications are older than seven days.
- Notification clear-down duration
-
Tests in a tenant with over three million notifications show that it takes many hours to complete the notification clear down. Although this was in a test environment, it still raises a risk. Therefore, customers with several million notifications should enable the Notifications Automation on a Friday. The clear-down process then starts at 2 AM on Saturday morning. Enabling the clear-down process on a Friday should reduce any impact on online users of the solution rather than if it runs during the week and it subsequently runs into business hours.