From Bright Pattern Documentation

Revision as of 17:43, 11 September 2026 by Wyler.metge (talk | contribs) (BPCC Version 5.36.2 Release Notes)

< Previous | Next >
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

BPCC Version 5.36.2 Release Notes

Suggested Actions

If you have a Zendesk integration account, switch it to the new Client Credentials authentication type before Zendesk retires the type your account uses now.

Added/Updated Features

Zendesk Client Credentials Authentication

Zendesk integration accounts now support OAuth 2.0 Client Credentials authentication. Existing accounts are unaffected. The previous authentication types remain available and are now labeled obsolete.

Zendesk began deactivating unused API tokens on July 28, 2026, stops allowing new API tokens to be created on October 27, 2026, and will permanently deactivate all remaining API tokens on April 30, 2027. Zendesk has also announced that it will begin expiring OAuth access tokens.

We recommend switching your Zendesk integration accounts to Client Credentials authentication ahead of those dates rather than waiting for an account to stop working.

Expanded Security Options for Salesforce Integrations

Salesforce allows PKCE, refresh token expiration, and refresh token rotation, which are now automatically handled by the Bright Pattern Salesforce integration.

New integration accounts require an External Client App to connect with, as the legacy Connected Apps can no longer be created. When you set up a new Salesforce integration account, note the two new properties:

  • App Type: External Client App
  • My Domain: your org's My Domain URL

Existing accounts are unaffected. Salesforce still supports connected apps that already exist, so there is no need to migrate them. If a Salesforce account can no longer refresh its token, an identifying alert is shown in the admin portal when you log in.

AI Provider Accounts

Added Support for the Gemini 3.1 Model Family

Added support for the Gemini 3.1 model family through multi-region endpoints (us and eu), as these models are not available through standalone regional endpoints.

The multi-region endpoint can be selected using the Region property of AI provider accounts.

Connection Testing for AI Provider Accounts

When saving an AI provider integration account, you are now warned if Test Connection has not been run since your most recent changes, or if the most recent test failed. Saving is still allowed.

Hosting Partner-Specific Items

AI Accounts

As with AI provider accounts, the AI accounts used in your AI packages now support Gemini 3.1 Flash-Lite, us and eu multi-region endpoints in the Region property, and the save-time Test Connection warnings.

< Previous | Next >