Skip to content

Brief Connect v2.6.3 Release Notes

Release date - 7th September, 2026

Package version: 2.6.3

This patch release improves document upload and rename reliability, expands support for plugins that customise record actions, and corrects plugin field matching and Initiator role migration retries.

Improvements

  • Expand plugin support for record actions

    Brief Connect plugins can now add options to the I Want To menu, filter available workflow actions, validate an action before submission, and request a refreshed record view after an action completes.

    Plugins can also determine whether the current user is a Record Administrator. These capabilities allow tenant-specific plugins to provide more contextual actions and workflow validation.

  • Match plugin rules against standard record fields

    Prefilled Roles and Prefilled Key Dates plugin rules can now match Organisation, Stage, Topic Summary, Closed Date, Correspondence Received Date, and Correspondence Written Date fields.

    Organisation-level labels in Prefilled Roles configuration now follow the configured field labels correctly.

Bug fixes

  • Resolve documents in libraries that retain a legacy SharePoint path

    Brief Connect now resolves a SharePoint document library by its internal URL name when the library's visible title has changed. This can affect pre-v2.6 records whose library title was updated to the current TYPE-0001 naming convention while the original date-based name remains in the URL.

    New copy and supersede operations can now materialise the selected source documents from these libraries. For an existing destination record whose document copy previously failed for this reason, a System Administrator can expand SharePoint recovery options and select Retry document copy now after the destination's SharePoint location is available.

    A manual retry copies missing eligible documents into the existing destination record. It does not repeat or reverse the copy or supersede operation, and it does not modify the source record. Eligible stale failures may also be retried by the existing background health process, but automatic recovery is not immediate or guaranteed for every failed record.

  • Preserve files selected from SharePoint

    Resolved an issue where some documents uploaded through SharePoint would show as empty documents, or not open correctly.

    Related support tickets:

  • Signed documents no longer stall at 99% uploaded

    Previously, the UI would show the upload as stalled, even when it had uploaded successfully - users would need to manually refresh the page to see the latest information. This is now resolved.

    Related support tickets:

Upgrade instructions from v2.6.x

These instructions apply to environments that use Brief Connect v2.6.x.

Manual pre-deployment steps

Review release pipeline variables

Apply changes to pipeline variables before you create a release. Each release stores the current variable values at creation.

If you change a variable later, create a new release.

  1. In Azure DevOps, open your Brief Connect project.
  2. Go to Pipelines -> Library -> Variable groups.
  3. Review the variables for each target environment.
  4. Update the values where required.
  5. Save the changes.

Create a new release

  1. In Azure DevOps, open your Brief Connect project.
  2. Go to Pipelines -> Releases.
  3. Open the Deploy Brief Connect Application release pipeline.
  4. If no release uses version 2.6.3, select Create Release.
  5. Set the Package Version variable to 2.6.3.
  6. If the release needs a description, add one.
  7. Select Create.
  8. Refresh the page.
  9. Make sure that v2.6.3 (n) appears in the release list.

Pipeline deployment steps

  1. Deploy the latest v2.6.3 (n) release to the target environment from the Deploy Brief Connect Application release pipeline.

Manual post-deployment steps

No manual changes are required.

Smoke tests

After deployment, follow our Basic testing of Brief Connect guide.

Release-specific tests for v2.6.3

Documents selected from SharePoint

  • Upload a record document from SharePoint - Requires: a non-empty test document in SharePoint and permission to edit record documents.

    1. Open a test record and select Manage Documents.
    2. In a document section, select Select files from SharePoint.
    3. Select the non-empty test document and finish the upload.
    4. Open or download the resulting record document.
    5. Compare it with the source document.

    Expected result: The destination document has the requested filename and contains the same content as the SharePoint source. It is not blank or corrupted.

Signed and renamed documents

  • Upload a signed document - Requires: permission to sign or replace a record document.

    1. Upload a signed replacement for a Primary document.
    2. Wait for the upload and document-details refresh to finish.
    3. Make sure that Done becomes available.
    4. Open the signed document.

    Expected result: The upload does not remain at 99%. The signed document replaces the correct original document, appears in the correct section, and opens successfully without a page refresh.

  • Rename and immediately open a document - Requires: permission to edit record documents.

    1. Rename a document in Manage Documents.
    2. Wait for the document-details refresh to finish.
    3. Open or download the renamed document without refreshing the page.

    Expected result: The renamed document opens successfully from its updated link.

Copying pre-v2.6 records

  • Start a new copy or supersede operation from a legacy library path - Requires: a pre-v2.6 record with at least one document, a migrated library display title such as TYPE-0001, and an unchanged date-based library URL.

    1. Open the pre-v2.6 source record.
    2. Confirm that its library display title follows the current naming convention while its URL retains the legacy date-based name.
    3. Copy the record and include its documents.
    4. Wait for SharePoint provisioning and document copying to finish.
    5. Open each copied document.
    6. Repeat with Supersede on another suitable test record.

    Expected result: The copied and superseding records finish provisioning with the selected documents. Each document opens successfully, and no unresolved document-copy health error remains. The source record's library title and URL remain unchanged.

  • Retry an existing failed document copy - Requires: System Administrator and an existing copied or superseding destination record whose document-copy status is Failed because its source uses a legacy library path. The destination SharePoint location must be available.

    1. Record the source and destination record IDs and the source record's current title and status.
    2. Open the failed destination record.
    3. Expand SharePoint recovery options.
    4. Select Retry document copy now.
    5. Wait for the retry and record refresh to finish.
    6. Open the documents in the destination record.
    7. Reopen the source record and compare its title and status with the values recorded before the retry.

    Expected result: Missing eligible documents are copied into the existing destination without duplicating documents that were already copied. Document-copy health changes from Failed to Succeeded. The destination record ID does not change, and the retry does not modify or reprocess the source record. For a supersede operation, the source remains superseded.

Rollback

If deployment validation fails, redeploy the previous stable package version.

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