April 15, 2020 release (5.0.655.1)

This is for:

Developer System Administrator
Important

Per the Coveo Version Support Lifecycle policy, this Coveo for Sitecore 5 release has been retired. See available Coveo for Sitecore releases.

Even if this release is retired, you must still perform some of its upgrade steps to upgrade to a more recent version of Coveo for Sitecore.

This release includes the 2.7968.10 version of the JavaScript Search Framework (see January 2020 Release (v2.7968)).

When using a CDN with the Coveo Hive framework, this release includes the latest 2.7968 version of the JavaScript Search Framework (see Understanding How the Coveo JavaScript Files are Loaded (CDN)).

Release Notes

This section summarizes the new features and fixed support cases introduced in the Coveo for Sitecore April 15, 2020 release (5.0.655.1).

Identifier Enhancement
SC-4252 Added rendering to support the Coveo JavaScript Search Framework QuerySuggestPreview component.
SC-4261 Added data source options to support recently introduced Coveo JavaScript Search Framework Searchbox, ResultList, and CategoryFacet component options.
SC-4319 Added support for SXA 9.3.
Identifier Case Fixed Support Case
SC-4350 00059817 Changed the AnalyticsEvent class CustomMetadatas property type to an IDictionary<string, object>. This is a breaking change (see Upgrade Steps).
SC-4361 00059860 Renamed the Coveo Conditional Renderings personalization rule condition.

Upgrade Steps

Important

Per the Coveo Version Support Lifecycle policy, this Coveo for Sitecore 5 release has been retired. See available Coveo for Sitecore releases.

Even if this release is retired, you must still perform some of its upgrade steps to upgrade to a more recent version of Coveo for Sitecore.

This section describes how to upgrade Coveo for Sitecore from April 1, 2020 (5.0.642.2) to April 15, 2020 (5.0.655.1). If you're upgrading over multiple versions, Coveo has a procedure to streamline the process.

Warning
WARNING

In the Coveo.Analytics assembly, the AnalyticsEvent class CustomMetadatas property has changed type from IDictionary<string, string> to IDictionary<string, object> in order to support other types than Strings. This should have been the implementation from the start since these metadata can be objects of any type.

To ease this breaking change, we added a TryGetValue extension method to IDictionary<string, object> which allows to pass in an already typed out value. If used, this extension will simply require you add the Coveo.Framework.Collections namespace in your using statements.
Important

For the best Coveo for Sitecore experience, always follow the upgrading leading practices.

Step 1: Upgrade Coveo for Sitecore

Important

Make sure the Microsoft MVC security update MS14-059 is installed on every Sitecore host in your environment.
  1. Log into the Sitecore Desktop.
  2. Access the Installation Wizard (Sitecore Start Menu > Development Tools > Installation Wizard).
  3. Upload and install the Coveo for Sitecore XX 5.0.655.1 package.
  4. When prompted to overwrite files, click Yes to all.

  5. When prompted to overwrite items, select Overwrite, then click Apply to all.

    Note

    You might be prompted twice with this question. Select the Overwrite option and click Apply to all both times.

  6. Once the installation is completed, make sure that you restart both the Sitecore client and server.

Step 2: (Optional) Configure New Data Source Options on Existing Renderings

In this release, Coveo for Sitecore fronts recently added Coveo JavaScript Search Framework component options in its data sources. Though none of the renderings default behavior have changed, you may want to leverage some of these new data source options in your existing renderings.

Here are the rendering data source options that have been added:

Coveo Searchbox rendering:

Coveo Category Facet rendering:

Coveo Results List rendering:

Step 3: Publish your site

In the Sitecore Content Editor, perform a publish site action. This ensures any changes related to Coveo components in the upgrade are published to the web database.

〈  Previous version upgrade steps Next version upgrade steps  〉