Version: v251027.1

Release Date: 27th October, 2025

Summary

This release includes a major update for the core Brief Connect platform (upgrade from 2.1.10 --> v2.2.19). Please review all the changes here: Brief Connect Release Notes - Brief Connect Documentation. Password: WeLove2ReadTheBCDocs!!

This release also provides fixes/updates for the following items:

• Ticket: Bug: Document Names overlapping – Engage Squared – Zendesk / Bug 70317 Hypercare: Document Names Overlapping
• Ticket: Update task takes 3 mins to complete – Engage Squared – Zendesk / Bug 68752 Hypercare: Update Task taking ~3min sometimes to complete and unblock UI
• Ticket: Bug: Brief Connect filenames and… – Engage Squared – Zendesk / Bug 70417 Brief Connect filenames and special characters
• Bug 66818: In UAT, "My records progress" not displaying record count as a centered number

Package version: 2.2.19

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.0.0`. 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. 

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