Skip to content

Version: v251015

Release Date: 17th October, 2025

Summary

This release includes fixes for the following bugs:

ID Work Item Type Title Assigned To State Tags
642076 Bug The Cancel button does not work in the Details page of created CMIN records Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015; Stage1_Priority
642505 Bug CMIN: Sending record onto Accountable Officer as Allocator: 7am defaulted and send button is greyed out Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015; Stage1_Priority
642507 Bug CMIN/CABSUB: Decision maker recommendations can be changed (and ticked/unticked) by the finaliser after a decision has been recorded/made by the decision maker Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015; Stage1_Priority
642827 Bug Records the user does not have access to are displayed in the dashboard under Open records Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015; Stage1_Priority
642882 Bug CMIN: Export PDF for completed record: PDF Pack is only 1 page long Deklan Heider E² \deklan.heider@engagesq.com New Dev; Release v251015
643089 Bug CABSUB: PowerBI: Record Details report missing the "time for delivery" and "time sitting with Decision Maker" columns Patrick Campion (Health) \patrick.campion@health.vic.gov.au New Power BI; Release v251015
643135 Bug Unable to see non-restricted records in "Open Records" Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015
643371 Bug PowerBI: Detailed Roles Report is missing some fields Patrick Campion (Health) \patrick.campion@health.vic.gov.au New Power BI; Release v251015
643373 Bug PowerBI: Closed Records (FOI) report missing stage at closure field Patrick Campion (Health) \patrick.campion@health.vic.gov.au New Power BI; Release v251015
643375 Bug PowerBI: Record and Task Volumes: filter not loading Patrick Campion (Health) \patrick.campion@health.vic.gov.au New Power BI; Release v251015
644033 Bug Power BI report details not displayed for some users Patrick Campion (Health) \patrick.campion@health.vic.gov.au New Power BI; Release v251015; Stage1_Priority
644590 Bug Not able to access the original created correspondence if the user is not the Decision Maker Ryan Ball E² \ryan.ball@engagesq.com New Dev; Release v251015
645052 Bug "Withdraw" option missing when Accountable Officer is assigned to the record Patryk Dymon E² \patryk.dymon@engagesq.com New Release v251015
645205 Bug dffh used instead of DFFH in the select text for some fields Ryan Ball E² \ryan.ball@engagesq.com New Release v251015; Stage 2 Consideration
645236 Bug Comments are recorded twice times when the user hold all the roles Deklan Heider E² \deklan.heider@engagesq.com New Release v251015; Stage1_Priority

Package version: 2.2.19

Manual pre-deployment steps

Review release pipeline variables

It's important to apply any changes to pipeline variables before a release created, because every release creates a snapshot of pipeline variables on the moment of creation, and the only way to re-deploy the application with updated variables - creating a new release

  1. Go to Azure DevOps, open Brief Connect project
  2. In left panel navigation go to Pipelines - Library - Variable groups
  3. Review variables for all environments included in this release and update the values where required.
  4. Save the changes

Create release for 'Deploy Brief Connect Application' release pipeline

  1. Go to Azure DevOps, open Brief Connect project, go to Pipelines - Releases page
  2. Find Deploy Brief Connect Application release pipeline, click on it to open
  3. If there is no release with a version specified in Package version section above, then execute the instruction below to create a new release. Release name should have the next pattern: v[Package Version] (n), where (n) just a counter, in case multiple releases created for the same package version.
Create new Brief Connect Application release (click to expand) 1. Go to Azure DevOps, open Brief Connect project, go to **Pipelines - Releases** page 1. Find **Deploy Brief Connect Application** release pipeline, click on it to open 1. Click on **Create Release** button on the right 1. Specify the **Package Version** variable with value from **Package version** section above. For example `2.0.0`. 1. Add a description (it's optional). 1. Click on **Create** button 1. Release with version `v[Package Version] (0)` will be created and will be available in the list of releases, after you refresh the page. ![image.png](/.attachments/new-application-release.png)

Pipeline deployment steps (in order)

  1. Deploy release v[Package Version] (n) (where (n) is latest number available, and Package version from the section above) for Deploy Brief Connect Application release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Manual post-deployment steps

Role required: Brief Connect Administrator

  1. Go to Brief Connect SharePoint Site for the target environment
  2. Go to Site Contents
  3. Open "Header links" list
  4. Create a new list item with next values:
  5. Tooltip: Logout
  6. Icon Name: SignOut
  7. Href: /logout
  8. Order: 6
  9. LinkType: Internal
  10. IsMobile: unchecked
  11. IsAdminOnly: unchecked

Import Latest Configuration File

Config file to import: DFFH Configuration v251013-config.zip

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel) > If there is no configuration set, you have to set up Administrator user Id in the Environment variable AdminEntraId in the Azure Function App. The value should be the Object Id of the user in Entra ID (Azure AD).
  2. Select "Import from Zip" and apply new config via AdminPanel.
  3. Ensure latest config is selected from the dropdown and click Apply.
  4. In AdminPanel in your target environment, select Update SharePoint Content Types button from the menu bar. Ensure that uploaded configuration is selected from dropdown first.

Clear the Server cache

Role required: Brief Connect Administrator

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)
  2. Open browsers Developer Tools, open Console tab and run the command window.clearCache() there. After successful execution, you should see Cache cleared. Server Result: true message in the console.

Smoke Tests

Please execute the following smoke tests after completing all deployment steps:

  • Assign a user to all roles, and leave a comment in the Activity Log of a given record. Confirm that the comment is only entered once.
  • Confirm that a user not in the Decision Maker role can access Original Correspondence for a given Correspondence record when the record is with the Decision Maker
  • Confirm that the cancel button in the Details page of a given record behaves correctly
  • Confirms correct configuration of permissions so that users cannot see record types they should not have access to. For e.g., attempt to access a Restricted record from an account that has not been named on the given record.
  • Confirm that non-restricted records created by other users are visible in the Brief Connect dashboard in the 'Open records' tab
  • Confirm that the 'export to PDF' button on the dashboard is exporting a PDF that encapsulates all records selected
  • Confirm that the AO can withdraw a record at all stages, except the closed stage
  • When an automated date is has been configured, confirm that when progressing a record on and when an automated date is populated, the 'Send on' button is no longer greyed out and can be selected without any editing of date and time.
  • Confirm the removal of 'dffh' instead of 'DFFH' in the DFFH Minister, Portfolio, and Non-DFFH Portfolio selection fields
  • Confirm that the Completer role cannot edit Decisions or Recommendations at the Finalise stage
  • Confirm correct details in the Roles PowerBI report
  • Confirm correct details in the Closed Records (FOI) PowerBI report
  • Confirm the 'Time for delivery' and 'Time sitting with Decision Maker' columns have been added to the Record Details report
  • Confirm that the filter in the Record and Task volumes report is correctly loading
  • Confirm report details are loading for all users who have access to reports