Changelog

The module is now displayed as a frontend module again. This ensures consistent display.

A bug in the opensearch-env.bat has been fixed.

The configuration of OIDC and Keycloak backend Connections failed when the BPC homepage was specified as the redirect URL (post-login or post-logout). The cause was the settingvalidation, which returns an HTTP status code 406 when checking the URL of the BPC homepage. As a result, it was not possible to create new OIDC or Keycloak backend Connections or edit existing ones. New cloud deployments that create backend Connections via Custom Resource were also affected.

This issue has been resolved.

New window for resolving conflicts when resizing cells in the table layout, where decisions can be made regarding the removal, moving, and resizing widgets.

The state of the action buttons on replication jobs has been corrected. In some cases, changes to replication jobs did not affect the availability of the functions.

The cache configuration was accessing Services that no longer exist, which was causing errors. These accesses have been removed.

In some cases, the navigation display would not update correctly when modules were accessed.

The menu for Monitor Views no longer displays an empty placeholder when no view is selected.

Under certain circumstances, an error Failed to process event could occur when starting Karaf.

The UI texts in WebTSM have been revised to ensure consistent multilingual support throughout.

Under certain circumstances, the Backup Manager might fail to start when Karaf is launched due to an error.

The display of text in the interface has been revised so that text is fully visible.

If, when loading the BPC Web GUI, the browser accessed the the browser would load the index page, which could lead to problems verifying the login. This could only occur with OIDC-based identity providers.

A possible cause could be, for example, a faulty theme.

The configuration org.apache.karaf.shell.cfg in Karaf has been revised.

Host Key & Signatures: Switch to RSA 4096 and modern SHA-2 algorithms (rsa-sha2-512/256); deactivation of insecure NIST curves (ECDSA).

Protocol hardening: Restriction to secure key exchange schemes (Curve25519), AES-GCM encryption, and Encrypt-then-MAC (EtM).

Important —If Karaf is not fully updated, but only the configuration file is applied, then the file etc/host.key must be deleted.

An issue has been resolved where large amounts of data were not fully transferred in HttpProxy.

After a BPC update to version 5.0.4 or 5.0.5, the error " HTTP ERROR 500 javax.servlet.ServletException: javax servlet.ServletException: java lang.NoSuchMethodError: 'java lang.String de.virtimo.bpc.api.service.CoreBundleService.getUserFlowIdentityProviderLoginRedirectUrl(javax.servlet.http.HttpServletRequest)' " might occur when accessing the BPC interface. This error has now been fixed.

The error occurred when a part of the interface (index.jsp) was not directly updated by the update and an OIDC/Karaf Identity Provider was being used.

If an update to this version is not possible, the error can be resolved by deleting the directory <BPC-INSTALL-DIR>/karaf/data/pax-web/ and restarting Apache Karaf.

"Share Process" is working again

Radio groups caused the application to crash on startup if a hard-coded value was used instead of data binding. This issue has been resolved.

XML data is processed correctly despite the error message. The request is not aborted.

The error message has been updated so that it now only appears when the return format is neither JSON nor XML.

The developer documentation has been restructured: core:/dev/tutorials/index.adoc

The monitor’s caching mechanism (state in local storage) in conjunction with the monitor settings has been described in detail.

Correction to the Replication documentation regarding the Replication_AdjustUpperDateLimitInSeconds setting, which is not limited to specific database management systems.

The documentation on monitor views has been updated. See Manage Process Views

This update upgrades the version of Apache Karaf.

Please update Karaf according to the update instructions.

Incorrect behavior in the monitor regarding the data_filter setting has been fixed: If you used the link OR and had not set a base filter, all records were displayed despite the filter rules.

With a AND link, the base filter was negated and combined with the other filter rules using a logical UND. This was incorrect; the base filter is now not negated here either, and specifies which documents are generally visible. This means that a data record is visible if it meets the base filter OR any of the session-specific filter rules.

Note: If you are using Monitor instances with ` data_filter ` in your BPC deployment, please verify that they continue to function as intended.

More details on the ` data_filter` setting can be found here: Restrict Visibility of Monitor Data

A JSON schema has been provided for the function_gridMultipleViewsConfig monitor setting. This provides guidance during configuration and helps prevent incorrect configurations.

The database connection was not closed correctly during Tailsync. This causes all connections in the connection pool to become blocked over time.

Column headers and, in some cases, content were unintentionally centered. The background of the filters on checkbox columns was sometimes not displayed correctly.

Incorrect behavior in the monitor regarding the data_filter setting has been fixed: If you used OR as a link and did not set a base filter, all records were displayed despite the filter rules.

In the case of a AND link, the base filter was negated and combined with the other filter rules using a logical " UND " operator. This was incorrect; the base filter is now no longer negated in this case either, and specifies which documents are generally visible. This means that a data record is visible if it satisfies the base filter OR any of the session-specific filter rules.

Note: If you are using Monitor instances with ` data_filter ` in your BPC deployment, please verify that they continue to function as intended.

