Skip to content

Release Date: 20th August, 2025

Summary

This release includes fixes for the below items, raised by the DWER team

::: query-table 6e653728-d244-4a15-8d6b-9c4072eacb27 :::

Package versions

  • briefconnect.server: 2.1.4
  • briefconnect.client: 2.1.4

Deployment and test instructions

Manual pre-deployment steps

N/A

Deployment steps (in order)

  1. Deploy Release-37 for Deploy Brief Connect App and Config release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

  1. Log into the target Brief Connect environment as an admin user. Open the Admin Panel (the /adminPanel page, e.g. https://briefconnectdwerwa-cdne.azureedge.net/#/adminPanel is the dev url)
  2. Import and apply new config via AdminPanel: Active Configuration v250820.1-config.zip (ensure latest config is selected before clicking apply)
  3. In AdminPanel in your target environment, select Update SharePoint Content Types button from the menu bar. Ensure that Active Configuration 250820.1 (Active) is selected from dropdown first.
  4. In the browser console via Developer Tools, run the command window.clearCache(). Example:
    image.png ```
  5. Run the Smoke tests below

v250820.1 Smoke Tests

Bug 69239 Hypercare: Unable to access original correspondence & Bug 69480 Hypercare: Original Correspondence is showing a filename, but there's not file in SharePoint for it

  • Create a CGEN record and ensure you upload a correspondence file when you are creating it --> Once the record has been created, view the correspondence file and check the URL for the correspondence file
    • It should not be in Personal Storage
    • Create a CGEN record without uploading a correspondence file when you are creating it --> Once the record has been created, upload a correspondence file. Then go back to the record and check the URL for the correspondence file
    • It should not be in Personal Storage

Bug 69615 Hypercare: Edge case where the collaborator can be assigned to the role multiple times * Create a new record * Assign user to Collaborator role - e.g. User A * Open People and Roles tab, then try to assign User A to Collaborator role --> when searching for User A, you should get no results. * Push record to Lead Author role in workflow * Open Send On to Collaborators step * Perform same search for User A when adding a new Collaborator --> when searching for User A, you should get no results.

Bug 69648: Hypercare: Renaming files on the documents tab shows incorrectly in the Activity Log

  • Open a record with a document
  • Rename a document
  • Check Activity log --> Observe it accurately records the name change (and includes the old name)

Bug 68768: Hypercare: Admin functionality not working

For each Business Admin group type (ODG, ODDG & MLU), perform the following actions * For records that the user is administrator for, confirm that the user can progress a record even when not named in the record (i.e., the user can see and interact with the 'I want to' options for that record type) * For records that the user is administrator for, confirm that the user can access the record even if it is sensitive

Rollback steps to previous version

  1. Deploy Release 36 for Deploy Brief Connect App and Config release pipeline in Azure DevOps to the target environment.
  2. Follow steps in Release v250812.1 - Overview