HomeGuidesChangelog
Changelog
Back to All

RegScale 6.29.2.1

March 23rd, 2026

[6.29.2.1] 2026-03-23

Changes

  • Chatbot Improvements

    • Enhanced system prompts and guardrails to reduce hallucinations and improve response accuracy and reliability.

Fixes

  • Evidence Module

    • Fixed an issue where the search field returned “0 Records” despite matching entries existing.

  • SSP Export

    • Resolved an issue where Security Categorization was not populating correctly in exports.

  • FedRAMP POA&M

    • Fixed an issue preventing POA&M exports from completing successfully.

  • Form Builder

    • Fixed an issue where form field validations could not be deleted and did not appear in the builder.
    • Resolved an issue where validation field values were not populating correctly.
    • Fixed tab panel not updating when switching between modules.
    • Fixed fields panel not refreshing when switching between modules.

  • SSP Control Implementation

    • Fixed a 404 error occurring when saving a part within a Control Implementation.
    • Resolved an issue where the control preview was not displaying.

Implementation Limitations and Known Issues in this Release

This is for everyone to be aware on any updates for SSO that involve our government customers.
With the .NET 10 upgrade that was part of our 6.29.X release there is no leniency in the verification of the login URL for SSO. There are now two Azure urls. Previously either could be used, they both return the same data indicating the .com url. If the customer is not GCC high, their validation is actually in the commercial (.com) not the government endpoint (.us).

Symptoms: The Console in the browser shows an “Issue mismatch”.

Resolution: If OAuth from Azure Entra fails after upgrading a customer to 6.29.X and their Authority url contains login.microsoftonline.us change it to login.microsoftonline.com.

Other

  • To avoid unexpected timeouts and being logged out of the application, set the session timeout value greater than the browser inactivity value. Session timeout is being enforced prior to inactivity. There is currently no warning to the end user before being automatically logged out of the application.

  • Inorder to delete an Interconnection the user must have both Update and Delete permissions.