Version: v251209 (BC 2.3.6)
Summary
This release contains the following items:
| ID | Title |
|---|---|
| 665070 | Cabinet configuration - CICSUB |
| 665071 | Cabinet configuration - CICAR |
| 665072 | Cabinet configuration - CICMC |
| 665073 | Cabinet configuration - CICCC |
| 663841 | Cabinet: CABMC/CABCC: Recommender is not multiple |
| 664139 | Parliament: PQON: Completer role is duplicated |
| 663794 | Cabinet: CABSUB: Lead Portfolio(s) instead of Lead Portfolio |
| 663830 | Cabinet: CABSUB: Final reviewer is not multiple |
| 663728 | Permissions change: Initiators for all record types able to 'withdraw' & 'NFA' (new requirement) |
| 662726 | (REQ-004) Multiple sequential Recommenders |
| 663434 | Cabinet: CABAR: Phase field is missing selectable values |
Package version: 2.3.6
Manual pre-deployment steps
Review/update release pipeline variables
It's important to apply any changes for all environments 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
- Go to Azure DevOps, open Brief Connect project
- In left panel navigation go to Pipelines - Library - Variable groups
- Review variables for all environments and update where required (outdated values, recent environment changes, requests from business, etc).
- Save the changes
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.3.1`. 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. Pipeline deployment steps (in order)
- Deploy release Release 21 for Deploy BC - Office Resources release pipeline in Azure DevOps to the target environment.
- 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
Import config
Config file to import: DFFH Configuration v251209-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
- Complete the initiation process for the following Cabinet record types: CICSUB, CICAR, CICCCC, CICMC
- Confirm that the records are created
- Confirm metadata and roles outlined in documentation
- For CABMC and CABCC record types, confirm that the 'Recommender' role is now a multi select role
- Confirm for the PQON record type that the Completer role is no longer duplicated across record stages
- For CABSUB record type, confirm that the Final Reviewer is a multi-select role
- Confirm that Initiators can now 'Withdraw' a record using the OOTB workflow controls in the 'I want to' menu. Please note, due to the limitations of permissions configurations currently, this change will apply across all record types.
- Confirm that all DFFH records allow multiple recommenders, and the Recommender task must be completed by all Recommenders for the record to progress
- For CABAR record type, confirm phase field is working as intended
Rollback steps to previous version
Execute all deployment steps for the target release from related Release Notes.