Bloomreach Content V17.2 Release Notes

Highlights for v17.2

Bloomreach Content v17.2 introduces new features, technical stack upgrades, and product improvements. This page summarizes the key changes in this release. For a complete list of release notes, see the release notes overview.

All features and changes described here are part of Bloomreach Content unless stated otherwise.

Significant Updates and New Features

In-Product Feedback

A new "Feedback" button is available in the CMS navigation bar. CMS users can now submit feedback or report issues directly to the Bloomreach Content product team from within the CMS, without opening a support ticket. Submitted feedback is only sent when the user clicks Submit, and users can review the content before submitting.

By default, feedback is sent to a Bloomreach-managed endpoint. You can disable this feature in the CMS console or configure it to send feedback to a custom endpoint if your organization prefers to handle feedback internally.

Note: Submitting feedback through this widget does not create a support ticket and does not generate a direct response. For issues requiring a reply or blocking your work, contact Bloomreach Support through your standard channel.

For more information, see the In-Product Feedback documentation.

Content Vulnerability Dashboard

The CMS Vulnerability Dashboard provides administrators with a real-time, self-service overview of known vulnerabilities relevant to their Bloomreach Content version and configuration. This eliminates the need to wait for support tickets or scheduled reports.

This dashboard is available independently of the CMS version in use.

Access: The dashboard is available to Premium Support customers. If you have Premium Support, contact Bloomreach Support to request access. To upgrade to Premium Support, contact your account manager.

For details, see the Content Vulnerability Dashboard documentation.

Ongoing Enhancements and Fixes

For End Users

Experience Manager

• The authoring environment now isolates plugin failures. If a single plugin fails, the rest of the page remains functional.
• Drag and drop for reordering items in ordered lists in the channel editor now works as expected.
• Entering a channel from the Projects perspective now switches to the correct branch.
• Locks, edits, and activity across document lists, revision history, Experience Manager, and Projects now display the user's name instead of the username.
• Opening a channel now accurately reflects the current project state.
• Locked channels now prevent moving items in the navigation menu, consistent with other lock restrictions.
• The component property editor opens automatically after dropping a component into an SPA channel.
• The focus outline now displays correctly on all fields.
• External links now open in the same browser tab instead of a new one.
• Labels on multiple/optional fields now display correctly.
• When overriding a menu item's name in Advanced settings, the toggle remains enabled after saving to indicate a custom name is in use.

Content Editor

• Files with less common extensions (e.g., .kml, .log) now upload consistently when allowed by project configuration.
• The take offline date now appears in a document's revision history.
• When taking a document offline from the Version History dialog, you can now record a reason for the action.
• Asset and image listings and pickers now display the last modified time in addition to the date.
• Document types are now sorted by their translated label rather than their internal name.

For Developers

AI Content Assistant

• Spring AI has been upgraded to 2.0.0. The Vertex AI Gemini integration now uses Google's updated Spring AI module, and several configuration properties have changed. Review the AI Module Upgrade Guide before upgrading.

Platform & Stability

• Plugin rendering exceptions are now contained using a new ResilientMarkupSourcingStrategy, preventing a single plugin failure from affecting the entire authoring page.
• Spring Boot has been upgraded to 4.1.0.
• Fixed a regression that prevented custom plugin-based value list providers from resolving.
• The deprecated OpenTelemetry deployment.environment attribute has been replaced with its supported alternative.
• Fixed URL encoding validation when creating HST pages.
• The hst:authenticated property can now be overridden at the sitemap item level.
• Error catching has been improved to reduce unrelated SEVERE-level log messages.

Targeting & Content Audiences

• The Targeting and Content Audiences frontend has been migrated from AngularJS 1.8.3/ExtJS to Angular, completing the migration.

Security Fixes

• This release addresses known vulnerabilities. Upgrade to the latest patch version for the most recent security updates. Premium Support customers can use the Vulnerability Dashboard to assess applicability.

Bloomreach SPA SDK Updates

Bloomreach SPA SDK 28.1.0

• New getImage() and getDocuments() helpers allow direct access to images and referenced documents.
• Fixed an issue where specifying a default port in the endpoint URL could break the connection.
• Channel Manager previews for content-heavy pages now load more smoothly, improving the editing experience. Requires Bloomreach Content 17.2.0 or later.

For more information, see the SPA SDK v28.1.0 release notes.

Bloomreach Cloud Updates

Native OpenTelemetry Tracing

