Skip to content

Version: v260226

Release Date: 26th February, 2026

Summary

This release contains improvements and bug fixes to the MongoDB database approach.

Bug fixes

Detailed bug list can be found here: Bug fixes 26/02/2026

Deployment

Package version: 2.5.2

Manual pre-deployment steps

Update environment variables

Update environment variables for all environments in Libraries - Variable Groups in in Azure DevOps

See the detailed instruction in Admin Guide 2.5.0 - Application Settings

Each environment should only have next required variables:

Name Is Required
appSettingsJson true
applicationDomainName true
azureFunctionAppName true
azureFunctionDomainName true
azureResourceGroupName true
azureStorageAccountWebName true
azureWebApiWebAppName true
clientAppRegistrationClientId true
devOpsAppRegistrationClientId true
serverAppRegistrationClientId true
sharePointSiteUrl true
tenantId true

Include existing FeatureFlags in appSettingsJson parameters. For example, for DEV environment it will have next value (fill the gaps with actual values from Function App settings or other sources, according to the admin guide): {"AppName":"BC/Assent DEV", "AuthorizedGroupId": "put group id here", "AuthorizedGroupName":"put group name here", "EmailNotificationsServiceAccount": "account UPN here", "TopHeaderBannerText": "BC Development Environment", "FeatureFlags__EnablePluginEditor":"true", "BundleStore__BundleStoreKind": "FileShare", "BundleStore__FileShareName": "put the file share name here"}

Setup Release Pipelines

  1. Rename Deploy Brief Connect Application release pipeline in Azure DevOps to [OLD] Deploy Brief Connect Application.

  2. Import Pipeline JSON and rename

  3. Import the release pipeline .json file provided (refer to: Release Pipeline Template - Deploy App).

  4. Note: This template is pre-configured for a single environment associated with a deployment stage within the release pipeline.
  5. Rename the pipeline to "Deploy Brief Connect Application".

After importing the pipeline, you need to update several settings to tailor it to your environment.

  1. Add and setup environment (first)

  2. To deploy to a new environment (e.g., DEV) rename the initial stage to the target name. Use the same environment/stage name from [OLD] Deploy Brief Connect Application pipeline.

  3. Open stage tasks
  4. Update Agent Pool specifications to the old values from [OLD] Deploy Brief Connect Application stage Agent Pool task (agent pool and specification).
  5. In the Universal Packages task Download App Package, update the service connection ('organization/collection connection' dropdown) to use the same service connection as in the old release pipeline.
  6. In the Azure CLI task Deploy App, update Azure Resource Manager connection to use the same connection from 'Azure CLI' task or 'Azure Functions Deploy' task in the old release pipeline.

  7. Go to Variables tab, select "Variable groups", click on "Link variable group" and link variable group for this environment. Make sure only 1 Variable group is linked to 1 environment (in following steps when you clone environment it will keep the link, so you need to remove it)

  8. Repeat previous step for all other environments from old release pipeline. For every new environment you need to clone and rename the initial environment from the previous step.

  9. After all configurations, save the Release Pipeline.

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.
  2. Deploy Release 36 for Deploy Office Resources release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Import config

Config file to import: DE-Config_260216-config.zip

Role required: Brief Connect Administrator

If there is no configuration set, you have to set up Administrator user Id in the Environment variable AdminEntraId in the Azure Function App. The value should be the Object Id of the user in Entra ID (Azure AD).

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)
  2. Select "Import from Zip" and import a new config ZIP file.
  3. The system will process the ZIP file and import the configuration. The list of configurations will refresh, and the imported configuration can then be selected and loaded.
  4. After importing, select the newly imported configuration from the dropdown list.
  5. Click the "Apply" button to apply the imported configuration.
  6. Wait for the confirmation message indicating that the configuration has been successfully applied.
  7. Select Update SharePoint Content Types button from the menu bar. Ensure that active configuration is selected from dropdown first.

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.

Reindex the SharePoint Site

Role required: Brief Connect Administrator 1. Go to Brief Connect SharePoint Site for the target environment 2. Go to Site settings 3. Go to Search and offline availability 4. Click Reindex site

Smoke Tests

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

Additional recommended smoke tests:

Smoke Test: Dashboard Count Matches Visual Graph | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Navigate to the Dashboard - My records tab.
| Dashboard loads successfully.
| | 2
| Click on the ‘Filter’ button.
| Filter fly-out panel is displayed.
| | 3
| Expand ‘Due Date Decision Maker’.
| Due date values are displayed.
| | 4
| Review the due date values in the list.
| Dates are displayed in correct user-friendly format and not in ISO format (e.g. 2025-02-24T13:00:00Z).
|

Smoke Test: Dashboard Count Matches Visual Graph | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Navigate to the Dashboard - My records tab.
| Dashboard loads successfully.
| | 2
| Apply a filter for Stage = Initiate.
| Filter is applied and results are displayed.
| | 3
| Check the ‘Results’ count in the grid.
| Count is displayed.
| | 4
| Check the corresponding stage count in ‘My records progress’ graph.
| The graph count matches the grid result count.
|

Smoke Test: Filters Apply on Closed Records Tab | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Navigate to the Dashboard - Closed records tab.
| Closed records list is displayed.
| | 2
| Click on the ‘Filter’ button.
| Filter fly-out panel is displayed.
| | 3
| Apply a filter for Record Type (e.g. Cabinet or Committee Briefing).
| Filter is applied.
| | 4
| Review the grid results.
| Only records matching the selected record type are shown.
|

Smoke Test: Keyword Search in Active Tasks Tab | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Navigate to the Dashboard - Active tasks tab.
| Active tasks list is displayed.
| | 2
| Enter a valid record number or keyword in the search field.
| Search is triggered.
| | 3
| Review the results displayed.
| Only matching records are displayed and the result count updates correctly.
|

Smoke Test: Documents Tab - Unexpected ‘Test’ Column | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Open a Cabinet record.
| Record loads successfully.
| | 2
| Navigate to the ‘Documents’ tab.
| Documents list is displayed.
| | 3
| Review document columns.
| No unexpected column named ‘Test’ is visible.
| | 4
| Click ‘Bulk edit details’.
| Classification dialog opens without displaying a ‘Test’ field.
|

Smoke Test: PPQ Bulk Update - Business Admin Access | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Log in as a CPU Business Admin user.
| User is logged in successfully.
| | 2
| Navigate to a PPQ record.
| Record page loads successfully.
| | 3
| Click on the ‘Bulk update’ button from the top right.
| Bulk update page opens successfully.
| | 4
| Verify access to the page.
| No permission error message is displayed.
|

Smoke Test: Cabinet Record - Classify Documents Feature | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Create or open a Cabinet record (e.g. CabBRI).
| Record loads successfully.
| | 2
| Move the record to Recommendation stage.
| Record transitions successfully.
| | 3
| Navigate to the ‘Documents’ tab.
| Documents tab loads.
| | 4
| Attempt to classify a document in Primary or Attachment section.
| Classification option is available and functional.
|

Smoke Test: Upload Signed PDF Document | Step
| Action
| Expected Result
| | --- | --- | --- | | 1
| Open a Cabinet Sub record in Decision stage.
| Record loads successfully.
| | 2
| Click ‘I want to’ → ‘Upload signed documents’.
| Upload dialog opens.
| | 3
| Click ‘Add or remove documents’.
| Document selection screen opens.
| | 4
| Upload a signed PDF to Primary or Attachment section.
| PDF uploads successfully without error message.
|

Rollback steps to previous version

Execute all deployment steps for the target release from related Release Notes.