Release Notes Archive 2023

This page contains archived information on Bloomreach Content (SaaS) releases in 2024.

For the latest release notes see Release Notes.

20231116 - The Content Management API Now Supports Document and Page Locales

This Content release improves support for localization and translation operations at API level.

🚧

Please note that this release won't be deployed to customer environments due to the active holiday freeze. The next release to be deployed after the freeze is expected to be 20240110 and will contain all changes introduced after the 20231102 release.

🎉 New Features

• The locale of a document or page can now be set and retrieved using the Content Management API's document and page endpoints.

🚀 Improvements

• The 'locale' property of a channel is now considered read-only by the Site Management API in order to preserve consistency with content associated with the channel. Bloomreach intends to make similar changes in upcoming releases to improve consistency for use cases related to localization and content reuse.

🐛Bug fixes

• Documents can no longer incorrectly be in published state temporarily in certain scenarios.
• Linking a translated folder to the root folder of another channel in the Content app, which caused an invalid state and locked up the UI, is no longer possible.
• The title of the Synchronize translated pages dialog in the Experience manager no longer incorrectly shows an ellipsis (...).
• The Delivery API 2.0 (Beta) now generates correct OpenAPI specifications for content types using content blocks.

20231102 - Easier and Better Page Synchronization and the Delivery API 2.0 Beta Nears Completion

Synchronize and publish pages with one button click, include page-specific component content in page synchronization, and test many new features and improvements in the Delivery API 2.0 Open Beta!

🎉 New Features

• Page-specific components now have an Update content on page sync checkbox to indicate their content should be updated when synchronizing pages between translated channels:

   

  

   

• You can now synchronize and publish pages with a single button click in the Synchronize translated pages dialog in the Experience manager:

   

  

   

• The page synchronization feature is now out of beta.

🚀 Improvements

• We made many improvements to the Delivery API 2.0 Beta response format and we expect it to be stable until the release.
• We now provide an OpenAPI specification for the Delivery API 2.0 Beta and will be publishing the interactive API reference in the next few week.
• An OpenAPI specification for your content types is now automatically generated at runtime.

🚧

Please note the Delivery API 2.0 is still in beta test phase and should not be used in production scenarios.

We will be publishing guides and reference documentation in the next few weeks. In the meantime, refer to the Postman collection for an overview of endpoints and usage examples.

🐛Bug fixes

• Linking documents as translations using the Content Management API now works as expected when the source document has a draft version.
• When synchronizing a page containing links to content that is translated in the target channel, the links in the target pages will now be properly updated to point to the translated content.
• Requests to the Content Type Management API no longer fail unexpectedly in case a merged development project is present.
• In the Channel settings dialog in the Experience manager, the field labels for the channel properties now show the properties' configured display names as expected.

20231018 - API Improvements

🚀 Improvements

• The Management APIs now allow GET operations in project contexts if the project is in any of the following states: unapproved, in review, approved, merge conflict, update conflict, running.Previously these were only allowed if the project was in the unapproved state.
• The Delivery API 2.0 (Beta) now allows searching for field names which have the same name as internal fields.
• The pattern "{{ s }}" (where 's' is any string) in user-provided values is now replaced with "<?> s <?>" in API responses.
• Some internal properties are no longer exposed by the Delivery API 1.0 and 2.0 (Beta).

20231004 - Search for Pages by URL and Monitor Locked Content Types.

🚀 Improvements

• In the Sitemap in the Experience manager you can now search on any of the path elements in a page's URL or its full or truncated URL path starting with a slash. For example, a /categories/bolts page can be found by searching for "bolts", "categories", "/categories/bolts", and "/categories/b".

   

  

   

• Locked content types are now displayed on the Home dashboard along with locked documents.

   

  

   

• Several improvements were made to the Delivery API 2.0 Beta.

• The new UI theme has been applied to the Site development and Integrations apps.

🐛Bug fixes

• The Delivery API no longer becomes unresponsive in some scenarios.
• The Javascript error "In this configuration Angular requires Zone.js" no longer occurs in the Content web application in some scenarios.
• The external preview of a channel no longer erroneously displays an earlier version of a page that is currently live in a campaign.
• External preview tokens no longer expire unexpectedly.
• UI glitches related to the new UI theme have been fixed.

