23.2.0 - Fredhopper Discovery Platform Release Notes – Rezolve Ai Support Portal

Introduction

These release notes provide an overview of the resolved issues and improvements of the most recent release of the Fredhopper Discovery Platform 23.2 line.

Fredhopper Discovery Platform 23.2 is a major release. The Query and Data APIs in this version are backwards compatible with all versions from Fredhopper Discovery Platform 7.5.x to 23.1.y. The Configuration API is backwards compatible with all Fredhopper Discovery Platform versions until 23.1.y.

Fredhopper Discovery Platform 23.2 supports Oracle Java 8 VMs. For detailed setup instructions, please refer to Install Java instructions.

Version: 23.2.0

Release Date: May 18, 2023

Improvements & Resolved Issues

Merchandising Studio & Preview Pages

[Fixed] Merchandising Studio now does not alter the entities’ initial "create date”.

[Fixed] When a “datetime” attribute was used for sorting, this could result in an error. The problem has been fixed: sorting by the “datetime” attribute works as intended.

[Fixed] In Preview Pages, spaces in translated URLs made the URLs invalid. Spaces in translated URLs are now removed.

[Fixed] The "Today" button in the “datetime” trigger showed performance issues. The problem has been fixed.

[Fixed] Values within a facet could be interpreted incorrectly when triggering the "more" or "less" button. The problem has been fixed.
[Fixed] Saving changes on the "System defaults" page in Merchandising Studio could block incremental product data feeds, which prevented Fredhopper from updating. The problem has been fixed.

Visual Merchandising Interface

[Fixed] In certain cases, the Visual Merchandising screen could have sorting issues. The problem has been fixed. The correct sorting is applied now consistently.

[Fixed] In the Visual Merchandising item pop-up, values for ranking cocktails' attributes could be wrong. The problem has been fixed.

Search and Navigation

[Fixed] In certain situations, location triggers using a search location were processed incorrectly by search analyzers. The problem has been fixed.