Skip to content

Release Date: 15th 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 cd0560f4-0852-4229-ac67-258bce1de461 :::

Package versions

  • briefconnect.server: 2.1.0-beta.158
  • briefconnect.client: 2.1.0-beta.201

Deployment and test instructions

Manual pre-deployment steps

N/A

Deployment steps (in order)

  1. Deploy Release 29 for Deploy Brief Connect App and Config release pipeline in Azure DevOps to the target environment.
  2. Deploy Release 25 for Deploy Office Resources 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 v250715.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 v250715.1 (Active) is selected from dropdown first.
  4. In the browser console via Developer Tools, run the command window.clearCache(). Example:
    image.png

  5. Upgrading Azure Function App Service Plan to Premium

    1. You will need Azure Command-Line Interface (CLI) PowerShell module installed and an account with Contribute or higher permissions on Azure Resource group
    2. Log in to Azure CLI, select tenant and subscription associated with the target Resource Group, using next PowerShell command

    az login --use-device-code
    3. Update variables with the actual values and execute next script in the same session where you logged in previously

     $resourceGroup = 'name of the resource group where environment resources provisioned'
 $functionAppName = 'name of Azure Function App resource'
 $consumptionPlanName = 'name of existing application name for Azure Function app'
 $premiumPlanName = 'name for the new application plan'
 $location = 'azure location (same as for other resources)'

 az functionapp plan create --name $premiumPlanName --sku EP1 --resource-group $resourceGroup --location $location

 az functionapp update --name $functionAppName --resource-group $resourceGroup --plan $premiumPlanName
    7. Run the Smoke tests below

v250715.1 Smoke Tests

Bug 66582: Region included column heading (plus Other):

Step Action Expected result
1 Navigate to Dashboard User should have access to Dashboard
2 Click on the '+ New record' button New Screen will be displayed : 'Initiate record'
3 Select any Record type and subrecord type and Click on 'Get started' New Screen will be displayed : 'Step 1 of 6: Enter the record's information'
4 Fill all the required fields on this screen and click on 'Next' button New Screen will be displayed : 'New Screen will be displayed : 'Step 1 of 6: Enter the record's information''
5 Scroll down and Click on Region field dropdown. All the available options are visible.
6 Verify that values does not contain "DWER Region" and "Other" Except "DWER Region" and "Other" values there should be other fields visible.

Bug 66810: Error when sending back to Accountable Officer from Decision make:

Step Action Expected result
1 Navigate to Dashboard User should have access to Dashboard
2 Create a new record of any record type New record should be created
3 Assign all the roles to appropriate persons Assinged roles will be displayed
4 In 'Activity' tab, send the record to Decision stage following each stage and assigning roles wherever necessary. Now record should be in Decision stage.
5 In 'Decision' stage, click on 'I want to' button and select 'Send back to Accountable Officer for changes' New pop-up appears with adding comments (optional)
6 Add comments if required and click 'Send' button Record should now be in 'Prepare and review' with 'Accountable Officer'

Bug 66138: Email template showing incorrect values - ABCLeadAuthor, ABCPrepareCollaborator, ABCAccountableOfficer, DWER_Endorser, DWER_QAOfficer, ABCRecommendRecommender, ABCTopicSummary

Step Action Expected result
1 Navigate to Dashboard User should have access to Dashboard
2 Create a new record of any record type New record should be created
3 Assign roles to appropriate persons Assigned roles should be visible
4 After record is created, try to change the person associated to a particular role The updated person should be assigned for that particular role
5 Check the Outlook inbox mailbox, to get the notification that there is change of role on that particular record The mail should state Who have changed the role and the name of the role should be visible (instead of internal name)
6 Try the same with different roles and re-assigning them For each change in role assingment, the mail should contain the new person associated and the name of the role (not internal name)

Rollback steps to previous version

  1. Complete deployment steps for Release notes v250708.1

Known issues

The following defects are still under active resolution as of 08 July, 2025. Please review each item for workarounds if applicable

ID Work Item Type Title Assigned To State Tags
65821 Bug Topic (Issue) and Purpose Statement Linked - and blanking required fields Ryan Ball E² ryan.ball@engagesq.com Active bc core v2.2; Release v250624.1
66134 Bug Proxy appearing in Activity incorrectly - Tasks assigned to user but activity showing on behalf of proxy Ryan Ball E² ryan.ball@engagesq.com Active
66140 Bug When sending to Collaborators multiple times, the emails are sent but the activity log doesn't record it Ryan Ball E² ryan.ball@engagesq.com Active
66142 Bug Add users on a multi-user role (eg collaborator or endorser) Ryan Ball E² ryan.ball@engagesq.com Active
66268 Bug Able to delete a recommendation (which can't be deleted) if you change a type Ryan Ball E² ryan.ball@engagesq.com Active
66764 Bug Email reminders not working for Proxy Expiration Ryan Ball E² ryan.ball@engagesq.com Active
66806 Bug Able to send to a person, even when the time is in the past Ryan Ball E² ryan.ball@engagesq.com Active
66818 Bug In UAT, "My records progress" not displaying record count as a centered number Ryan Ball E² ryan.ball@engagesq.com Active

Changelog

Time Change
15/07/2025 7:35pm Replaced automated terms deprecation with manual steps due to script issue