Bloomreach Cloud customers can now export distributed traces from their CMS environment to any OTLP-compatible observability backend (such as Dynatrace, Grafana Cloud, or Honeycomb). This extends the existing OpenTelemetry pipeline that already supports log data.

This feature is available for customers running brXM 16.0 and later.

Setup: To enable trace export, contact the Bloomreach Cloud team via a support ticket.

For configuration details, see OpenTelemetry Tracing on Bloomreach Cloud.

Ecosystem & Add-on Updates from Professional Services Team

Bloomreach Forge Plugins Upgraded for Bloomreach Content 17

Several Bloomreach Forge community plugins, including the IP Filter Plugin and Servlet Filter Decorators, have been upgraded for Bloomreach Content 17 (Java 21 and Spring Boot 4).

For the current status and released versions, see the Forge project list. Additional plugins are being upgraded progressively.

Upgrade Assistance from Bloomreach Content Experts

The Bloomreach Professional Services team offers upgrade support for Bloomreach Content projects. The team has extensive experience with project implementations and can assist with upgrading to the latest Bloomreach Content versions.

An Upgrade Assessment service is available. In three days, the team will evaluate your systems and infrastructure to determine upgrade requirements. The assessment includes:

• Executive summary
• Overview of major changes
• Recommended upgrade procedure
• Comprehensive list of findings

The evaluation fee is fully refundable if you proceed with Professional Services for the upgrade.

To request upgrade assistance, contact your account manager.

Notices

AI Content Assistant Module Spring 2.0 Upgrade

The following configuration changes result from the upgrade to Spring AI 2.0.0 and affect projects using the AI Content Assistant. Review these items before upgrading.

PromptLoggerAdvisor log level
The log level for PromptLoggerAdvisor has changed from INFO to DEBUG. Update your logging configuration if you want to continue capturing these logs.

Usage Audit Logging
The UsageLoggingStore logger now uses DEBUG instead of INFO. Adjust your logging configuration if necessary.

Vertex provider renamed
The Vertex AI provider has been renamed from VertexAIGemini to GoogleGenAiVertex. Update any configurations referencing the old name.

Removal of completions-path and embeddings-path
The OpenAI provider no longer supports the completions-path and embeddings-path configuration properties. Remove these properties if present.

OpenAI API URL default changed
The default OpenAI API endpoint (spring.ai.openai.api.url) is now https://api.openai.com. If you set this property explicitly, verify it points to the intended endpoint.

Minor Release

v17.2 is a minor release and remains backward compatible with the previous minor version. Upgrading from v17.1 to v17.2 requires minimal effort. See the upgrade instructions (login required) and the overview of minor version upgrade instructions for more information.

Supported Technologies

For full system requirements and a detailed table of third-party compatibility, see the system requirements documentation.

End-of-Life, Support, and Maintained Code

Nomenclature

The following definitions clarify how Bloomreach uses the terms "end-of-life," "supported," and "maintained":

Supported Product Version

A supported product version is eligible for helpdesk support as described in your service level agreement (SLA). Multiple service levels are available.

If a bug is identified in a supported but not maintained version, fixes are only applied to maintained versions. To receive a fix, you must upgrade to a maintained version.

Maintained Product Version

Maintained versions receive code updates, security patches, and bug fixes. System requirements for third-party libraries and components are kept current. Bloomreach supports the use of certified system requirement providers but does not provide support for the providers themselves (e.g., databases, Java).

Non-maintained versions do not receive code updates and may contain unresolved bugs or security vulnerabilities.

End-of-Life Product Version

End-of-life versions are neither supported nor maintained. They may be available in archives but can be removed without notice.

Support Status Table

The table below lists the planned end-of-support dates for each product version. Versions not listed are not active, not supported, and considered end-of-life.

Version	Planned end date of Standard Support	Planned end date of Premium Plus Support	Original major version release date
Latest 14.x	December 2024	December 2025	December 2019
Latest 15.x	December 2025	December 2026	April 2022
Latest 16.x	December 2026	December 2027	June 2024
Latest 17.x	December 2027	December 2028	May 2026

Table: Planned end-of-support dates based on current SLA terms. Supported versions may vary depending on contractual agreements.

Versions highlighted in orange are actively maintained and receive bug fixes and product improvements.

Security Notes

This release updates third-party dependencies with published vulnerabilities. Keep your systems current by applying product releases as they become available.

Availability

Bloomreach Content v17.2 is available as of August 13, 2026. The open source release will follow approximately two years later, in accordance with the Bloomreach release policy.