20230920 - Link Content Items as Translations by API and Beta Test the New Delivery API 2.0!

🎉 New Features

• Link Content Items as Translations by API
  It is now possible to link and unlink documents, pages, and folders as translations using the Content Management API! This enables batch processing the linking of existing content items in channels that are part of the same translation group. The API can also get existing translations and provide a list of suggestions (which documents should be linked as translations) based on paths.

  

• Beta Test the New Delivery API 2.0
  The new Delivery API 2.0 is now available for beta testing! It is designed to be easy for developers to work with directly and implement use cases such as, for example, retrieving individual content items from the repository or retrieving all content items in a folder. The original Delivery API was not well suited for such use cases as it was primarily designed to be consumed by our front-end SDKs. As such both Delivery API versions complement each other.
  

  🚧

  Beta

  Please note that the Delivery API 2.0 is in beta testing stage and as such should not be considered stable and should not be used in production scenarios.

🚀 Improvements

• The UI theme has been updated to be more consistent with other Bloomreach apps.

🐛Bug fixes

• Switching between projects in the Experience manager's channel preview no longer results in an error in the sitemap in certain scenarios.

Release 20230906

🎉 New Features

• A new Images endpoint has been added to the Delivery API. It lists all images that are direct descendants (with pagination) under the specified folder path.

Release 20230823

🐛Bug fixes

• The Content Type Management API no longer erroneously returns 400 Bad request in case of content type definitions containing a selection field with an empty sortBy property.
• The New channel dialog no longer erroneously saves a locale different from the one displayed as selected in certain user interaction scenarios.

New SPA SDK Documentation Portal

The SPA SDK has a new documentation portal hosted at its github repository. The portal includes a combination of all the content found in the READMEs in the repository, a migration guide, and links to the release notes and changelog, to be expanded on in the future.

You can find the SPA SDK documentation portal at https://bloomreach.github.io/spa-sdk/docs/.

Release 20230809

🎉 New Features

• You can now navigate to a particular page in the list of translated pages in the Experience manager.

🚀 Improvements

• The Site development app now displays the state of each development project in the list and no longer lists merged projects.
• When synchronizing a translated page, you can now only select target channels that are part of the selected target project.
• We made improvements under the hood to make adding a new channel based on an existing one more robust.

🐛Bug fixes

• The name of the selected project in the For project selector in the Experience manager no longer disappears after cancelling adding a new translated page.
• When adding a new channel based on an existing one and selecting a source channel that was only just added to a translation group, that translation group is now corrected pre-selected.
• Inline <style> elements are no longer incorrectly removed from rich text fields.

Release 20230726

🎉 New Features

• It is now possible to add a new channel by copying an existing one, significantly speeding up the process to localize channels for new markets.

🚀 Improvements

• We made several UX improvements to the page synchronization feature.

🐛Bug fixes

• We updated third-party libraries to their latest versions following our standard security procedures.

Release 20230712

🚀 Improvements

• You can now view a page's translated pages, add new translated pages, and initiate synchronization in the right side panel in the Experience manager.
• We updated third-party dependencies in the Spartacus storefront integration.

🐛Bug fixes

• We fixed a critical issue introduced in the previous release causing high CPU load in certain scenarios.
• Copying a page from the Core channel to a project-version of a channel no longer results in an error message.

Release 20230628

🚀 Improvements

• Improved feedback messages when synchronizing pages between translated channels.

🐛Bug fixes

• When translating a document, the translated document's locale is no longer set in an incorrect format.
• Creating a translation of an Experience page document when the parent folder does not have a linked translated folder yet no longer fails if the user does not have the admin role.

Release 20230614

🚀 Improvements

• The Synchronize translated pages dialog in the Experience manager now shows for each target channel when the page was last synchronized (if applicable).

🐛Bug fixes

• The Content Batch Import API now correctly imports Experience pages that don't have any static components.
• The Sitemap now reflects any changes made in the Content app when switching from the Content app to the Experience manager.
• Folders with an underscore in their name no longer cause broken locale icons.
• Creating a translation of an Experience page document when the parent folder does not have a linked translated folder yet no longer fails if the user does not have the admin role.

Release 20230531

🚧

