Bloomreach Experience Manager V14.7.0 Release Notes - Bloomreach Experience Manager - The Fast and Flexible Headless CMS

Bloomreach Experience Manager V14.7.0 Release Notes

RELEASE NOTES

Bloomreach Experience Manager v14.7

Bloomreach Experience Manager Developer Edition v14.7

Highlights for v14.7

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. 

Key New Features

More Robust Image and Asset Validation for Various File Extensions

To make the image and asset uploader more robust, a new validation logic has been introduced. The CMS image and asset uploaders now validate the browser-provided mimeType against the mimeType found through inspecting the actual uploaded content: By looking for special (so called "magic") patterns of bytes near the start of the file, it is often possible to detect the type of the file. By leveraging one of our technology providers, brXM now checks whether the extension of a file matches the actual content detected and whether it should be allowed to be uploaded. This takes into account whether a CMS user uploads a file with a renamed file extension and takes into account sub or super mimeTypes. 

Also, it is now possible to configure the extensions to be allowed for the validator as described in documentation, which has been validated to work with more than 200 different extensions and file types via the content detection mechanism.

Extended Visual Editing Support

The visual editor can be used to edit content from within the Experience manager. Ongoing improvements strengthen the capabilities of the visual editor even further. With the release of v14.7 it is now possible to add, edit, and remove optional fields; improvements have been made to choice fields; drag and drop behaviour for compound fields is more reliable; and there are several other additions.

Separate Release Lifecycle for SPA SDKs

To make developing a front-end for Bloomreach Experience Manager easier, we introduced the SPA SDKs. In the field of front-end development, changes happen incredibly quickly. To keep our SPA SDKs relevant to our customers, we’ve decided to separate the release lifecycle of the SPA SDKs from the brXM releases. This allows us to update the SPA SDKs more frequently, without having to wait for a brXM release, which occurs less frequently.

Customers who are on brXM v14.6 or lower should stick with their respective SPA SDK version. Starting with v14.7 we recommend customers to use the latest version found on Github up until the next brXM minor or major release. Upgrade steps for the SPA SDKs can be found within the readme and upgrade notes in the changelog.md file. 

BigCommerce Connector

With the release of the Bloomreach GraphQL Service v14.7.0 we are welcoming BigCommerce to our list of OOTB commerce backend connectors. This new connector will enable front-end developers to create magical commerce experiences faster with BigCommerce and Bloomreach while keeping great performance.

The BigCommerce connector, as with other existing connectors, supports basic commerce functionalities such as authentication, user registration, login/logout, category and product search and variants, cart management, checkout, order management etc. You can check our GraphQL Service documentation for a complete list of items. 

It’s also good to remind that the GraphQL Service includes a connector for Bloomreach Discovery. This makes powering search and product grids with the Bloomreach Discovery module even easier. This also makes adding a product to cart and/or getting more product details directly from the commerce backend easier than ever with a single endpoint to be used.

The new BigCommerce connector will also enhance the Bloomreach Experience Manager’s Category and Product pickers. This allows business users to add components with product data to their pages, by selecting categories and products directly from their BigCommerce catalog.

GraphQL Service Improvements for Commercetools

With the Bloomreach GraphQL Service v14.7.0 we have also made several improvements in our commercetools connector such as:

  • Localised category and product search including product titles and descriptions

  • Improved performance by enabling the retrieval of product information for multiple products in one request

  • Search for categories and products by their human-readable slugs

  • Create user friendly URLs by retrieving categories and products slugs (SEO friendly)

  • Search for categories and products associated with a specific store

  • Get stock levels, product prices, and shipping costs per store

  • Create and manage wishlists

Ongoing Improvements

For end users

  • For customers using the Navapp to have a single menu structure for Bloomreach Discovery and brXM, performance has greatly improved through a new loading method of the various applications.

  • For customers using bulk workflow in advanced search it was impossible to click the menu for adding a tag to documents. This requires customers to update their custom workflow extensions.

  • With the acquisition of Exponea in the beginning of 2021, Bloomreach created a refreshed brand identity that better reflects the heritage of Bloomreach, while modernizing the strong brand. In v14.7 this brand is reflected throughout the UI.

  • Error handling has been improved to prevent confusing situations where the user was not sure what action to take

  • Improved rendering of icons and labels in the audience perspective

  • Several fixes were introduced to improve the handling of an experience page when it is part of a project or campaign

For developers

  • Fixed an issue where the Page Model API did not stop serializing references documents if it is an asset or imageset

  • Fixed an issue where cookie consent was not processed properly for targeting

  • Several fixes were made for enterprise forms, including an issue where the semi-colon in cc would break processing of the data.

  • Fixed an issue regarding link creation in case of advanced sitemap configuration

  • Fixed an issue using the configuration verifier where it would not execute the command properly 

  • Fixed an issue with a dynamic component dropdown not working properly for drop down properties

Notices

Client implementations with custom bulk workflow extensions should update their custom bulk workflow implementation as part of the upgrade to v14.7. See the upgrade documentation for details.

Minor release

v14.7 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 are 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:

(Orange cells indicate changes compared to the previous release)

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

Not maintained

14.7

latest

16.0 GA

17.0 GA

Yes, until 14.8 or 15.0 GA

Security notes

This release includes updates for 3rd party dependencies that have published vulnerabilities. It also includes fixes for medium-severity issues identified in the product itself. These issues will be disclosed to customers separately, and publicly in 6 weeks. We recommend that customers keep their systems up to date with announced product releases.

Availability

This version of brXM is available as of Nov 18, 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.6-to-14.7.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?