Skip to content

Release Date: 10.10.2025

Summary

This release contains new functionalities and bug fixes.

Configuration Updates

See the full list here: Release 251010.1 - Boards

This release also includes changes to the Manage Access & Permissions section, as requested by Ankul via email on 10.10.2025.

Smoke Test cases:

User Story 55648: Configurable Document Metadata | Step | Action | Expected result | | ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Create any Cabinet record and upload all types of documents like primary, supporting and attachments | Record should be created with the uploaded documents | | 2 | Go to Documents tab, Check if all the uploaded documents are visible | All the uplaoded documents should be visible over here | | 3 | Check if all the documents should not have any classification field next to name of documents | There should not be any name classification detail next to document name for all the document types | | 4 | Click on Add or remove documents button | A new screen will appear where user can edit documet details | | 5 | Try renaming All types of documents | Editing should be allowed if user has edit permissions | | 6 | Try editing the document metadata like classification | Editing should be allowed if user has edit permissions, and after making changes, the updated Classification value should be displayed | | 7 | Chech if after each renaming of document, the modified by user name and time is correctly captured by using multiple accounts with edit access | The modified by user name and modified time should be correctly displayed | | 8 | Chech if after each Editing metadata (like classification) of document, the modified by user name and time is correctly captured by using multiple accounts with edit access | The modified by user name and modified time should be correctly displayed | | 9 | Try editing all types of documents with different accounts with edit access and check if modified by user name and modified time is correctly captured | The modified by user name and modified time should be correctly displayed | | 7 | Now create any other record with record type other than Cabinet and uplaod all types of documents | Record should be created with the uploaded documents | | 8 | Follow the same procedure from step 2 (Make sure classification field is not there for all record types other than Cabinet) | All the functionality stated above should work other than classification field |

Bug 59699: Allocator task is repeating twice - QwN, CQU, INF, SPE, VID, PPQ | Step | Action | Expected result | | ---- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | 1 | Create a record of type ADJ with all the required fields | The record should be created | | 2 | After creation of record, select the 'I want to' button | A pop-up window will appear with the Role assignment details and tasks | | 3 | Asign a allocator (if not done yet) and click on the 'Assign a task' dropdown | There should be only one task visible called: 'Allocate Lead Author' | | 4 | Follow the same steps and check in CQU and QON records | Result should be same as above |

Bug 59703: Unable to clone BRE, BRM, INF, SPE, VID records getting error
| Step | Action | Expected result | | ---- | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | 1 | Initiate and close a BRE record | The record is created and closed | | 2 | Select the 'I want to' button and click on 'Copy record' | A new screen will appear with details of coping the record | | 3 | Select record details or record details and documents option | | | 4 | Select the check box Copy recommendations and Relate record | | | 5 | Add the required roles and Click on 'Copy record' | The new record should be created | | 6 | Follow the same steps for INF, SPE, BRM records as well and check if copy record functionality is working | The new record should be created |

Bug 59771: Send back to reallocation, the expected task is 'sent back to allocator' instead of send on to lead author | Step | Action | Expected result | | ---- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | 1 | Initiate and close a BRE record | The record is created and closed | | 2 | Send the record to Allocator or Accountable Officer | The record should be now with allocator or accountable officer (whoever is assigned) | | 3 | Click on the 'I want to' button and select the task 'Send back for reallocation' | This action is for user to send back to Initiator for re-allocating Allocator or Accountable officer (which was previously assigned) | | 4 | Send the record to Lead Author | Record would be now with Lead author | | 5 | Now check if lead author have 'Endorse and send on for endorsement', 'Send on to Collaborators' and 'Send back to Accountable Officer' | Previously there was 'Send back for reallocation' action which should be now replaced with 'Send back to Accountable Officer' |

Bug 59783: Send button not enabled in ‘Endorse and Send to Secretary’ workflow when 'Briefing Due to Secretary' filed is filled while initiating CAB BRI | Step | Action | Expected result | | ---- | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | 1 | Initiate a CAB BRI record type with a date and time to the “Briefing Due to Secretary” field at step 2. | The record is created | | 2 | Move the record to Executive Director and Send the record to Secretary | The pop-up window will appear about the task for Secretary | | 3 | Fill in all mandatory fields in the “Endorse and Send on to Secretary” dialogue box. | | | 4 | Try to continue the workflow. | The Send button should be enabled after all mandatory fields are completed. |

