Coveo for Sitecore 5 is now available!

Release Notes for December 2017 - 4.1.184.18

The initial December 2017 release was 4.1.184.18. However, due to an issue with the Legacy UI, it had to be hotfixed to 4.1.184.19.

The official December 2017 release is 4.1.184.19 (see Release Notes for December 2017 - Minor Release 4.1.184.19).

To ensure compatibility with some external Dynamic Placeholder modules, this release includes a breaking change.

When upgrading from a previous version of Coveo for Sitecore, you need to follow the steps here: Solving the Conflict Between Keys from Dynamic Placeholder Modules and Coveo Dynamic Placeholders

This release includes the v1.2537.35 and v2.3477.9 versions of the JavaScript Search Framework (see July 2017 Maintenance Release (v1.2537.35) and November 2017 Release (v2.3477.9))

This page summarizes the new features and fixed support cases introduced in the Coveo for Sitecore December 2017 release (4.1.184.18).

To download the December 2017 release, see Downloads.

For the upgrade procedure, see Upgrading from October 2017 (4.1.125.11) to December 2017(4.1.184.2).

Issue number New features
SC-1981 Validated item parameters sort order, help links, and display name.
SC-2042 [Global Search Box] Added OmniboxResultList component.
SC-1242 Removed Query Duration from the example page.
SC-2182 HTMLContentInBodyWithRequestProcessor is now customizable.
SC-2254 Coveo for Sitecore is now FIPS compliant.
SC-2371 [Coveo for Sitecore Hive] Pipeline and MaximumAge now added as options for the searchbox.
SC-2379 DistanceComponent from coveo-search-ui now replaces custom ones.
SC-2413 Date and Time were added to the Diagnostic Package file name.
SC-2421 SSO pre-authenticator was implemented for FetchPageContent.
Issue number Bug fixes
SC-359

[UI] Removed Renderings and Sublayouts items related to the Coveo Sort.

SC-1134 [Search Box] Fixed broken component preview for secured target search page.
SC-1544 Fixed issue where encryption key was written to the wrong data folder.
SC-1583 [Security Provider] Fixed issue where first rebuild did not end due to errors in security identities.
SC-1670 Validated API key to prevent multiple denied calls to the platform.
SC-1782 Renamed Cloud admin UI to Cloud administration console.
SC-1877 [Security Provider] Fixed issue where push of permissions were duplicated.
SC-1986 Updated help links for component properties.
SC-1991 [UA] Fixed issue where link was unavailable in visit browser for Coveo for Sitecore result clicks.
SC-2057 Fixed issue where console logging could not be disabled.
SC-2081 Fixed issue where  user-friendly error message for UI components did not work .
SC-2111 Hid sections in the Edit Properties dialog according to license.
SC-2131 Added missing searchHub querystring attribute to query suggest requests in the Experience Editor.
SC-2159 Fixed issue where ResolveItemSiteProcessor did not take site language into account.
SC-2167 Fixed issue where URI had to be logged when its format could be determined.
SC-2251 Updated deprecated JavaScript Search Framework property in default result template.
SC-2271 Added automatic boosting to placeholder settings for result header.
SC-2292 Fixed issue where views using the same model output the same ID.
SC-2305 [Security Provider] Fixed issue where roles containing a non-existing user were still sent to the expanded provider.
SC-2311 Fixed issue where profiles with multiples profile cards were not indexed completely.
SC-2318 [Security Provider] Improved diagnostic page error message about the security provider not existing.
SC-2319 Fixed issue where message Item already exists was displayed when installing a package on a new instance.
SC-2320 Updated link redirecting to Create your first search page.
SC-2323 Fixed issue where supposedly disabled search indexes still appeared in the Sitecore configuration.
SC-2324 Fixed issue where legacy sort components did not recognize certain fields.
SC-2325 Fixed issue where QueryFilter was ignored in a Coveo for Sitecore Hive search page.
SC-2326 Fixed issue where clicking on result title was impossible on a Coveo for Sitecore Hive result page.
SC-2348 Applied prebinding to registered external components.
SC-2364 Folder icons were removed from Coveo Hive package.
SC-2367 Fixed issue where a Serializable attribute was missing on component EditDataSourceAction.
SC-2369 Fixed link Indexing Documents with HTML Content Processor in the installation wizard.
SC-2374 Added error message for Update User or Role actions in the UI.
SC-2380 Added missing fieldTranslator prebind attribute to Facet Computed Field in Coveo for Sitecore Hive.
SC-2388 Fixed issue where Filter Expression Rules had disappeared in the 4.1 Legacy UI.
SC-2408 Fixed issue where xDB profiles with different names for their items and keys were not mapped in documents.
SC-2412 [Legacy] Fixed broken Boosting Action Remove X from score.
SC-2417 Fixed issue where generating a diagnostic package interrupted Sitecore activities.
SC-2422 Fixed issue where prebind attribute in default result template was invalid.
SC-2427 Added missing external fields to Coveo.SearchProvider.config for Sitecore 8.1.
SC-2429 Fixed issue where mappings were overridden when updating Sitecore source.
SC-2430 Fixed issue where deleted items still showed up in diagnostic page.
SC-2433 [Hive] Fixed issue where Sort Direction Settings inherited from Standard Rendering Parameters.
SC-2459 Resolved conflict between dynamic placeholder module and Coveo Hive dynamic placeholder.
SC-2461 Resolved conflict between dynamic placeholders for renderings without Model.Id.
SC-2479 [Coveo for Sitecore Hive] Fixed issue where Maximum Age was not using the index configuration in the Experience Editor.
SC-2486 Fixed issue where the rebuild process tried to get security provider entities even when the IndexPermissions setting was disabled.
Issue number Case Fixed support cases
SC-2284 00038311 Analytics stopped coming through after upgrading Coveo for Sitecore 4.0 from April 2016 to January 2017 and upgrading Sitecore instance from 8.0 to 8.2.
SC-2509 00040218 [Legacy UI] Fixed issue where boosting rules were not applied to the right part of the query.