Skip to content

Brief Connect v2.6.2 Release Notes

Release date - 19th August, 2026

Package version: 2.6.2

This patch release corrects Initiator role permissions. It also improves support for Brief Connect plugins that interact with the user interface.

Improvements

  • Improve support for plugins that use the user interface

    Brief Connect plugins that interact with the user interface (UI) now have more reliable access to application information.

    This change improves how these plugins integrate with record views.

Bug fixes

  • Restore Initiator role access and permissions

    Brief Connect now keeps the main Initiator value and its configured role-field alias synchronised.

    New records and later Initiator changes now apply the configured role permissions.

    During deployment, InitiatorRoleAliasMigration repairs affected existing records. The migration starts a permission refresh for each repaired record.

    Users in the Initiator role can then open these records and find them through My Records and search.

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.2, select Create Release.
  5. Set the Package Version variable to 2.6.2.
  6. If the release needs a description, add one.
  7. Select Create.
  8. Refresh the page.
  9. Make sure that v2.6.2 (n) appears in the release list.

Pipeline deployment steps

  1. Deploy the latest v2.6.2 (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.2

Initiator role migration

  • Repair an affected existing record — Requires: System Administrator.

    1. Before deployment, identify an affected record that has an Initiator without the configured role permissions.
    2. Record the Initiator and the current access results.
    3. After deployment, open App Health.
    4. Make sure that InitiatorRoleAliasMigration finishes without an unresolved error.
    5. Sign in as the Initiator.
    6. Open the record from its direct link.
    7. Find the record in My Records and search.

    Expected result: The migration repairs the record. The Initiator can open and find the record.

  • Apply Initiator permissions to new and updated records — Requires: two non-administrators and a System Administrator.

    1. As the first non-administrator, create a representative record.
    2. Keep the first user in the Initiator role.
    3. Finish record initiation.
    4. Make sure that the first user can open and find the record.
    5. As the System Administrator, assign the second non-administrator to the Initiator role.
    6. Sign in as the second user.
    7. Open the record and find it in My Records and search.

    Expected result: The current Initiator receives the configured role permissions after record initiation and role reassignment.

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.