Skip to content

BC v251205.1 (2.3.6)

==================

Release Date: 5th December, 2025

Summary

This release contains:

  1. One user story:
ID Title Work Item Type
(https://dev.azure.com/engagesq/Brief%20Connect/_workitems/edit/60969/) Notification Delivery Based on Record Access Permissions User Story

This user story disables notifications for users who do not have access to the record. 2. The following bug fixes: Bugs fixes v251205.1 3. Changes to CabSUB, CabBRI, CabCRD record types to enable agreed draft stage:

  • Allocator role was moved from Initiate stage to Prepare and Review stage.
  • Record permissions were updated so that only Initiator (and Administrators) has access to the record in the Initiate state.

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

  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 and update where required (outdated values, recent environment changes, requests from business, etc).
  4. 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. ![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

Import config

Config file to import: DE-Config_251205-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 AdminEntraId in the Azure Function App. The value should be the Object Id of the user in Entra ID (Azure AD).

  1. Log into the target Brief Connect environment as the Brief Connect Admin user and open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel).
  2. Select Import from Zip and upload the new configuration ZIP file.
  3. The system will process the file and refresh the list of available configurations. Once it appears, select the newly imported configuration from the dropdown.
  4. Click Apply to apply the imported configuration.
  5. Wait for the confirmation message that the configuration has been successfully applied.
  6. Make sure the active configuration is selected in the dropdown.
  7. In the menu bar, click Update SharePoint Content Types.
  8. Tick Clean up unused fields from content type. It won't remove any data, only detach unused fields from Content Types, then click Confirm. cleanup-ct-fields

  9. Wait 20 minutes for the process to finish.

  10. 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). cleanup-list-fields

  11. Wait for 10 minutes for the process to complete.

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.

Notifications Logic App Workflow deployment

1. Workflow deployment

Package to deploy: LogicApp

List of Workflows:

  • DueInMoChanged
  • NominatedLeadAuthor
  • NominatedSupplementaryAreaContributors
  • ParliamentItemIsClosed
  • SupplementaryAreaContactsChanged
  • TrackingStatusIfClassifyCabinetRecords

For each workflow in the list, repeat the steps:

  1. Open the folder labelled with the workflow you want to deploy (eg. DueInMoChanged)
  2. Open the workflow.json file in VS Code or editor of choice, and copy the JSON.
  3. Open the Logic App resource in Azure Portal.
  4. In the left-hand menu, click Workflows
  5. If workflow with this name doesn't exist, then create it first using the steps below. If exist, then go to the next step
  6. Click Add, name the new workflow "DueInMoChanged".
  7. Select Stateful, then click Create.
  8. Wait until the workflow is created.
  9. Open the workflow and switch to the Code view.
  10. Paste in the JSON from the workflow.json file that is in the corresponding folder (eg. DueInMoChanged folder -> workflow.json).

2. Add Workflow Settings

  1. Open the Logic App resource in Azure Portal
  2. Go to Workflows -> Open any workflow -> Parameters

  3. Add the following parameters TBD:

    Parameter Example Value Type Description
    authAudienceString <client-id> String The Azure App Registration Client Id for the Brief Connect Server app registration
    briefConnectDoEDEVHomeString https://briefconnect.com/#/ String The homepage URL of Brief Connect, be sure to include the /#/ that is present in the URL
    serviceAccountEmailString serviceaccount@briefconnect.com String The service account UPN used to send emails for the notifications
    webApiBaseURLString https://briefconnectapilink.net/ String Base URL used for making API calls to the Brief Connect API, with trailing / at the end.
    cpuRecordTypesArray "Adjournment Debate (ADJ)", "Constituency Question (CQU)","Question on Notice (QON)","Question Without Notice (QWN)","Possible Parliamentary Question (PPQ)", "Cabinet Submission (CabSUB)","Cabinet or Committee Briefing (CabBRI)", "Coordination Comment Briefing (CabCRD)","Briefing for Decision (BRD)" Array An Array used to control was subtypes are controlled / under the purview of the CPU Team.
    cpuTeamEmailString serviceaccount@briefconnect.com String The group mailbox of the CPU Team, used to send emails to their inbox

3. Add Webhook for each workflow

After deployment, register a webhook in Brief Connect so new records trigger the Logic App.

LogicApp name PartitionKey RowKey Order
DueInMOChanged 2 DueInMOChangedWebhook 1
NominatedLeadAuthor 2 NominatedLeadAuthorWebhook 1
NominatedSupplementaryAreaContributors 2 NominatedSupplementaryAreaContributorsWebhook 1
ParliamentItemIsClosed 2 ParliamentItemIsClosedWebhook 1
SupplementaryAreaContactsChanged 2 SupplementaryAreaContactsChangedWebhook 1
TrackingStatusIfClassifyCabinetRecords 2 TrackingStatusIfClassifyCabinetRecordsWebhook 1

For each workflow in the table, repeat steps below:

  1. Copy the Logic App trigger URL:
    • Azure Portal → Logic App → Workflows → [LogicApp name] → Trigger → "Show callback URL"
  2. Create the webhook in the Azure Table via Azure Portal:
    • Azure Portal → Brief Connect Resource Group → Brief Connect Data Storage Account → Storage Browser → Tables → WebhookSubscription
  3. Add a webhook entity to the table with the following details
  4. PartitionKey: data from [PartitionKey] column
  5. RowKey: data from [RowKey] column
  6. Endpoint: Paste trigger callback URL from the Step 1
  7. Order: data from [Order] column

PLEASE NOTE: If the name of the workflow's trigger is EVER updated, the webhook row in the table must be removed and recreated using the trigger's new callback URL.

Smoke Tests

We recommend following our basic testing guide after this release: Basic testing of Brief Connect - Brief Connect Documentation

Rollback steps to previous version

Execute all deployment steps for the target release from related Release Notes.

Known Issues