Due to a blocker issue, this release won't be deployed to customer environments. All changes below will be available as of the next release.

🎉 New Features

• The UI Extension Javascript Client Library has three new methods that make it easier for developers to read and write any field values within their document field extensions. This enables integrations with services that can enhance or generate content such as our new ChatGPT Text Generator. The new methods are available in the @bloomreach/ui-extension-saas library as of version 0.3.1.
  Currently, the new methods are only supported in the editor in the Experience manager app.

🚀 Improvements

• System performance and resilience of the delivery tier have been improved.

Release 20230517

🎉 New Features

• It is now possible to synchronize pages between channels in the same translation group. The Configure Channels for Page Synchronization developer documentation page explains at site configuration level how page synchronization works and what the requirements and best practices are for the feature to be enabled and working as expected.

🚀 Improvements

• The New channel dialog in the Experience manager is now scrollable and no longer hides part of the new channel form.
• It is now possible to configure an iframe allow attribute for Custom integrations to optionally enable access to microphone, camera, and/or clipboard.
• A Custom integration configured with dialog size "large" now results in the iframe being opened with the maximum size as expected.

🐛Bug fixes

• Loading an experience page stored inside a folder named "resources" no longer results in an error page.
• The content-type header in Delivery API responses is no longer incorrectly missing the charset.
• The Bynder integration no longer unexpectedly requires an explicit login when selecting assets in the content editor.

Release 20230503

🚀 Improvements

• It is now possible to expose up to 30 segmentations in Engagement (previously this was limited to 5). This requires version 3.0.0 of the Engagement SDK snippet and version 14 of the @bloomreach/segmentation library.
• The Reference SPA now supports segment-based personalization using Engagement out-of-the-box.

🐛Bug fixes

• The Sitemap in the Experience manager no longer initially shows as empty on opening it in certain scenarios.
• Updating segmentations now properly invalidates relevant entries in the delivery tier cache.
• The Bynder integration no longer shows the error message "Oops! Something went wrong" in certain scenarios. The relevant documentation has been updated. When creating an OAuth app to connect Bynder to Content, make sure to check the meta.assetbank:read property when defining the app's scope.

Release 20230419

🎉 New Features

• The Bynder integration now supports audio and document asset types.

🚀 Improvements

• Long page URL names are now truncated in the Experience manager's Sitemap and no longer overlap.
• Continuing improvements in error messages for the Content and Batch Import APIs.

🐛Bug fixes

• When searching for pages marked as favorites in the Experience manager's Sitemap, the homepage is now included in the results as expected if it is marked as favorite.
• The Sitemap in the Experience manager no longer fails to load in certain scenarios in which the user switches from one channel to another.
• Fixed a Content API issue with pages that use components with drop-down parameters that are configured to populate/read their values from a resource bundle document.

SPA SDK 20.0.0 - Vue 3 support

This release of the SPA SDK adds Vue 3 support. Vue 2 SDK support will end when Vue 2 reaches EOL (December 31th, 2023). This allows customers some time to upgrade their web apps.

Please refer to the full SPA SDK 20.0.0 release notes on Github for more info.

Release 20230405

🎉 New Features

• The Content Type Management API now supports renaming and deleting of content types.

🚀 Improvements

• Custom integrations now supports downloads from the iframe the integration is running in.
• The Site Management API now supports the dot character ('.') in names of routes and layouts. For example: "sitemap.xml".

Release 20230322

🚀 Improvements

• Warning messages in the Content APIs have been improved to be more specific and better distinguish warnings and errors.
• The Content APIs now reject PUT requests with redundant, conflicting values for the same property.
• The Content Management API's Page endpoint now rejects PUT requests if a component on the page has a contentType specified in its component definition, but the payload is missing the "fields" object for content data.
• The Content APIs' PUT operations now accept the "null" value for field type Boolean with displayType=RadioGroup. The "null" value is treated as "false".
• The Content APIs' PUT operations now treat taxonomy fields with an empty string in an array ([""]) value the same as the "null" value, i.e. the value is omitted.

🐛Bug fixes

• Removing a channel from a project as a user in the Site Developer role no longer results in an error message.
• Deleting a page-specific component from a page no longer fails if it contains an empty FieldGroup.
• Fixed an issue where the content type editor could store an incorrect configuration for a boolean radio group field, which could make documents of that content type inaccessible in the GUI.
• The translations menu for documents is now correctly limited to allow linked translations only in channels within the same translation group as the current document.

