Bloomreach Experience Manager V14.6.0 Release Notes - Bloomreach Experience - Headless Digital Experience Platform

Bloomreach Experience Manager V14.6.0 Release Notes

RELEASE NOTES

Bloomreach Experience Manager v14.6

Bloomreach Experience Manager Developer Edition v14.6

Highlights for v14.6

We are pleased to announce a new version of Bloomreach Experience Manager (brXM). This minor release introduces new functionality and a number of useful improvements to the product. In this document we will give a brief overview of the highlights in this release. You can also find these release notes at: https://documentation.bloomreach.com/about/release-notes/release-notes-overview.html 

Please note that as a result of our security release policy the public availability of the community source code and artifacts for all active releases will follow in about six weeks. Customers however, have immediate access to these new releases at the release date.

Everything mentioned in this document is an integral part of Bloomreach Experience Manager (brXM) and the developer edition, unless mentioned otherwise. If a feature only applies to brXM and not to the developer edition, this is explicitly mentioned. Features that are mentioned as part of brXM also apply to brX.

Key New Features

Page campaigns 

Since the release of Experience pages in v14.3 we’ve been getting frequent responses from users how they love the easier way of working with pages. The versioning and scheduling of pages enables new ways to get the campaigns live at just the right times. With Page campaigns, we’re enhancing this by making it possible to prepare several page versions to go live in advance. This allows several page campaigns to be scheduled before the first publication date, allowing content marketers to prepare multiple changes that go live on just the right moment in time.

  • The new Page campaigns feature enables site editors to schedule an alternative version of a page to be served on the live website from a specified start date and optionally until a specified end date.

  • A page without a specified end date will stay live until a new campaign for that page starts or until an end date is added.

  • It is now possible to rename page versions.

  • It is now easier to set-up campaigns in advance as you can prepare multiple go-live dates on pages before the first scheduled publication date.

Notes:

  • The Page campaigns feature needs to be activated through a feature flag. Please check our documentation site to see how to enable this (link).

  • The list of versions is limited to showing 100 versions to ensure consistent performance

Ongoing Improvements

For end users

  • Multiple UI improvements for UI consistency across the platform, while making buttons, icons and menus more readable across various features.

  • Opening a menu item by right-clicking on ‘open in tab’ now works as expected.

  • Several new icons for distinguishing experience pages and their respective folders in the content perspective.

For developers

  • If an experience page document can’t be loaded in the Page Model API, a 404 is now returned instead of a 500 error.

  • Upgraded CK Editor to v4.16 for improved rich text field handling, for added functionality see https://ckeditor.com/cke4/release/CKEditor-4.16.0 

  • Since v14.6, Spring Boot framework has been integrated into CMS applications which adds support for a number of additional features to help in monitoring and managing CMS applications when it is pushed to production. Auditing, health, and metrics gathering can also be automatically applied to the application.

Notices

There are no notices for this release.

Minor release

v14.6 is a minor release so it is backwards compatible with the previous minor release. Also, updating to this version from the previous minor version should be of little effort. Specific upgrade instructions for this release can be found in our documentation [1] for enterprise customers (requires a login). An overview of all upgrade instructions for minor versions in this major release can be found in our documentation [2] as well.

Supported Technologies

The full system requirements can be found in the online system requirements [3]. This page also includes a detailed table of maintained third party compatibility.

End-of-life, support and maintained code

Nomenclature refresher

As the terms ‘end-of-life’, ‘supported’, ‘maintained’ are used in various ways in our industry, we clarify the nomenclature we use for this below.

Supported product version

When a product is supported, this means that the customer will receive help from the helpdesk when issues arise as described in the service level agreement (SLA) that the customer has with Bloomreach. There are several service levels available. 

Please note that if a bug is acknowledged in a supported, but not-maintained version, and a fix is needed, this fix will only be applied in the maintained product versions. This means the customer will need to move to a maintained version to receive the fix. 

Maintained product version

When a product is maintained, the product code is updated and security- and bug fixes are made to the code. For maintained products, the system requirements for third party libraries and components is kept updated as well. Please note that we do not provide support for system requirement providers (e.g. databases, java, etc..), but we only support the usage for mentioned certified system requirement providers. 

If a product is non-maintained, this means that the code is not maintained anymore and therefore might contain bugs and/or security vulnerabilities due to newly discovered issues in our code, or the libraries used.

End-of-life product version

Products that are not maintained and not supported are end-of-life. These might be available from our archives but could be removed without notice.

What does this mean for the current release?

Please note that this release does not change any maintenance or support mode.

In the table below you can find the support status of your product and when support will end; this is dependent on  the version currently being used and license level. Please note that versions that are not listed are not active and not supported, and therefore end-of-life.

 

If you are on version:

You will receive support until the release of version:

 

Version

Standard license

Premium license

Maintained

12.1

latest

No Support

15.0 GA

Not maintained

12.2

latest

No Support

15.0 GA

Not maintained

12.3

latest

No Support

15.0 GA

Not maintained

12.4

latest

No Support

15.0 GA

Not maintained

12.5

latest

No Support

15.0 GA

Not maintained

12.6 (LTS)

latest

No Support

15.0 GA

Yes, until 15.0 GA

13.0

latest

15.0 GA

16.0 GA

Not maintained

13.1

latest

15.0 GA

16.0 GA

Not maintained

13.2

latest

15.0 GA

16.0 GA

Not maintained

13.3

latest

15.0 GA

16.0 GA

Not maintained

13.4 (LTS)

latest

15.0 GA

16.0 GA

Yes, until 16.0 GA

14.0

latest

16.0 GA

17.0 GA

Not maintained

14.1

latest

16.0 GA

17.0 GA

Not maintained

14.2

latest

16.0 GA

17.0 GA

Not maintained

14.3

latest

16.0 GA

17.0 GA

Not maintained

14.4

latest

16.0 GA

17.0 GA

Not maintained

14.5

latest

16.0 GA

17.0 GA

Not maintained

14.6

latest

16.0 GA

17.0 GA

Yes, until 14.7 GA

(Orange cells indicate changes compared to the previous release)

Security notes

There are no specific security notes for this release.

Availability

This version of brXM is available as of May 26, 2021 onwards. Please note that this release contains security fixes, and due to our release policy the release of the open source CMS / developer release will follow in approximately six weeks after this date.

Links

[1] https://documentation.bloomreach.com/14/library/upgrade-minor-versions/upgrade-14.5-to-14.6.html

[2] https://documentation.bloomreach.com/14/about/upgrade/introduction.html

[3] https://documentation.bloomreach.com/library/about/system-requirements.html 

 

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?