More details on the ` data_filter` setting can be found here: Restrict Visibility of Monitor Data

The use of Flow for Forms has been described in detail. See Integrating IGUASU with BPC

The documentation on multiple grid settings (function_gridMultipleViewsConfig) has been updated. See Configuring Multiple Grids/Views

See OpenSearch

Example for dynamic filter value with #user.loginName# added. See Restrict Visibility of Monitor Data

Data used by OIDC providers for login is stored in an encrypted cookie on the client’s device. This prevents system overload caused by a large number of login requests.

For BPC module developers

If you have developed your own UserFlowIdentityProvider implementation, you must adapt it. The function ` URI createAuthenticationRequestURI(String requestUrl) ` has been replaced with ` UserFlowLoginContext createAuthenticationRequestContext(String requestUrl) ` and now returns not only the redirect URL to the OIDC login but also a cookie containing the login state. This cookie is set by the frontend during a login attempt.

For BPC administrators

Install the new modules bpc-be-core.jar and bpc-fe-core.war. A restart of the BPC/Karaf is required. If the BPC is still unavailable, please delete the directory karaf/data and restart Karaf. (You may want to back up your log files first.)

Timeseries Management Administrators who do not belong to the "bpcadmin" role and previously only had the "webtsm_admin" permission now need the "webtsm_edit" permission instead. A Timeseries Management Administrator could also be assigned the "WEBTSM_ADMIN" role instead of the specific permission. This would also be more future-proof if, for example, future versions define fine-grained permissions for the endpoints instead of the "webtsm_edit" permission.

The Data Management Module no longer has a standalone backend component (bpc-be-vam.jar). It must be removed during the update.

To perform the update, first remove bpc-be-vam.jar and then install the updated bpc-fe-vam.war.

The Data Management Module has been incorporated into the regular release cycle.

Additional HTTP headers can be defined via the WebTSM setting module_apis, which are then set with every WebTSM API call. To do this, enter the HTTP headers to be set in the field additionalHttpHeaders (see example). Variables, such as the one below ${config.de.virtimo.bpc.core.karaf.uuid}, can be set to the same values as for the BPC HTTP Proxy.

Sharing links for monitor processes have been shortened. The link now only contains information about the active view, filters, and sorters.

Form versions and forms can now be deleted in the Forms Repository.

You can now configure the initial sort order for groups in the monitor settings. See setting column_groupDirection

Data used by OIDC providers for login is stored in an encrypted cookie on the client side. This prevents system overload caused by a large number of login requests.

For BPC module developers

If you have developed your own UserFlowIdentityProvider implementation, you must adapt it. The function ` URI createAuthenticationRequestURI(String requestUrl) ` has been replaced with ` UserFlowLoginContext createAuthenticationRequestContext(String requestUrl) ` and now returns not only the redirect URL to the OIDC login but also a cookie containing the login state. This cookie is set by the frontend during a login attempt.

For BPC administrators

Install the new modules bpc-be-core.jar and bpc-fe-core.war. A restart of the BPC/Karaf is required. If the BPC is still unavailable, please delete the directory karaf/data and restart Karaf. (You may want to back up your log files first)

Only the WebTSM backend communicates directly with Hakom. The WebTSM frontend now communicates only with the WebTSM backend. This means that a "HTTP Proxy" type backend Connection is no longer required, and the "tsm_backendConnectionId" setting has been removed from the WebTSM Viewer components.

If "useRendererValues" is true during a process status change, the fallback values "" and "*" are no longer displayed in the status combo box.

Please remove the values with the key "authorization" in the Timeseries Management JSON settings under General → module_apis. This value contains the username and password in plain text (Base64-encoded) and is no longer needed.

Timeseries Management administrators who do not belong to the "bpcadmin" role and previously only had the "webtsm_admin" permission now need the “webtsm_edit” permission instead. A Timeseries Management Administrator could also be assigned the "WEBTSM_ADMIN" role instead of the specific permission. This would also be more future-proof if, for example, in subsequent versions, fine-grained permissions are defined for the endpoints instead of the "webtsm_edit" permission.

Duplicate setting groups are merged into a single group

An error in schema generation for some DTO classes has been fixed.

Filtering by column is now possible again. An additional option has also been added to set a different template for the filter. This may be necessary if the column template accesses fields other than the one specified in dataIndex.

See also Configuring the Monitor Columns

targetModule is automatically converted to a string in the viewConfiguration

Safeguarding of BpcCommon.Api.getTranslation: If a translation incorrectly returns an object (e.g., for "config"), the system now falls back to the key string to avoid [object Object].

When the process status changes, "preselectState": "_first" can now also occur if "useDistinctValues" is false and custom states are used. See also Process Status Change Configuration

The spacing issue with checkboxes within a checkbox group has been resolved.

Previously, only columns in the child data were exported for which there were corresponding columns in the parent monitor using a dataIndex with the same name.

