Fredhopper Discovery Platform 26.1.0 Upgrade Notes

Fredhopper Discovery Platform 26.1.0 is compatible with the previous release FAS 25.3.0.

Change Rank in Scope for Multiple Entities

Starting with FAS 25.3.0, the existing REST endpoint for changing rank in scope has been extended to support multiple entity IDs.

Endpoint

POST entities/ab-tests/priority

This endpoint changes the priority of one or more entities and accepts the following body parameters:

• id: Specifies the ID of the entity. This parameter can now be provided multiple times to update several entities in a single request.

• priority: An integer value greater than or equal to 1 that specifies the new priority for the entity or entities.

Example

curl -X POST \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -i http://localhost:9180/fredhopper/config/entities/campaigns/priority \
  --data '&id=entityId1&id=entityId2&priority=4'

Integrate Merchant AI Chatbot in Merchandising Studio

Starting with FAS 26.1.0, Merchandising Studio supports integration with the Dify application, enabling the Merchant Agent AI Chatbot for customers.

This integration is controlled by a feature switch.

Configuration in system.xml

A new configuration section is available under:

/com/fredhopper/bm/difyConfigChatbot

The following options can be configured:

• enabled: Enables or disables the Merchant AI Chatbot (Dify application) integration.
  Values: true or false
  Default: false

• difyConfigFile: The name of the Dify application configuration JSON file containing initialization parameters.
  This file must be located in the FAS config directory.
  Default: difyConfig.json

• src: The location of the Dify application embedding script.
  This parameter is mandatory when the integration is enabled.

Example system.xml Configuration

<node name="difyConfigChatbot">
  <map>
    <!-- Is the feature enabled -->
    <entry key="enabled" value="true"/>
    <!-- Specifies the json config file, should be located under `/config` directory -->
    <entry key="difyConfigFile" value="difyConfig.json"/>
    <!-- Dify source -->
    <entry key="src" value="https://dify-dev.eu-west-1.fdp-qa.fredhopper.com/embed.min.js"/>
  </map>
</node>

Dify Configuration File

For the integration to work, a JSON configuration file must be provided in the FAS config directory.
The file name is configured in system.xml (see above) and defaults to difyConfig.json.

Example difyConfig.json

{
  "token": "I3jAcbzq46VsnDt3",
  "baseUrl": "https://dify-dev.eu-west-1.fdp-qa.fredhopper.com",
  "systemVariables": {},
  "userVariables": {},
  "containerProps": {
    "className": "dify-chatbot-custom"
  }
}

For more information about Dify initialization parameters, see the Dify documentation:
https://docs.dify.ai/en/guides/application-publishing/embedding-in-websites