Skip to content

Brief Connect v2.4.1 Release Notes

Release date - 12th December, 2025

Package version: 2.4.1

New features requiring configuration

  • Maintenance mode

Brief Connect can now be placed into a maintenance mode to support activities like migrations and upgrades.

When enabled:

  • Normal users will see a maintenance message and be prevented from using the application
  • Super Admins can still access the application and will see a prominent maintenance banner
  • Background jobs and queue processing are paused to reduce the risk of data loss during maintenance windows

For setup and operational steps, see the Admin Guide: Maintenance mode.

Changes and improvements

  • Simplified signed document management (signed vs unsigned)

Documents now follow a simpler two-state model:

  • Uploading a signed copy replaces the displayed version while preserving the original unsigned document
  • Users can remove a signed copy to restore the original

  • Signature-enabled documents are shown as a single entry to reduce confusion

  • More control over who can create (and copy) records

Administrators can restrict record creation to specific users (or Entra ID groups) and optionally scope that permission to specific record types via Permission Sets. Record copying now also respects these same creation permissions.

For configuration steps, see: Controlling record creation permissions.

  • Task notification emails now include the sender’s comment

The “Record sent to me for action” email notification now includes the comment entered by the sender, giving recipients more context without needing to open the record.

Note

This change will only apply if you haven't already configured a custom notification template for the "Record sent to me for action" notification. Please speak with the Brief Connect team if you are using a custom template and would like to incorporate this change.

  • Improved frontend update reliability (automatic cache busting)

Client deployments now include automated cache busting and a client-side version check, reducing the likelihood that users will load stale UI bundles after an upgrade.

Bug fixes

  • Dashboard, search, and record header

  • Dashboard columns are now more reliable (pinned core fields, enforced key columns, and column reordering works as expected)

  • Fixed cases where saved search swapping could cause columns to appear blank until re-applied
  • Global search terms are now applied more reliably on the search page

  • Record header dates now display in a user-friendly, localised format

  • Workflow, access, and exporting

  • The “Send” button no longer stays disabled when due date/time is prefilled from Key Dates

  • The “View access is restricted to” field now supports multiple people
  • “Export record documents” now sends the expected email with documents

  • Fixed an issue where a workflow could break when a proxy user completed a Recommend-stage task on behalf of the original user (Recommenders role)

  • Documents and SharePoint

  • Fixed signed document classification getting stuck in a loading state

  • Improved Add/remove documents layout so action buttons no longer wrap unexpectedly
  • Fixed SharePoint file picker not loading sites due to Microsoft Graph Toolkit provider initialisation
  • Improved reliability of the “Original Correspondence” document lifecycle (upload/delete/display) and related user feedback
  • Improved SharePoint sync/upload error handling in some environments

  • Fixed an issue where non-admin users could receive a 500 error during correspondence upload/parsing

  • Plugins and security

  • Plugins are now compatible with strict Content Security Policy (CSP) configurations

  • The Admin panel now respects the Plugins feature flag

  • Platform reliability and data correctness

  • Reduced noise in the activity log (removed redundant entries and irrelevant SharePoint health alerts)

  • Improved stability of the HealthCheckAndFix function (avoids failures due to the 30-minute timeout in some environments)
  • Server-side token replacement now respects the configured server timezone (rather than always rendering AEST)
  • Supplementary Area reporting now stores “Due Date and Time” values correctly, and the people-search input is cleared after selection
  • PPQ Bulk Set Extraction / bulk update now applies changes as expected