An export in the Process Monitor now works even if instance_data_view_limit or monitor_data_view_limit is less than 2500.

Update OpenSearch according to the update instructions

This update upgrades Apache Karaf to version 4.4.10. In this context, it is necessary to update the following modules: bpc-be-core, bpc-be-analysis, bpc-be-forms, and bpc-be-monitor.

Please update Karaf according to the update instructions.

Adjusting the logging configuration

The configuration file etc/org.ops4j.pax.logging.cfg was modified as part of an Log4J update. Important: Do not copy this file unchanged from an existing (old) Karafinstallation. If you have made customizations, please transfer them manually to the new configuration file.

Note for BPC module developers

If your BPC backend module uses the dependency jackson-annotations and has previously used the variable ${jackson.version} (to reference the same version as in the BPC-Coremodules), this needs to be updated. Use ${jackson.annotations.version} instead.

The Data Management Module no longer has a standalone backend component (bpc-be-vam.jar). It must be removed during the update.

To perform the update, first remove bpc-be-vam.jar and then install the updated bpc-fe-vam.war.

The Data Management Module has been incorporated into the regular release cycle.

The URL to Flow endpoints can be copied directly from the Flow Manager to the clipboard and reused, for example, for Forms submit URLs.

In the frontend, the global event beforeShowModule is fired before switching to a new view (module or module component). The following parameters are passed: the module ID of the current view, the module ID of the new view to be displayed, and additional options. If an event listener returns ` false `, the transition to the new view is canceled. If this behavior is implemented, the user should also receive feedback explaining why the transition was canceled.

Since BPC 4.2.13 and 4.1.25, process actions were no longer displayed in child grids. This has been fixed, and process starters are no longer incorrectly displayed in the child grid.

The behavior introduced in BPC 4.2.16 and 5.0.2, in which the connection is explicitly closed in the backend connection, sometimes led to issues where responses from the server were not transmitted at all or were transmitted incompletely.

BPC Breadcrumb Plugin is displayed again

The frontend now offers the option to manually start a tail sync for replication jobs. In addition, a manual tail sync can also be started via the REST API; see Replication API.

Similar to importing module settings, we now offer the option to import preconfigured OpenSearch indexes; see Installation with a Preconfigured BPC.

Tail Sync runs can now be logged. When logging is enabled, entries are written to the index bpc-tailsync-log. Additionally, the monitor Tail Sync Log Monitor is created. You can read more about this under Replication.

When creating a Log Service instance, the "External Reference" field is now included in the default configuration. Additionally, the field types object and flat_object have been added.

Tooltips with URL links can be hovered over with the cursor without them disappearing.

Fix for a potential DoS attack that leads to high memory consumption when there are a very large number of concurrent login requests.

The configured limit (max. number of records) for XLSX is now taken into account again when exporting data from the monitor. For CSV and JSON, a limit can now also be configured in the export dialog. An upper limit applies only to XLSX, not to other file formats.
See also Configuring the Monitor Data Export
Exporting Processes

The following issues have been resolved when exporting monitor data with configured custom renderers: - Custom renderers were only applied to string-type data. Now, custom renderers are also applied to integer, long, and boolean types during export. - For a column, you can set the custom renderer to the value true. In this case, a custom renderer with the same name as the one at dataIndex is used. If this does not exist, the "defaultRenderer" custom renderer is used. During export, only "defaultRenderer" was used in this case. This has been fixed.

For GUI modules that offer types, components with types can now be created again. Translations for the name of a type no longer require a "CORE_" prefix. The schema for the translation keys is "<MODULID>_INSTANCE_TYPE_<WERT>_"_.

The default instances in the Analysis module are now initialized correctly, so that the data modifier is available immediately.

An incorrect plugin configuration is now ignored during migration and logged as a warning.

The "Users" section on the "BPC Administration" documentation page is described in greater detail. See BPC Administration

Detailed description of the process action configuration. See Configuring Process Actions

Detailed documentation of the process status change configuration. See Process Status Change

See Configuring the Monitor Data Export

The documentation for column formatters and export formatters has been improved.

The migration guide (Migration from BPC 4.0 to BPC 4.1) has been updated.

See Chart Editor

Two new plugins have been added to link to internal or external content. See also core:/admin/plugins/external-link.adoc and core:/admin/plugins/internal-link.adoc

BPC now supports PKCE (Proof Key for Code Exchange) for OpenID Connect and Keycloak identity providers to enable a hardened login flow. To enable this, you must set the PKCE method in the identity provider’s backend Connection and, if necessary, configure this in your Keycloak client.

The highlighting of settings that have values different from the default has been changed.

Index cleanups are performed 60 seconds after BPC starts, and then run at the configured interval.

It is now possible to use the value ` 0 ` in the ` valueMap ` of a Custom Renderer and to see this value as a Label in the monitor. Previously, ` 0 ` values were not displayed.

In the form for sending notifications, the " bpcuser " role is preselected as the recipient group. It is no longer possible to send a notification without specifying a recipient group.

