Upgrade from v5 to v6

This is for:

Developer System Administrator

The Coveo for Salesforce v6.1 release introduces changes in the Coveo for Salesforce AppExchange package.

This article addresses the most common concerns about upgrading from Coveo for Salesforce v5 to v6.

What are the breaking changes associated with the Coveo for Salesforce v6 package?

  • Use of organization endpoints for all hosted experiences

    The main change in the Coveo for Salesforce v6 package is the enforced usage of organization endpoints for all the hosted experiences. This means that all hosted components will use organization endpoints by default. This change applies regardless of whether the setting was enabled on the Advanced Configuration page. Although non-hosted components such as Coveo Lightning components will continue to respect your initial endpoint setting, we recommend that you enable organization endpoints at your earliest convenience.

  • Removal of the Relevance Generative Answering (RGA) rephrase buttons

    With the update to v6, the QuanticGeneratedAnswer component no longer offers buttons to rephrase the format of a generated answer because the rich text formatting option offers a better experience and a more consistent answer quality. After the package update, these buttons no longer appear on a generated answer and can’t be re-added.

  • Update to RGA citation click tracking

    Coveo Relevance Generative Answering (RGA) citation clicks are now tracked as regular click events instead of custom click events in Coveo Usage Analytics (Coveo UA) reports. This change ensures that citation clicks are included in the Average Click Rank and Search Events Clickthrough metrics. Deployments that have enabled RGA for their Coveo Hosted Insight Panel or Coveo Hosted Search Page components will see this change reflected in their Coveo UA reports.

Why is Coveo enforcing the use of organization endpoints?

To improve separation of concerns, resiliency, and to make multi-region and data residency deployments smoother. With these new endpoints, you no longer need to keep track of the location of your primary deployment region. These endpoints are region-agnostic and will automatically route requests to the region offering the lowest latency.

Which Coveo components are affected by the organization endpoint update?

What can I expect as an impact on my implementation of Coveo for Salesforce if I’m using a Coveo hosted component?

You’ll see the network calls (for example, analytics and search calls) of your hosted components target the organization endpoints. Since the required Content Security Policy (CSP) Trusted Site Settings are included in the v6 package, this means you shouldn’t have any manual operation to perform unless you modify the packaged CSP settings. In such case, you’ll need to ensure your organization’s CSP Trusted Site Settings aren’t blocking the organization endpoints.

What will happen if I keep using Coveo for Salesforce v5?

In short, you’ll miss out on the latest updates, features, and potential bug fixes. However, v5 isn’t being deprecated. Although new features will only be available on v6 going forward, Coveo will continue to support v5 until further notice.

Can I roll back to v5 once I upgrade to v6?

It’s difficult to roll back a Coveo for Salesforce package after upgrading. We strongly recommend that you read the documentation, verify if the changes will affect your implementation (for example, by testing it in a sandbox first), and plan accordingly before upgrading your package.

What if I don’t want to upgrade to v6?

You may continue to use v5. Coveo will continue to support v5 until further notice. Depending on the situation, if you encounter an issue, we may decide that upgrading to v6 is the best course of action to continue support. See Product lifecycle for more information.