Documentation Update March 15th, 2023

We added the following new guides for developers:

• Milestone 5: Create a Complex Component Data Model and Milestone 6: Create a Shared Document-Driven Component have been added to the Get Started with Bloomreach Content guide.
• Copy Content explains how to use the APIs to copy content between different development projects and/or different environments.

Release 20230308

🚀 Improvements

• Handling of empty or null values in the Content APIs has been improved.

🐛Bug fixes

• The Preview button to open a channel's external preview no longer results in a 404 Not Found page for routes using wildcard matchers.
• Modifying a channel group no longer results in translation links between folders being removed in certain scenarios.

Release 20230222

🎉 New Features

• Users can now mark or unmark pages as favorites in the Sitemap in the Experience manager app.

🚀 Improvements

• When adding a new channel in the Experience manager, it is now possible to add the new channel to an existing translation group in the New channel dialog.
• It is now possible to delete a page template without disabling it first.
• GET requests to the Content Management API now succeed, even if a content editor is currently editing the requested document or page.
• Significant progress has been made in phasing out outdated AngularJS code in order to increase security and improve performance of the Experience manager UI.

🐛Bug fixes

• Removing a channel from a project when the user has Site Developer privileges no longer fails.
• The UI nog longer locks up when specifying an invalid icon string in the New channel dialog in the Experience manager.
• Inconsistencies between the Sitemap and the channel preview in the Experience manager app have been fixed.

Release 20230208

🎉 New Features

• Our new External Customer Data Platform integration enables content personalization using segmentations managed in any CDP. Read the documentation to learn how to configure the integration, how to import the segmentation from your CDP, and how to implement personalization in your SPA.
• A Locked Documents listing has been added to the Home app.
• The Page Template feature is now out of beta.

🚀 Improvements

• When adding a new channel in the Experience manager, it is now possible to create a new translation group and add the new channel to it in the New channel dialog.
• The Content Batch Import API's error messages have been improved.

🐛Bug fixes

• The Experience manager's Channels overview no longer shows a blank page and returns a 403 response when deleting a channel that's part of a translation group.
• When merging a project with conflicts, the conflicts are no longer invisible and blocking the merge in certain scenarios.
• When creating a page in a project using the Content Management API's Page endpoint, containers no longer go missing in some scenarios.

SPA SDK 19.0.0 - Angular 15 support

This release of the SPA SDK brings Angular 15 to the Angular SDK. Both the Angular SDK and the example app have been updated to use Angular 15. There are no changes to any of the previous API’s related to the Angular SDK.

Please refer to the full SPA SDK 19.0.0 release notes on Github for more info.

Release 20230125

🚀 Improvements

• Default response headers provided by Bloomreach for the Delivery APIs are now preserved when additional headers are added by customers in their channel configuration.
• The performance of preview requests in the Experience manager has been improved by fine-tuning CORS settings for allowed HTTP headers.
• The handling of null, empty string, and missing properties in the Content Management API and Content Batch Import API has been improved.
• Unlocking a document or page now results in behavior that is consistent between the Experience manager and Content apps.

🐛Bug fixes

• Copying a page from one channel to another no longer fails in certain scenarios.
• Navigating between different apps in the UI no longer results in random 404 errors.

Release 20230111

🚀 Improvements

• The Content Type Management API now supports specifying a namespace prefix in content type names.
• The Commerce category picker is now able to display all available category facet values, regardless of the configured Max number of facet values in any facet, on any page.

🐛Bug fixes

• Static Dropdown fields no longer disappear from the editor in certain document editing scenarios.
• The View menu in the Content app no longer produces an error in scenarios where a document exists only in a project but the document's channel is not part of that project.
• Switching between certain apps no longer results in a 404 error in certain scenarios.
• The For project selection in the Experience manager's channel preview no longer resets from a selected project to Core when switching to the Content app, then back to the Experience manager.
• Clicking on a page in a project now opens that page in the Experience manager's channel preview instead of incorrectly opening the Channels overview.

Archives

• Release Notes Archive 2022
• Release Notes Archive 2021