The values of the various options in combo boxes are no longer uniformly appended with "  ." This facilitates automated testing of the user interfaces.

The driver provided via pax-jdbc-mssql is no longer included in the release.

Ensure that the MSSQL driver you are using is at least the following version: 10.2.4, 11.2.4, 12.2.1, 12.6.5, 12.8.2, 12.10.2, 13.2.1

If an older driver is being used, it should be replaced. Remove the old driver by deleting it from the deploy directory or by uninstalling it from pax-jdbc-mssql or the driver itself. Then install an up-to-date driver (without the " `pax-jdbc-mssql`" feature). See also: Databases

A bug has been fixed where an incorrect process starter was displayed when exactly two process starters were configured, one of which was hidden.

If an error occurs during index migration, the index newly created for the migration is removed to prevent subsequent errors or to revert to a stable state.

If the configured Identity Provider is unreachable, the system no longer incorrectly logs that the local Karaf Identity Provider is selected as a fallback. Instead, it indicates that this could be enabled as a fallback.

Buttons that discard local changes now have a clearer text description.

Changes to the valid value range directly affect the validation of the default value.

Retrieving subgroups has been adjusted to accommodate changes in the Keycloak API.

In the central configuration file(bpc.env.sh), a bug in the commented-out option DE_VIRTIMO_BPC_DECANTER_APPENDER_OPENSEARCH_DELETEENTRIESOLDERTHAN has been fixed. Previously, enabling it had not worked, because the value must be enclosed in quotation marks. The Windows version was not affected.

An issue was resolved where changing the language in the Keycloak screen had no effect when redirected from BPC to Keycloak after logging out.

The status endpoint returned an incorrect response when incorrectly configured loggers were set up.

This update upgrades the Karaf version to 4.4.8. It is necessary to update the modules bpc-be-core, bpc-be-analysis, bpc-be-forms, and bpc-be-monitor.

For BPC module developers

With the updated Karaf, we are shipping CXF 3.6.8 instead of 3.6.7, which provides Jackson version 2.19.2.

Please update the CXF version (3.6.8) and the Jackson version (2.19.2) in your pom.xml. To do this, check whether you have an import package statement for this version. This must be added or updated if you use Jackson functions such as the ` ObjectMapper ` class.

HTTP calls made via an HTTP proxy or Flow connection filter out the BPC API key header (X-APIKey). Note: This could affect existing BPC configurations if, for example, an INUBIT process is triggered that, in turn, makes calls to the BPC API using the API key sent along with it. (In this case, it would be better to store a fixed BPCAPI key in the INUBIT process.)

In the frontend, it is possible to redirect to a BPC URL via the query parameter redirectPostAuth after the login process. This works for all OIDC identity providers.

The cells in the dashboard’s table layout now make better use of their available space, and spacing between cells is maintained. Errors no longer occur when resizing cells.

The endpoint /cxf/bpc-core/opensearch/indices/compact does not return any OpenSearch internal indexes. These are all indexes named with an . prefix. Accordingly, these are no longer filtered in index selectors in the frontend.

A new filter type, json, has been added to display filtered structured data in the column header. See Filter Columns

The tooltips for Cron patterns in replication have been updated to include a link to the Quartz Scheduler documentation.

For Boolean values in the settings tables, a combo box is no longer displayed; instead, only the checkbox with the truth value appears. The value can be changed by clicking, pressing the spacebar, or pressing Enter.

The classes arrow-spacing-sm (small) and arrow-spacing-xs (extra small) can now be applied to buttons to reduce the arrow spacing.

The mouse pointer now appears over checkboxes and radio groups in a way that clearly indicates You can change their state by clicking here.

The " licencedModules " setting can no longer be edited in the frontend. Previously, the setting could be edited, but the value was not applied.

Internal calls to the KeyCloak API to query users, groups, etc., no longer use Integer.MAX_VALUE for the GET parameter ` max ` to prevent false-positive blocking by Web Application Firewalls (WAF).

HTTP calls made via an HTTP proxy or Flow connection filter out the BPC API key header (X-APIKey). Note: This could affect existing BPC configurations if, for example, an INUBIT process is triggered that in turn makes calls to the BPC API using the API key provided. (In this case, it would be better to to store a static BPC API key in the INUBIT process.)

For new backend Connections of the HTTP Proxy and Flow types, the " Filter BPC Session " option is enabled by default.

If you use the file custom.java.security, you should adjust the property jdk.tls.disabledAlgorithms to make the TLS configuration stricter and thus more secure.

Replication could get stuck in a specific time window if it was adjacent to the present and no records were found.

Views are correctly marked as changed if the view object contains new values or objects. If new columns or grids have been added in additional tabs, the view is automatically saved for the user, provided the user has permission to save the view. A message is displayed indicating whether the save was successful or failed.

See monitor:/admin/process_views.adoc#_gespeicherte_ansicht_ändern

