Skip to content

Release Date: 13th, June, 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 82eece79-e0c6-41a8-bbb2-2efb63290448 :::

Package versions

  • briefconnect.client: 2.1.0-alpha.120 (update)
  • briefconnect.server: 2.1.0-alpha.97 (Update)
  • briefconnect.configsync: 1.2503.71

Deployment and test instructions

Manual pre-deployment steps

N/A

Deployment steps (in order)

  1. Deploy Release-26 for Deploy Brief Connect App and Config release pipeline in Azure DevOps to the target environment.
  2. Deploy Release-19 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 v5-250625.1.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 v5_v250624.1 (Active) is selected from dropdown first.
  4. In the browser console via Developer Tools, run the command window.clearCache(). Example: image.png
  5. Reindex site
  6. Go to SharePoint Site
  7. Go to Site settings
  8. Go to Search and offline availability
  9. Click Reindex site
  10. Run the Smoke tests below

v250624.1 Smoke Tests

  • During initiation of a record, confirm that a new non-mandatory field 'Migrated record' has been added to support migration from CTS
  • As an administrator, create a record that has it's Information Security Classification set to 'Sensitive'. Make sure only the admin account is given roles on this record. From a regular user account, attempt to access this record.
  • Create the following record types: CMIN, CDG, CGEN. And confirm that there is an 'Other' option for the following fields
    • CMIN: Ministerial type
    • CDG: Correspondence type
    • CGEN: Correspondence type
  • For any record type, progress the record so that the record is with a Collaborator. Confirm that the next action available to the collaborator is 'Complete collaboration task' instead of review task.
  • From the settings screen, navigate to the Manage Proxy access section. Confirm that selecting the 'Edit end date' and 'request to remove' proxy buttons automatically open an email with correct information
  • During record creation, confirm that the 'information security classification' field is defaulting to 'Official'
  • (note, this test will only work after reindexing the site - make sure to do this as a post deployment step) Confirm that the following fields are now populating in the dashboard:
    • Decision maker
    • Drafter
    • Stage
    • Accountable officer
    • Collaborator
    • Information security classification
    • Approver
    • Noter
    • Due date with Drafter
  • Upon record creation, confirm that the 'Topic' field has been renamed to 'Purpose statement' to remove confusion over why this field is populating when purpose statement is edited.

Rollback steps to previous version

  1. Deploy backup of SearchConfig to SP Site: SearchConfiguration (6).xml
  2. Complete deployment steps for Release notes v250613.1

Known issues

The following defects are still under active resolution as of 24 June, 2025. Please review each item for workarounds if applicable - For Bug 65820 - 'Act by date' is still not populating in the dashboard. This fix is ongoing.