Skip to content

Brief Connect v2.6.1 Release Notes

Release date - 11th August, 2026

Package version: 2.6.1

This is a patch release that enables SharePoint library title rename migration by default, improves record notification settings, and resolves workflow, document, sign-in, SharePoint provisioning and health, background job, and audit logging issues.

New features and improvements

  • Enable SharePoint library title rename migration by default

    In this release, Brief Connect automatically applies the new SharePoint document library naming model (introduced in v2.6.0) to existing record document libraries, so existing libraries align with the current record type + sequence naming logic.

    This migration updates only the SharePoint library Title for existing libraries. It does not change the underlying library path/URL, so existing document links continue to work without any changes.

    For details on the record document library model, see Solution Design - Record Documents.

  • Remove Sites.Read.All application permission from the Server Application registration

    Brief Connect no longer requires the Microsoft Graph Sites.Read.All Application permission on the Server Application registration.

    You can safely remove this permission and revoke the associated tenant admin consent for all Brief Connect environments.

    For the current required permission set, see Solution Design - Server Application permissions.

Improvements

  • Improve timeline consistency for AllMustDecide tasks

    We've made general improvements to the Activity timeline view, specifically for AllMustDecide-style tasks, to ensure they consistently show the appropriate user and their actions.

  • Better logging into Application Insights

    We improved our logging into App Insights, while reducing instances where log entries were duplicated.

  • Improve background SharePoint provisioning and health recovery

    Record creation and migration health processes now use smaller, more reliable background messages and report queue failures more clearly. Failed SharePoint provisioning can be retried reliably from the stored record data.

  • Improve ActionOverdue configuration and deduplication handling

    ActionOverdue configuration is now stored as actionoverdue:config and managed in Admin Panel → Plugins → Edit Data. Obsolete notification-history storage is removed. Each daily run sends at most one reminder for each eligible overdue task and continues to skip closed records and muted users according to the saved configuration.

  • Improve document move duplicate-name validation and error handling

    Document move operations now clear stale validation errors and handle duplicate file names more reliably.

Bug fixes

  • Fix key date updates being discarded

    Pending changes in the Key Dates tab are no longer discarded if the record silently fetches metadata updates in the background.

  • Fix client-side caching issue that blocked sign-in

    Client-side caching no longer prevents users from signing in.

  • Fix transition window dynamic resizing

    The workflow transition window now resizes dynamically as expected.

  • Fix upload error for original correspondence documents

    Uploading an original correspondence document now works correctly when other correspondence files are already present.

  • Fix record document visibility for group members

    Users assigned through group membership can now view record documents as expected.

  • Fix immediate post-initiation record progression stage update

    Record stage updates now succeed when users progress a record immediately after initiation.

  • Fix group hydration in background record field updates

    Background record field updates now retain group owners and members correctly for User Groups assigned by plugins.

Known issues

  • Initiator role does not receive role-assignment permissions after initiation

    In some scenarios, when a record is initiated, the user in the Initiator role is not granted record permissions when record created.

    Affected users can lose access to the record after initiation, and the record may not appear in My Records or search results for non-admin users.

    A fix is being prioritized for the upcoming hotfix release.

    Workaround: After initiation, assign the user directly to any alternative role, so record permissions are applied.

Upgrade instructions (from v2.6.x)

The following instructions apply to environments already running Brief Connect v2.6.x.

Manual pre-deployment steps

Review release pipeline variables

Apply any changes to pipeline variables before you create a release. Each release snapshots variable values at creation time, and you must create a new release to redeploy with updated variables.

  1. Go to Azure DevOps and open your Brief Connect project.
  2. In the left navigation, go to Pipelines -> Library -> Variable groups.
  3. Review variables for all environments included in this release and update values where required.
  4. Save any changes.

Create a new release

  1. Go to Azure DevOps, open your Brief Connect project, and go to Pipelines -> Releases.
  2. Open the Deploy Brief Connect Application release pipeline.
  3. If there is no release with version 2.6.1, click Create Release.
  4. Set the Package Version variable to 2.6.1.
  5. Add a description (optional).
  6. Click Create.
  7. The release v2.6.1 (n) is created and appears in the release list after refresh.

Pipeline deployment steps

  1. Deploy release v2.6.1 (n) (where (n) is the latest number available) from the Deploy Brief Connect Application release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Remove obsolete Microsoft Graph application permission

Role required: Tenant Administrator

  1. Open the Server Application app registration in Microsoft Entra ID for the target environment.
  2. Go to API permissions.
  3. Remove the Microsoft Graph Sites.Read.All permission where Type is Application.
  4. Revoke admin consent for this removed permission.

Smoke tests

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

Release-specific tests for v2.6.1