In BPC 5.0.0, unsaved changes occur in views from older versions because the fields in the model have been updated. The views must then be saved once.

An issue has been resolved where errors could occur when creating multiple new users, roles, or permissions simultaneously while Karaf was selected as the identity provider.

The resizing of widgets in the dashboard table layout has been improved, and the likelihood of errors has been reduced.

When retrieving translations (cxf/bpc-core/i18n/translations or in the frontend), custom entries for the fallback language are now also taken into account.

Language identifiers are now translated into the selected BPC language in the BPC interface.

The documentation has been updated to include a description of the frontend URL Parameters.

Previously, a large portion of the Identity Provider (Backend Connections) configuration was handled via a single JSON setting. This has been split into individual settings. Existing configurations will be migrated automatically. If older deployment exports of Identity Provider components are being used, it is best to recreate them.

See also: Creating, Configuring, and Using an Identity Provider, Database as Identity Provider, Connecting and Setting Up Keycloak, Keycloak and Dynamic Redirect URIs, Deployment Constraints

The OpenSearch configuration directory can be configured via OPENSEARCH_PATH_CONF. This allows you to move the configuration directory out of the OpenSearch directory. As a result, you will no longer overwrite it during an OpenSearch update. See also Moving the OpenSearch Configuration.

The bundle installation file now ships with BPC using a configuration directory moved to INSTALLATIONSVERZEICHNIS/opensearch_config.

It is recommended to set OPENSEARCH_PATH_CONF in BPC.env.

A configuration interface for identity providers is now available.

This update requires you to update Karaf.

The BPC provides OpenAPI-compliant specification files for our APIs. These are located under Downloads and can also be accessed dynamically via the BPC, provided this option is enabled. For more information, see in the BPC-API section.

If a BPC module used a different versioning scheme than the BPC Core, the project.version property affected the dependencies in the BPC Core and caused problems. Dependencies within the BPC Core are no longer affected by the ` project.version ` property in the module.

The readability of large numbers in the number of records has been improved by adding thousands separators. The "Remove Filter" button now includes additional information about the currently applied filters.

Moving and resizing widgets in the dashboard while the table layout is enabled has been improved.

The OpenSearch configuration directory can be configured via OPENSEARCH_PATH_CONF. This allows you to move the configuration directory out of the OpenSearch directory. As a result, you will no longer overwrite it during an OpenSearch update. See also Moving the OpenSearch Configuration.

In the bundle installation file, BPC is now delivered with a configuration directory moved to INSTALLATIONSVERZEICHNIS/opensearch_config

It is recommended to set OPENSEARCH_PATH_CONF in BPC.env.

Until now, a large portion of the Identity Provider (Backend Connections) configuration was handled via a single JSON setting. This has been split into individual settings. Existing configurations will be migrated automatically. If older deployment exports of Identity Provider components are being used, it is best to recreate them.

See also: Creating, Configuring, and Using an Identity Provider, Database as Identity Provider, Connecting and Setting Up Keycloak, Keycloak and Dynamic Redirect URIs, Deployment Constraints

The HTTP proxies configured in BPC now also forward OPTIONS and PATCH requests.

The plugin can now configure a process that is displayed immediately upon triggering. In addition, the text and icon can now be freely configured. See also Process Starter Plugin

The option to group settings is now enabled by default. We recommend using this view, as it displays the settings in a shared context.

The names and tooltips of settings have been revised.

The output of the HTML component is sanitized to remove script content, for example.

The default window size for Process Starter can now be configured.

See Process Starter

During the monitor export, empty columns for which there is no OpenSearch mapping yet are also exported.

A preselected value can now be configured for the process status change. The preselection is controlled based on the configuration preselectState in the setting function_changeStateConfig.

"preselectState": "_first": Always selects the first available value from the dropdown. "preselectState": "<Suchwert>": Selects the first entry that contains the specified text (case-sensitive). Both raw values and display names (from Custom Renderer) can be used.

If exactly one process is loaded and there are exactly two values to choose from, the status field automatically selects the status that does not match the current status.

Any path information is ignored to prevent path traversal attacks.

During replication, Shadow Copy, Tail Sync, and Consistency Check encountered issues if the setting targetIndexCaseSensitivityOfFields was set to lowerCase or upperCase. In the case of Shadow Copy and Tail Sync, this could result in data loss.

The ProcessStarter configuration for windowWidth and windowHeight now correctly affects the window.

The order of properties in JSON forms is preserved.

OpenSearch exceptions now also display triggers, if available. A more detailed error message is displayed in the Monitor Grid if full-text search is enabled.

Advanced Search has been added for filtering limitations.

File downloads are now possible in both parent and child data.

Due to storage space constraints, fields containing binary data are now excluded from the result data of OpenSearch queries.

A bug has been fixed where newly arriving notifications were incorrectly hidden by the "Show Only Unread" filter.

When using the DB2 database, the log no longer displays warnings with the message " Did not recognized the used database."

