This page provides information on the **Bloomreach Content (SaaS) releases**. Watch this space to stay updated about our fortnightly, planned releases containing critical bug fixes, feature enhancements, and new feature releases. We also share **new documentation updates** to bring exciting and helpful pages to your attention.
Releases are deployed to customer environments 2 weeks after the date encoded in the release version. This will occur between 10:00-14:00 CET on a Tuesday for customers hosted in the US or APAC. (This is usually 4-8am EST or 18:00-22:00 AET, except during daylight saving time transitions.) For customers in the EU, this will happen on the same Tuesday between 18:00-22:00 CET.
Bloomreach recommends always using the [latest version of the SPA SDK](🔗) for frontend applications integrating with Content SaaS. For more details see [SPA SDKs - Lifecycle and Support](🔗).
## 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.
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.
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
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.
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.
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.
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.
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
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.
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
Handling of empty or null values in the [Content APIs](🔗) has been improved.
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.
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.
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.
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.
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
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.
[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
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](🔗).
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.
[Release Notes Archive 2022](🔗)
[Release Notes Archive 2021](🔗)