Release Date: 21st July, 2025
Summary
This release includes fixes for the below items, raised by the DWER team. There are both bugfixes and requirements included in this release. ::: query-table e5f1b089-9f8f-4dae-9e5e-8f2c8a821a73 :::
Package versions
- briefconnect.server: 2.1.0-beta.165
- briefconnect.client: 2.1.0-beta.201
Deployment and test instructions
Manual pre-deployment steps
N/A
Deployment steps (in order)
- Deploy Release 30 for Deploy Brief Connect App and Config release pipeline in Azure DevOps to the target environment.
Manual post-deployment steps
- 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)
- Import and apply new config via AdminPanel: Active Configuration v250721.1-config.zip (ensure latest config is selected before clicking apply)
- In AdminPanel in your target environment, select
Update SharePoint Content Typesbutton from the menu bar. Ensure thatActive Configuration v250715.1 (Active)is selected from dropdown first. - In the browser console via Developer Tools, run the command
window.clearCache(). Example:
``` - Run the Smoke tests below
v250721.1 Smoke Tests
Bug 66733: Field Order of Key Roles for Correspondence mixed up
1. Open any PQ / EVAP record, or create a new one
2. Review the order of Key Dates, ensure it follows the correct order:

Bug 66134 Proxy appearing in Activity incorrectly - Tasks assigned to user but activity showing on behalf of proxy 1. Log in as a user (User A) who is a Proxy for another user (User B) 2. Create a new record, assign all roles to User A 3. Complete some workflow tasks 4. Review the activity timeline and ensure it does not say User A completed the task on behalf of User B
Rollback steps to previous version
- Complete deployment steps for Release notes v250715.1