When the BPC is running in a cluster, it may not be possible to deactivate maintenance mode via the GUI.

See also Module and Module Instance Settings

See Core Services and Create-Index-related BPC settings

In some cases, the message "Expired copy of the Froala Editor" was displayed in the HTML editor.

When handling events, Map should be used instead of Dictionary.

The logging configuration has been changed so that session tokens are masked. For new Karaf installations, this happens automatically. For existing installations, please update the configuration file [KARAF]/etc/org.ops4j.pax.logging.cfg. Replace the old line

with the following lines:

Since session tokens in Keycloak and OIDC are UUIDs that are also used elsewhere, we log the first and last four characters here.

The confirmationText of a process action is now displayed if either requireComment or requireConfirmation is true.

If binary files were uploaded via INUBIT or another backend system, the files might have been corrupted during download or viewing.

An error that occurred when updating the tooltip while switching between states in the Monitor has been fixed; this error occurred when multiple grids were disabled.

The " Monitor_FileReferenceColumn " field was missing from the editor.

When opening a monitor via a deep link that included filters, those filters might still be displayed in the column header even after being removed.

A bug has been fixed where the date filter was not displayed correctly in the monitor.

When replicating MSSQL tables, schema and table names masked with square brackets and quotation marks—such as [customer-abc].logging or "customer-abc".[logging]—are now also supported.

An error has been fixed that prevented users from editing a monitor view despite having the " bpcMonitor_editMonitorViews " permission and the necessary write permissions.

For existing Karaf installations, include the following value in KARAF/etc/custom.properties:

A user’s missing first or last name is no longer displayed as "null."

See core:/dev/generated/api/log_service.adoc and core:/dev/generated/api/storage.adoc

Dashboard widgets now display the configuration icon only if the user is allowed to edit the dashboard. To do so, the user needs the " `bpcDashboard_editDashboard`" permission. Users without this permission can no longer edit dashboard widgets. If editing capabilities (e.g., for custom widgets) are to continue to be offered, either the corresponding permission must be granted or the configuration must be provided through alternative means (e.g., via the widget header).

A health check endpoint can now be configured in the Identity Provider Backend Connections if the identity provider in use provides such an endpoint. Once configured, this status can be queried in the Status API via /cxf/bpc-core/status/identity-provider. The /cxf/bpc-core/status/health endpoint includes the identity provider status in the health check. For further details, see Configuring the Identity Provider and Status API. Information on deploying the health check endpoints in Keycloak can be found at Connecting and Setting Up Keycloak.

In the moduleHeaderContent setting, the parameter showSelectionCounter in the metablock can be used to control whether the number of selected records is displayed.

See also Monitor Quick Actions

Forms now correctly translates Labels for all components, including in the state. This makes it possible to set bindings on Labels. See Multilingual Content.

setFormState can now also correctly handle Labels in multiple languages. As part of this update, a bug was fixed that caused setFormState to remove bindings, resulting in the submit after setFormState containing only data from before setFormState. Additionally, all components can now be used in combination with setFormState, including combo boxes and tables.

The current language is now stored under /language. Date formats are now handled consistently by the date field and the table and formatted appropriately for the user based on the language.

Dashboard widgets now only display the configuration icon if the user is allowed to edit the dashboard. To do so, the user requires the " `bpcDashboard_editDashboard`" permission. Users without this permission can no longer edit dashboard widgets. If editing capabilities (e.g., for custom widgets) are to continue to be offered, either the corresponding permission must be granted, or the configuration must be provided via alternative methods (e.g., via the widget header).

In a cluster environment, backups must be initiated by only one node. Due to the change, the "bpc_backups_scheduled_jobs" metric has been removed. It contained the number of existing backup jobs.

The startup script no longer waits 30 seconds after OpenSearch and Karaf have started. If problems arise where OpenSearch is not available in a timely manner, the watchdog should be used.

The startup script no longer makes any changes to the environment. Directories must be configured according to the installation instructions, and JAVA_HOME must also be configured correctly.

A loading animation is now displayed while the export is in progress. In addition, error messages are now displayed when an error occurs.

The Status API has been extended to include an endpoint /cxf/bpc-core/status/license, which returns 200 OK if the license is valid and not expired, and 503 Not Available otherwise. The /cxf/bpc-core/status/health endpoint includes the license status in the health check. See also API documentation

Rows in the navigation settings are now highlighted in alternating colors to improve readability.

The descriptive texts during upload have been adjusted to accommodate the different types of content (modules, licenses, and DB drivers).

Users are now retrieved from Keycloak in batches. When using external Identity Providers in Keycloak (e.g., LDAP), longer load times may still occur if Keycloak is performing a synchronization.

The ProzessStarter configuration for windowWidth and windowHeight now correctly affects the window.

The selection of an operator for "number" filters has been restricted to the operator list. "=" is defined as the default operator, and the default operator can also be changed in the filter configuration within the column configuration. See also Configuring the Monitor Columns