Bug 59821: While testing cab CRD workflow, Review and Endorse section in the activity tab displayed blank | Step | Action | Expected result | | ---- | ------------------------------------------------------------------------------ | ---------------------------------------------- | | 1 | Create a new CabCRD record with all the necessary fields | The record will be created | | 2 | Send the record to the Decision stage following all the roles | The record will be now with the Decision Maker | | 3 | Check if there is data displayed in Review and Endorse section in Activity Tab | There should be data visible in this section |

Bug 59859: ADJ: Bug with 'All decide' feature, when 2 ED's are added it is not working as expected | Step | Action | Expected result | | ---- | --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | 1 | Create a new ADJ record | The record will be created | | 2 | Send the record to the Endorsers | There should not be 'All must agree' feature enabled over here | | 3 | Suppose the task is assinged to multiple Endorsers and any one of Endorser send the record forward. | The record should be sent to next role and all the previous endorsers tasks should be closed |

Bug 59890: Incorrect “Send Back” options available for Lead Author in workflow - applicable for all Parliament record types | Step | Action | Expected result | | ---- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | 1 | Create any Parliament record | The record is created | | 2 | Initiator sends the record to the Allocator for allocation. | The record should be now with Allocator | | 3 | The record moves to the Lead Author. | The record should be now with Lead Author | | 4 | The Lead Author attempts to send back the record. | Now, there should be option to send back record to Allocator as well as Accountable officer |

Bug 59915: Update the tracking status dropdown values for CAB BRI, CAB SUB

Step Action Expected result
1 Initiate all the mentioned records, and on Step 3 of creation phase check 'Tracking status' have the updated values shared in the Bug The dropdown values should now be the values shared in this bug

Bug 60188: Unable to generate PDF pack, getting error - Unable to create pdf pack
| Step | Action | Expected result | | --- | --- | --- | | 1 | Initiate the record type that required signature (Decision Maker) | The record should be created | | 2 | Go to the documents tab/Activity tab and click on 'View PPDF pack' | PDF pack should be generated and user should be able to view |

Bug 60436: Browser compatibility issue: Issue with Chrome | Step | Action | Expected result | | --- | --- | --- | | 1 | Check if the issue of Sved searches overlapping issue is fixed on the dashboard screen when width of screen is reduced | The issue should be fixed and there should not be any overlapping |

Bug 60603: Tracking status in the dashboard view is not displaying data.
| Step | Action | Expected result | | --- | --- | --- | | 1 | Create few new records with the Tracking status value added | Records should be created with the tracking status values | | 2 | Go to Dashboard screen and check if Tracking status column has values for these new created records | There should be the appropriate corresponding tracking value displayed for each of record types |

Bug 60608: Stage missing from filer panel
| Step | Action | Expected result | | --- | --- | --- | | 1 | On the Dashboard screen, check if Filter pane option have Stage field | There should be stage field displayed in this pane | | 2 | Select any of the desired stage and click 'Apply and save' button | The filter should be applied and only filtered records should be visible |

Package version: 2.2.17

Manual pre-deployment steps

Review 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 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 29 for Deploy Office Resources release pipeline in Azure DevOps to the target environment.
  2. 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_251010.1-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 Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)
  2. Select "Import from Zip" and import a new config ZIP file.
  3. The system will process the ZIP file and import the configuration. The list of configurations will refresh, and the imported configuration can then be selected and loaded.
  4. After importing, select the newly imported configuration from the dropdown list.
  5. Click the "Apply" button to apply the imported configuration.
  6. Wait for the confirmation message indicating that the configuration has been successfully applied.
  7. Select Update SharePoint Content Types button from the menu bar. Ensure that active 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.

Reindex the SharePoint Site

Role required: Brief Connect Administrator

  1. Go to Brief Connect SharePoint Site for the target environment
  2. Go to Site settings
  3. Go to Search and offline availability
  4. Click Reindex site

Rollback steps to previous version

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