Upgrade 17.1 to 17.2

Overview

This guide describes how to upgrade a Bloomreach Content implementation from version 17.1.x to 17.2.y.

Significant Changes

Version 17.2 introduces updates to the technical stack for the AI Content Assistant and consolidates MIME type handling for uploads. Key changes for developers upgrading from 17.1 to 17.2 include:

Spring AI upgraded to 2.0.0:
The Vertex AI Gemini chat model integration now uses the Spring AI Google GenAI module. The previous module was removed upstream. Several AI-related configuration properties have been renamed or removed. See the Upgrade Steps section for details.
Targeting and Content Audiences UI updated:
The Targeting module front end now uses Angular instead of AngularJS/ExtJS.
In-product feedback widget:
A "Feedback" button has been added to the CMS navigation bar. Users can submit issues and suggestions directly to the Bloomreach Content product team. This feature is enabled by default and can be disabled in the CMS console. For details, see the in-product feedback documentation. Submissions do not create support tickets or receive direct replies. For urgent issues, contact Bloomreach Support.
Legacy value list providers resolved:
Custom value list providers that extend Wicket's Plugin and are registered under /hippo:configuration/hippo:frontend/cms/cms-services are now resolved in the legacy document editor, restoring pre-17.1 behavior. These providers remain unavailable in Experience Manager. For migration guidance, see Custom Value List Providers.

For a complete list of changes, see the 17.2.0 release notes.

Upgrade Steps

1. Perform Generic Minor Upgrade Steps

Follow the generic instructions for minor upgrades before proceeding with version-specific changes.

2. Update AI Service Module for Spring AI 2.0

If your project uses the AI Content Assistant and configures it via properties or Essentials, review and update the following:

PromptLoggerAdvisor log level:
The log level for the prompt logger has changed from INFO to DEBUG. Update your logging configuration if necessary.
Usage Audit Logging:
The log level for the UsageLoggingStore logger is now DEBUG instead of INFO. Adjust your logging configuration as needed.
Vertex provider renamed:
The provider name has changed from VertexAIGemini to GoogleGenAiVertex. Update your AI configuration if you use the Google provider.
Removal of completions-path and embeddings-path:
The OpenAI provider no longer supports the completions-path and embeddings-path configuration properties. These options are no longer available.
OpenAI API URL change:
The default value for the spring.ai.openai.api.url property changed from https://api.openai.com/v1 to https://api.openai.com.

3. Review Custom Targeting (Relevance) UI Plugins

The Targeting module's front end has migrated to Angular. Review the UI components of any custom collector or characteristic plugins for compatibility. For upgrade instructions, see:

Both pages include an "Upgrade Path towards 17.2" section.

4. Review Custom Project Code for Library Incompatibilities

Third-party library upgrades in this release may introduce backward compatibility issues. If your project code fails to build or run, review the affected libraries and update your code to use the latest versions.

5. Review Detailed Release Notes

For additional information, see the detailed release notes.