Release Notes - CRT v6.13.353, TPRM v3.1.56, & SGA v3.1.35
The above versions were released on 4/23/2025. This article contains information about what was included in those releases.
BUG FIXES
- #2608 - Administration > Task Library - An issue was found where the Client name was not being shown on Task Library Details page even though tasks has been assigned to a client by a user. This was reviewed and resolved in this release.
- #2789 - Reporting > Stat Analysis - It was found that inside the Procedure Summary, the Policy and Practices Number were not being updated. This was adjusted and confirmed to now function as expected.
- #2833 - Login - In certain situations users were being presented with an error message when they would log in for the first time and attempts to view the engagement details under Administration > Manage Client. The cause was identified and resolved.
- #2835 - Administration > Authentications - It was found that if a user had the PSR of "User" that the list of previously created engagements does not show up when a user create a new engagement. This was reviewed and resolved.
- #2854 - Administration > Application Settings > SMS Settings - Inconsistency in functionality between TPRM and SGA portal configuration settings and CRT portal configuration settings
- #2920 - Maturity Management > Synced/Aligned Practices: It was found that if a managed finding was being shown multiple times, and it is added three times once one is chosen. This has been resolved.
- #3055 - Third Party Risk Management Portal > Set Password: When creating a password, commas and dots are not considered special characters, but the system accepts them. This has been reviewed and updated.
- #3141 - Login Screen - It was identified that the label color for error messages was incorrect. The color was updated to the expected color so the error message is viewable to the user as expected.
- #3189 - Maturity Management - Users found when trying to add initial evidence to a managed finding that the "Add Evidence" button was missing, but if the user had already added evidence via Compliance Management the "Add Evidence" button would appeared. This has been resolved in this release.
- #3205 - Risk Register > Risk Item - It was found that certain required fields within the Risk Register module have no indicator to say they are mandatory/required. The UI was reviewed, and field that were missing the "*Required" field had the indicator added. This indicator appears only if the fields are set to "Required" as part of the setup, and they indicators will only appear once the record is saved.
- #3232 - Compliance Management > Assessments > Assessment Plan Report - It was found that the report version was displaying "NaN" as the version number rather than a valid version number. This was resolved in this release.
- #3279 - Third Party Risk Management Portal > Assessments - It was found that vendor users were able to inadvertently bypass the configured Assessment Pack logic if the user
- #3305 - Third Party Risk Management > Assessment List - An issue was found with drop menu's when there are one or two assessments that the drop lists would not function properly/display the data properly. The drop menu was displaying within the HTML div only. This has been resolved.
- #3308 - DCMS > Document - When editing text fields if a user navigates away from the screen the record does not save. The system has been updated so it is auto-saving while editing a document.
- #3311 - Risk Register > Risk Item > Engagement Tab - While saving data within the engagement tab data wasn't saving as expected. The issue was reviewed and resolved so the data now saves as expected.
- #3313 - Risk Register > RR Management > Compact Form Settings - Internal testing discovered that the tab title name was incorrect. This was resolved as expected.
- #3321 - Risk Register > Risk List/Risk Item - Users found that there was sometimes a mis-match in the saved Risk Status on the risk item, and the displayed risk status in the risk list. This mapping / display issue was resolved.
- #3330 - Administration > User Security - An issue was found when a new user was created, and the user attempted to select their primary security role, the system would throw an error message. This has been resolved.
ENHANCEMENTS/FEATURES
- #2870 - OSCAL: the Open Security Controls Assessment Language - Initial investigation and estimation
- #3182 - DCMS - Users found that when you were adding attachments to a document the evidentiary items were being mixed with the published document within the UI. This is now been broken into separate functions.
- #3184 - Repository Configurations > Weblink Usage - Simple updates to make utilization of weblinks more effective within the user interface.
- #3255 - Risk Register - We've added the "Created By" and "Created By Date" fields to the user UI for visual auditing purposes.
- #3278 - Third Party Risk Management > Assessment Packs - An option has been added that allows for users to configure packs to allow assessment completion in a series format (one must be completed after another) or parallel format (any assessment in the pack can be completed in any order).