What's fixed

TRUexchange and TRUsource versions 5.2 include fixes for the following issues.

TRC-3436

Add files page button overlap in some languages

When files were added to an RFQ, the buttons were overlapping on some TRUsource language pages. This issue is now fixed and the buttons are aligned properly.

TRC-3852

RFQ page button overlap in Safari

The Configure Questionnaire button was overlapping the other buttons when the TRUsource RFQ page was viewed in Safari. This issue is now fixed and the Configure Questionnaire button is aligned properly.

TRC-3913

TLS1.0 and TLS1.1 deactivation

TRUexchange web security is enhanced through deactivation of TLS1.0 and TLS1.1 protocols as they were identified as weak. The TRUexchange SaaS application and all integrations and TRUexchange clients are validated.

TRC-3912

Configuration cleanup

TRUexchange configuration files were cleaned up to remove invalid items. This cleanup simplifies the CICD scripts.

TRC-3914

TRUexchange SaaS-Tests results with Qualys SSL LABS Scan Tool

After deactivation of TLS1.0 and TLS1.1 protocols, security is enhanced and TRUexchange SaaS is again rated Grade A from the Qualys SSL LABS Scan Tool.

TRC-3921

Web Client session exception Issue

TRUexchange Web Client did not work properly due to session exception issues. The new version of the TRUexchange Web Client resolves the specific exception and the client is working properly.

TRC-3924

Issue with TRUexchange Desktop Client standalone version auto updates

Automated online updated were not triggered for the standalone version of TRUexchange Desktop Client. The new version of TRUexchange Desktop Client fixes this issue and automated online updates are triggered.

TRC-3998

Transaction Report filter not working properly

The Transaction Report in the new UI was not filtering records by transaction reference number properly. This issue is now resolved and the report provides the correct records.

TRC-4045

Incorrect number of records in GSN Active Users Report

The GSN Active Users Report in the new UI was showing an incorrect number of records. This issue is resolved, and the report shows the correct number of records.