The error message for validating entries in the ProcessStarter table is no longer truncated.

The reset function previously removed bindings. As a result, the current state could no longer be submitted after a reset. This issue has been resolved.

The Table and Combo Box components have been improved and now behave like the other components.

The bpcMonitor_editMonitorViews permission can be set for specific instances to create and modify views in certain monitors by appending the module ID at the end.

See Application Examples

See OpenSearch Index View

See Developing a BPC Module and Module and Module Instance Settings

There is now a description of the BPC’s internal model_version at Versioning of the Internal BPC Configuration. It also explains that this can affect a BPC downgrade and the Deployment between different BPCs.

The changelog now notes when an update to the internal configuration is available.

In addition, Administration Changelog displays an overview of all versions in which a change to model_version occurred. As part of this, an overview of versions with Karaf and OpenSearch updates has also been added.

The documentation on creating and using Monitor Deeplinks has been expanded. Monitor Deeplink

See MinIO as an S3 Backup for OpenSearch

The installation via bundle file is now described at Installation. The included start and stop scripts are now described.

Notes added stating that database connections generally require read-only permissions.

See Backend Connections, Security, and Documents.

Instructions for downgrading the BPC, taking technical specifics into account. See: * Versioning of the Internal BPC Configuration * Troubleshooting * Downgrade Guide

Revised instructions. See Developing a BPC Module

Correction of spelling errors and improvement of wording

The Flow module is described on its own documentation page, along with its possible uses.

Update OpenSearch according to the update instructions

Monitors that contain an externalReference field with an IGUASU reference can display a link that allows you to jump to the data source in IGUASU. To enable this, the renderer flow!_!flowRenderer must be set in the monitor column configuration.

See also: BPC → IGUASU

Scripts are provided that can be used to start and stop BPC, Karaf, and OpenSearch.

See Download - Virtimo File Server

The user session can be supplemented with customData that comes from the Additional Info endpoint of the Identity Provider Backend Connection.

See also Add additional organizations, roles, permissions, and other data to the user session

Replication now supports the direct entry of an SQL query as an alternative to existing database tables/views.

See also sourceCommonTableExpressionQuery in Replication

The LogService endpoint for opening a monitor now also supports cases where there are multiple monitors for a LogService and displays a selection window with the available monitors http://<bpc_host>:<bpc_port>/cxf/bpc-logservice/<logservice-instance-id>/open/monitor

See also API documentation: Log Service API

The OpenSearch log contains many entries such as "QueryGroup _id can’t be null, It should be set before accessing it." This is a known OpenSearch bug that was introduced in version 2.18.0. We have reduced the output as much as we could on our end.

To display existing charts using a darktheme without a white background, the background color of the charts should be set to full transparency under Chart Configuration → Settings → Background Color (RGBA alpha value set to 0).

The " Common Table Expression Abfrage " setting in replication can now be edited in an editor that supports SQL syntax.

Snapshots whose names do not conform to the current naming scheme have blocked the execution of backups.

When the HTTP proxy used an HTTP/2 connection, the pseudo-header ":status" was passed on to the client. Under a strict interpretation, this results in an error. For example, nginx reported a 502 Bad Gateway error to the client in this case.

Varying plugin load times resulted in a different order. The order specified in the configuration is now maintained regardless of load time.

If a deployment was performed from a BPC with existing monitor views to a BPC that did not yet have any views, an error occurred.

This error has been fixed.

A bug has been fixed that prevented instance-specific HTML content editing permissions from being granted by the role htmlcontent_editor_<MODUL-ID>.

When an editor field was displayed in a pop-up window, the initial value of the field was shown in that window. Any changes previously made by the user were ignored.

If an element with subelements was created in the navigation, brief freezes could occur in the application if a subelement pointed to the same module as the parent element.

Update OpenSearch according to the update instructions

Properties were set in the custom.java.security

If you are not yet using a ` custom.java.security ` file via Central configuration file, you should do so.

Existing ` custom.java.security ` files should be updated with the following entry:

The bpc.env files now also set the security.properties for OpenSearch from the file custom.java.security. As a result, changes made to this file affect both Karaf and OpenSearch.

If you are using a BPC.env file, it is recommended that you update it. If it does not already exist, the file custom.java.security be added. To do this, the following must be added.

See also Central configuration file

The "Data Filter Operator" setting can now be used to configure how different data filters (for organizations, roles, permissions, or users) are linked together.

With OR (default), all data that meets any one of the filter settings is displayed. With AND, only data that meets all filter settings is displayed.

See also Restrict Visibility of Monitor Data

Settings can now be protected from changes via the BPC license. This will primarily be used in our cloud installations (K8s). For example, there we use the core setting 'backupRepository' to define the configuration of OpenSearch backups in an Amazon S3 bucket, and we do not want this to be changeable via the BPC frontend.

To achieve this, when creating the license, the XML can be extended with the list element ` NON_WRITEABLE_SETTINGS `, containing the IDs of the non-editable settings.

