Release Notes
This page describes the most important new features.
Changes within the BPC version are documented at Changelog.
Explanation of Versioning
Versions with different version numbers are released regularly for the BPC. A version number consists of three parts: major.minor.patch.
A change in the major version number(e.g., 4.0) indicates that the release includes significant changes to the software.
For example, APIs may have been changed or removed, major changes may have been made to the user interface, or major features may have been removed or added.
A change in the minor version number(e.g., 4.3) may include new features, changes to existing features, or the removal of features.
In addition, changes may occur for supported platforms (e.g., databases, operating systems, Git versions).
A change in the patch version number(e.g., 4.3.1) may include bug fixes, stability improvements, and performance enhancements.
Minor changes to existing features may be included, but these do not include new features or critical changes.
Breaking changes are generally intended to address potential security vulnerabilities and may therefore occur in any release.
However, the goal is still to include these changes in major releases.
Breaking changes are highlighted in the Changelog.
4.1
For updates from earlier versions, please refer to Migration from BPC 4.0 to BPC 4.1.
Personalization
Version 4.1 laid the groundwork for customizing BPC to individual needs.
You can now create personal monitor views that are not visible to other users.
Future 4.1 releases will offer additional personalization options.
Sharing
You can now share the current view of the BPC *. You’ll receive a link containing all the necessary information, which you can paste into emails or chats, for example.
* Prerequisite: The modules must support the corresponding interfaces, and the necessary permissions to view the shared page functions must be in place.
Migration from Elasticsearch to OpenSearch
The internal data storage has been migrated from Elasticsearch to OpenSearch.
Due to recent changes in the Elasticsearch license, we are no longer able to use this software in current BPC versions in a legally compliant manner. Therefore, we have migrated our internal data storage to OpenSearch. OpenSearch is licensed under the Apache 2.0 license. This allows us to monitor the development process and respond immediately to known security vulnerabilities.