Deployment and health

  • SharePoint library title migration — Requires: System Administrator.

    • Setup and action: Before deployment, choose an existing v2.6.0 record library and capture its display title, URL, and working record and document links. After deployment, open App Health, confirm SPLibraryTitleRenameMigration completes, and recheck the library and links.
    • Expected result: The library receives its sequential record type and sequence display title. Its URL is unchanged, and the existing record and document links still open.

  • Server Application permission removal — Requires: Tenant Administrator.

    • Setup and action: Remove the Microsoft Graph Sites.Read.All application permission from the Server Application as described in the post-deployment steps. Sign in, open the dashboard and an existing record, open a document, and create a representative record.
    • Expected result: Sign-in, dashboard and record access, document access, and record creation all complete without permission errors.

  • Migration and SharePoint provisioning health — Requires: System Administrator.

    • Setup and action: In Admin Health, allow the migration and SharePoint provisioning health checks to finish and review their results. If a failed provisioning record is available, retry it and wait for the retry to finish.
    • Expected result: The health checks finish without unresolved failures. Any retried provisioning record recovers successfully and no longer reports an unresolved failure.
Authentication and notification settings

  • Supported record notification settings — Requires: a regular record user.

    • Setup and action: open a record's notification settings and look for Notify of recommendation and Notify of decision. Change a supported notification setting, save it, and reload the record.
    • Expected result: The two unsupported controls are absent. The supported setting saves and retains its new value after reload.
Workflow, activity, and key dates

  • Immediate progression after record initiation.

    • Setup and action: Initiate a representative record and progress it immediately, before SharePoint provisioning finishes. Open the record's Activity view after the transition completes.
    • Expected result: No stage-update error appears, the record advances exactly once, and the transition appears in Activity.

  • AllMustDecide activity attribution — Requires: System Administrator for test setup.

    • Setup and action: Configure or select an AllMustDecide step assigned to Users B and C. As User A, progress the preceding step into it, then complete representative decisions as the current-step assignees and review Activity.
    • Expected result: User A is not shown as having decided. Users B and C, and the actions they actually complete, appear correctly for the current step.

  • Unsaved key date changes during automatic refresh.

    • Setup and action: Edit a key date and its reason, but do not save. Leave both changes pending for longer than the configured automatic record-refresh interval, then save them.
    • Expected result: The automatic refresh does not discard either value, and both changes save successfully.

  • Workflow transition dialog at reduced screen space.

    • Setup and action: Open a workflow transition at 125% browser zoom and again in a narrow viewport. Review the full dialog and use its controls.
    • Expected result: The dialog resizes or scrolls to fit the available space, and Send and Cancel remain visible and usable.
Documents, duplicate handling, and group access

  • Original correspondence upload with existing correspondence.

    • Setup and action: On a record that already has another correspondence file, add or replace the original correspondence. Wait for the upload to finish, verify the file in SharePoint, and refresh the record.
    • Expected result: The upload completes without error, the file reaches SharePoint, and it remains present after refresh.

  • Document access through Brief Connect User Group membership — Requires: System Administrator for test setup.

    • Setup and action: Add a non-administrator to a Brief Connect User Group and assign that group to a role with document-view permission. Sign in as the group member and open the record and one of its documents.
    • Expected result: The group member can open both the record and its documents with the access granted by the role.

  • Duplicate file move during record initiation.

    • Setup and action: During record initiation, select one file and try to move it into a section that already contains a file with the same name. Review the selection and selected-file count after the move is rejected.
    • Expected result: The move is blocked, only the chosen file remains selected, and the selected-file count is accurate.

  • Individual and bulk duplicate-file moves on an existing record.

    • Setup and action: Open Manage Documents on an existing record. Test an individual move and a bulk move where the destination contains a duplicate filename. Dismiss the error, take a corrective action, or close and reopen Manage Documents.
    • Expected result: When a filename clashes, none of the selected files move and the error appears in the destination section. The error clears after dismissal, a corrective action, or reopening Manage Documents.
Applicable plugins

  • User Group assignment from a background field update — Requires: an enabled plugin that assigns roles through UpdateRecordFieldsBackground and System Administrator for test setup.

    • Setup and action: Use the plugin to assign a Brief Connect User Group to a record role. Open People and Roles, then sign in as a group owner or member and perform an action allowed by the assigned role.
    • Expected result: The group's owners and members remain attached to the assignment, appear in People and Roles, and receive the expected record access and actions.

  • ActionOverdue configuration and daily notifications — Requires: the enabled ActionOverdue plugin and System Administrator.

    • Setup and action: In Admin Panel → Plugins → Edit Data, edit actionoverdue:config, save it, and reopen it to confirm persistence. Prepare an eligible overdue task and, where supported by the saved configuration, a closed-record task and a task assigned to a muted user. Review the results after the next daily run.
    • Expected result: The configuration persists. The eligible overdue task produces one reminder in that daily run without duplicates, while configured closed records and muted users produce none.

Rollback

If the deployment fails validation or introduces critical issues, redeploy the previous stable package version from the Deploy Brief Connect Application release pipeline.

  1. Go to Azure DevOps and open your Brief Connect project.
  2. Go to Pipelines -> Releases.
  3. Open the latest successful release that used the previous stable package version.
  4. Redeploy that release to the affected environment.
  5. Confirm core smoke tests pass.