Skip to content

Version: v260401 (BC 2.5.3)

Summary

This release contains the following requirements changes, bugfixes and record subtype configuration items:

ID Title
693016 Outstanding Role config items
662910 (REQ-021) Customisable notifications
https://engagesq.zendesk.com/agent/tickets/15949 Remove date auto-calculation for Parliamentary record subtypes
https://engagesq.zendesk.com/agent/tickets/15939 Key Dates Sequence Reorder - CABMC & CABCC
https://engagesq.zendesk.com/agent/tickets/15938 Meeting Dates for all Cabinet and Appointment record subtypes
https://engagesq.zendesk.com/agent/tickets/15933 Document Required Signature for CABCC, APCAB, APCG, APGIC and APMIN (i.e., change default to 'YES')
https://engagesq.zendesk.com/agent/tickets/15882 Remove Ministers from DFFH Minister(s) dropdown values
https://engagesq.zendesk.com/agent/tickets/15881 Add a new Submission Type dropdown value for all DFFH CAB record subtypes
https://engagesq.zendesk.com/agent/tickets/15880 Due Dates and Time not to be required when Decision Maker records decision (sending on to Completer)
https://engagesq.zendesk.com/agent/tickets/15875 DFFH - Send back to previous role option appearing for Lead Author
https://engagesq.zendesk.com/agent/tickets/15869 move final reviewer out of recommender stage
https://engagesq.zendesk.com/agent/tickets/15859 Create a new permission group
https://engagesq.zendesk.com/agent/tickets/15935 PQN Not appearing on dashboard - DH Parliamentary Question subtype
https://engagesq.zendesk.com/agent/tickets/16000 DFFH & DH - PPQ Series (identifier) field tool tip edit request
https://engagesq.zendesk.com/agent/tickets/15833 Metadata field for client name
https://engagesq.zendesk.com/agent/tickets/15977 Add field 'CAB - Appointment (AP)' to Appointment record subtypes
https://engagesq.zendesk.com/agent/tickets/15995 Request to change subject line wording for role assigned notification email

Deploy Office Resources

  1. Navigate to Releases in the DFFH/DH Azure DevOps: https://ssudevelopment.visualstudio.com/Brief%20Connect/_release?_a=releases&view=mine&definitionId=3
  2. Select the appropriate release
  3. Trigger the release for the relevant environment that you are performing deployment for (DEV, TEST, PROD)

Manual post-deployment steps

Import config

Config file to import: (DFFH Configuration v260401-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.
  9. Wait 60-90 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).
  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.

Smoke Tests

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

  • As changes have been made to many core columns in this release, it is highly recommended that one of each record type is created during testing to confirm that each record type creates successfully and is working as intended.
  • Confirm that QAO within the EOB record is group-enabled
  • Confirm that Recommender role is group-enabled for BMIN, BCAB, CABSUB, APCAB, APGIC, APCG, APMIN
  • Confirm from the 'settings' page that a new notification section is visible, where users can create notifications for specific record types. Create custom notifications for each record type and confirm they are working as expected.
  • Confirm that DFFH Parliamentary records no longer include automatic date population
  • Confirm the correct ordering of Key Dates in CABMC and CABCC record subtypes
  • Confirm the 'Meeting date' field now resides at the top of the Key Dates tab, and beneath the Description field during record initiation
  • Confirm that Document Required Signature field for CABCC, APCAB, APCG, APGIC and APMIN field value are all defaulted to 'Yes' on record initiation
  • Confirm removal of 2 ministers from the DFFH Ministers field
  • Confirm addition of new Submission Type dropdown value for all CAB records
  • Confirm that the Record Decision transition should no longer be accompanied by a due date and time
  • Confirm that Lead Author no longer sees the 'Send back to previous role' option in the I want to menu
  • Confirm that the Final reviewer for BMIN and BSEC only, is no longer operating in the Recommend stage but rather in the Review stage
  • Confirm the creation and correct operation of the ME entra ID group
  • Confirm that NEW PQN records correctly appear on the dashboard after the normal dashboard update delay
  • Confirm that the 'Client full name' field is now available for MCO, OCO, SCO record subtypes
  • Confirm that DFFH Appointment record subtypes now have a prefilled value in the Submission Type field - CAB - Appointment (AP)
  • Confirm subject line change for role assigned notification correctly states 'notification only'

Rollback steps to previous version

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