Version: 260212 (BC 2.5.1)
Summary
This release contains the following requirements changes, bugfixes and record subtype configuration items:
| ID | Title |
|---|---|
| 672291 | Update permissions for DH records so that the 'Recommend' stage is now Read-only for regular users |
| 667925 | Appointment: Health ministers are missing from the DH Ministers field |
| 669229 | CORRO and EOB need the 'correspondence fields' toggle to default to visible |
| 668979 | Step 2 has incorrect tool tip |
| 668983 | Amend 3 Requested Action titles in record initation stage |
| 669007 | Duplicates in Correspondent type |
| 669754 | BSEC - duplicates in drop down options for requested actions |
| 670667 | Briefing: SBR: multiple Decision Makers are allowed |
| 670694 | Appointment: GIC (APGC) should be GIC (APCG) |
| 670033 | Cabinet: Cabinet records should default to Restricted - Cabinet in Confidence |
| 670273 | Portfolio list requires 2 amendments |
| 667306 | Appointment: templates are missing from all record types |
| 667307 | Parliament: templates are missing from all record types |
| 668037 | Briefing: templates are missing at record creation |
| 663000 | (REQ-076) Additional signature instructions for other role types |
| 668892 | Briefing: EBR: Decision Maker's Signature field missing |
| 669753 | Key Dates contains mandatory fields and is a collapsible section |
| 671310 | Briefing: SBR: Office, Lead Portfolio and Additional Portfolios are not required |
| 670120 | Parliament: QWN: "Perform final task" step is not required in the workflow |
| 670899 | Recipient metadata filed not required - CORRO and EOB |
| 665379 | PDF pack - incorrect fields |
| 670047 | Correspondence: Key Dates and Correspondence fields are concealed |
| 669095 | Parliament: The finalise steps include "Finalise and close" and "Close the record" tasks |
| 669269 | Parliament: PCQ: Template automation not working |
| 669266 | Correspondence: CMIN/DDR: Decision Maker to be optional upon record creation |
| 669268 | Correspondence: CMIN: duplicated values in the Correspondent Type field |
Known bug
There is a known bug that is restricting standard users from being able to upload Primary and Attachment documents to records. For this release, we have opened up the permissions configuration so users are able to do this, but are still determining the cause of this bug. This means that in some instances users may be able to do more than they are supposed to, but will be able to test uploading and moving documents between Primary and Attachments.
Role assignments that have been edited to now enable document edit access fully:
SC SCE DHBN BN BCMD
Manual post-deployment steps
Import config
Config file to import: DFFH Configuration v260209-config.zip
Role required: Brief Connect Administrator
If there is no configuration set, you have to set up Administrator user Id in the Environment variable
AdminEntraIdin the Azure Function App. The value should be the Object Id of the user in Entra ID (Azure AD).
- Log into the target Brief Connect environment as the Brief Connect Admin user and open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel).
- Select Import from Zip and upload the new configuration ZIP file.
- The system will process the file and refresh the list of available configurations. Once it appears, select the newly imported configuration from the dropdown.
- Click Apply to apply the imported configuration.
- Wait for the confirmation message that the configuration has been successfully applied.
- Make sure the active configuration is selected in the dropdown.
- In the menu bar, click Update SharePoint Content Types.
- Tick Clean up unused fields from content type. It won't remove any data, only detach unused fields from Content Types, then click Confirm.
- Wait 20 minutes for the process to finish.
- Click Cleanup Unused Fields from SP Lists, then Confirm in the confirmation dialog. This process will cleanup unused fields from lists (fields provisioned with old configs and removed in later configs).
- Wait for 10 minutes for the process to complete.
Clear the Server cache
Role required: Brief Connect Administrator
- Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (
https://[WEB_APP_URL]/#/adminPanel) - Open browsers Developer Tools, open Console tab and run the command
window.clearCache()there. After successful execution, you should seeCache cleared. Server Result: truemessage in the console.
Smoke Tests
We recommend following our basic testing guide after this release: Basic testing of Brief Connect - Brief Connect Documentation
- Navigate to corresponding PBI's/Bugs in attached list of items to confirm functionality and test accordingly.
Rollback steps to previous version
Execute all deployment steps for the target release from related Release Notes.