Skip to content

Version: v250301.1

Release Date: 3rd December, 2025

Summary

This release includes several bug fixes and improvements. Please review all the changes here: Brief Connect v2.3.5 Release Notes.

Key updates

Key changes introduced in Brief Connect v2.3.5 include:

  • Resolving frequent user reauthentication requests Some end users recently found Brief Connect would force them to log in more frequently, following an upgrade to version 2.3.2 or higher. We've implemented a fix for this, so login prompts should return to their normal frequency
  • Limiting notifications to users who don't have record access We've made a change to the default behaviour of notifications - now, a user will not receive notifications for a record if they don't have access to view that record in the first place.
  • Incorrect links to Original Correspondence We've implemented a fix to records where there were some cases of links to 'Original Correspondence' files being incorrect.

Package version: 2.3.5

Manual pre-deployment steps

Review release pipeline variables

It's important to apply any changes to pipeline variables before a release created, because every release creates a snapshot of pipeline variables on the moment of creation, and the only way to re-deploy the application with updated variables is by creating a new release or modifying a previous release.

  1. Go to Azure DevOps, open Brief Connect project
  2. In left panel navigation go to Pipelines - Library - Variable groups
  3. Review variables for all environments included in this release and update the values where required.
  4. Save the changes

Create release for 'Deploy Brief Connect Application' release pipeline

  1. Go to Azure DevOps, open Brief Connect project, go to Pipelines - Releases page
  2. Find Deploy Brief Connect Application release pipeline, click on it to open
  3. If there is no release with a version specified in Package version section above, then execute the instruction below in the "Create new Brief Connect Application release" section to create a new release.

When you create a new release, the release name should have the following pattern: v[Package Version] (n), where (n) just a counter, in case of multiple releases created for the same package version.

Create new Brief Connect Application release (click to expand) 1. Go to Azure DevOps, open Brief Connect project, go to **Pipelines - Releases** page 1. Find **Deploy Brief Connect Application** release pipeline, click on it to open 1. Click on **Create Release** button on the right 1. Specify the **Package Version** variable with value from **Package version** section above. For example `2.3.1`. 1. Add a description (it's optional). 1. Click on **Create** button 1. Release with version `v[Package Version] (0)` will be created and will be available in the list of releases, after you refresh the page. ![image.png](../.attachments/new-application-release.png)

Pipeline deployment steps (in order)

  1. Deploy release v[Package Version] (n) (where (n) is latest number available, and Package version from the section above) for Deploy Brief Connect Application release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Clear the Server cache

Role required: Brief Connect Administrator

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)
  2. Open browsers Developer Tools, open Console tab and run the command window.clearCache() there. After successful execution, you should see Cache cleared. Server Result: true message in the console.

Smoke Tests

We recommend following our basic testing guide after this release: Basic testing of Brief Connect - Brief Connect Documentation