Skip to content

Release Date: 12th August, 2025

Summary

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

::: query-table f4f8f64a-c493-490f-81f4-560df4c8625d :::

Package versions

  • briefconnect.server: 2.1.1-12
  • briefconnect.client: 2.1.1-10 (no change)

Deployment and test instructions

Manual pre-deployment steps

N/A

Deployment steps (in order)

  1. Deploy Release-36 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 v250812.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 v250812.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

v250812.1 Smoke Tests

Bug 66806: Able to send to a person, even when the time is in the past

  1. Create a record with all required fields.
  2. Click on "I want to" button and assign a person to a role.
  3. Select the Due Date and try to choose a time before the current time.
    • Expected behaviour: System should not allow selecting a past time, and Send button should be disabled.
  4. Select a Due Date/Time greater than the current date and time.
    • Expected behaviour: System should allow selection, and Send button should be enabled.
  5. Click Send.
    • Expected behaviour: Task should be assigned with the selected due date/time.

Bug 69073: Hypercare: Decision maker unable to edit Primary Documents

  1. Create a record with all required fields, upload Primary Documents, and assign the Decision Maker while not in the decision stage.
  2. After record creation, check if the Decision Maker can edit the Primary Documents.
    • Expected behaviour: Decision Maker should not be able to edit the documents.
  3. Progress the record to the Decision stage.
  4. Check if the Decision Maker can edit the Primary Documents.
    • Expected behaviour: Decision Maker should be able to edit the documents.

Bug 68897 Hypercare: Proxy for Collaborator has no actions

  1. Get two normal end-user accounts which do not have any special permissions - User A and User B
  2. Assign User B as a collaborator on the record
  3. Open the record as User A, you should not be able to open it
  4. Assign User A as User B's proxy and make a small change to the metadata, then save - this will trigger a permissions refresh on that record immediately
  5. Open the record as User A again, User A should be able to open the record
  6. Push the record on and assign a collaborator task to User B
  7. Open the record as User A again - User A should see the same I Want To workflow options as user B

Rollback steps to previous version

  1. Complete deployment steps for Release notes v250806.1

Known issues

Bug 68768 Hypercare: Admin functionality not working is still outstanding, but development work has commenced by e2 product engineering team