Excerpt from a sample license:

The settings (example: _core_noinstance_backupRepository) are the same as those used in the OpenSearch index ‘BPC-configuration’.

The structure is as follows: <ModuleId>_<InstancId>_<SettingName>

If the setting pertains to a module and not to an instance or component, then the value noinstance must be used for the <InstanceId>. You can access the <SettingName> by displaying the “ID” column in the Settings grid in the BPC frontend.

Example: _core_noinstance_backupRepository

We have reduced the number of shards to 1 in the Core_IndexTemplates setting. This is also the default setting that Elasticsearch/OpenSearch has been using for new indices for the past few years. This change only affects newly created indices. Existing indices are not affected.

The application toolbar has been made slightly lighter. In the admin area, modified text in grids is now displayed with better contrast. The loading animation has been adjusted.

Optimizing accesses to the OpenSearch Backup API results in fewer accesses to the data storage. This reduces the associated costs, for example, when using Amazon S3.

The interface for configuring and creating Analysis components has been standardized.

Performance has been improved and heap memory usage reduced. Java must perform significantly fewer garbage collector calls. This is especially true when the log levels for the BPC packages are set to the default (WARN). This applies to the standard BPC modules for Karaf as well as the OpenSearch plugin.

When saving JSON settings, attributes within objects were automatically sorted. This behavior has been disabled. This makes it possible to customize the order according to your own criteria.

The currently set font can be retrieved via the CSS variable --font-family.

The bpc.env files now also apply the security.properties settings from the file custom.java.security to OpenSearch. As a result, changes made to this file affect both Karaf and OpenSearch.

If you are using a BPC.env file, it is recommended that you update it. If it does not already exist, the file custom.java.security To do so, add the following:

See also Central configuration file

The license filename may now also be license.xml.virtimo. Previously, it had to be license.xml.bpc. This makes it possible to use a license that is also a valid INUBIT license file.

When using dark themes, charts now use styling compatible with dark themes.

This change speeds up the loading of the BPC configuration on the client.

Properties have been set in the custom.java.security

If you are not yet using a custom.java.security file via Central configuration file, you should do so.

Existing custom.java.security files should be updated with the following entry:

The placeholder #user.loginName# is now correctly replaced in the Data_Filter when the dynamic filter # is used.

If the client sends multiple session cookies—possibly because multiple BPC instances are installed on the server—the appropriate session cookie is now taken into account.

In cases where data changed frequently, errors could occur in the monitor when displaying detail views. As a result, the entire rendering of the application was disrupted, and the page had to be reloaded manually.

Uploaded files are no longer kept entirely in memory. This reduces memory usage and prevents "OutOfMemoryException".

The page Developing a BPC Module has been translated into German.

See BPC Cluster

The documentation Chart Editor has been updated to clarify the required configuration of data types for axes and data series.

See Data Management Installation and Update

This update requires updating Karaf and the modules bpc-be-core, bpc-be-analysis, bpc-be-forms, and bpc-be-monitor.

For BPC module developers:

In our earlier Karaf versions, we used CXF version 3.5.4. This CXF version includes Jackson version 2.14.3. We now ship Karaf with CXF 3.6.5, which includes Jackson version 2.17.2.

Please update the CXF version (3.6.5) in your pom.xml. More importantly, you must also update the version of Jackson you are using (2.17.2). To do this, check whether you have an import package statement for this version. This must be added or updated if you use Jackson functions such as the ` ObjectMapper ` class.

Replace

with

Update OpenSearch according to the update instructions

New data in the "Frontend Log Monitor" is now displayed or reloaded immediately.

In selected code editors (JSON, CSS, …​), you can now use the to display the content in a pop-up window. This provides more screen space and makes it easier to view or edit the content.

BPC module developers can now use the corresponding components from the CoreCommon package.

The log level for the BPC plugin in OpenSearch has been reduced from trace to info. This setting can be found in the file opensearch/config/log4j2.properties.

Modules can now send updates to the plugins loaded there via their hooks. See also: Developing BPC Plugins

The interface for configuring and creating replication components has been standardized. It is no longer possible to directly enable or disable individual replications in the list of replication components. This is done after selecting a replication in the detail view.

The option for "CascadingDynamicFilter" has been added to the administration interface for monitor components.

The LogService API for creating DeepLinks to monitors can now handle various query parameters to set appropriate filters in the monitor.

A deep link to the Audit Log Monitor can be retrieved via the Audit Log API.

The bundle info, which can be accessed via the Karaf console, no longer displays the build time but rather the time of the last change to the underlying source code.

Forms in the detail view now receive updated data when the monitor reloads. To suppress this behavior—since the data changes may not be relevant to the form—you can set the option “ ignoreUpdates ” on the form in the detail configuration. See also: Configuring Monitor Detail Views

AuditLog and LogService API documentation updated. See: BPC API

The possible query parameters for the AuditLog and LogService APIs for opening a monitor via deep link have been added to the documentation.

See BPC API