Changelog

Data used for login with OIDC providers is stored encrypted in a cookie on the client. This prevents overload from a very large number of login requests.

For BPC module developers

If you have developed your own UserFlowIdentityProvider implementation, you need to adapt it. The function URI createAuthenticationRequestURI(String requestUrl) has been replaced with UserFlowLoginContext createAuthenticationRequestContext(String requestUrl) and now, in addition to the redirect URL for the OIDC login, also returns a cookie containing the login state. This cookie is set by the frontend during the 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 necessary. If the BPC is still not available afterwards, please delete the directory karaf/data and restart Karaf again. (You may want to back up your log files beforehand.)

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, for example, if in subsequent versions more fine-grained permissions are defined for the endpoints instead of the "webtsm_edit" permission.

The Data Management module no longer has its own backend component (bpc-be-vam.jar). It must be removed during the update. To use the module, it is sufficient to use bpc-fe-vam.war.

The Data Management module has been included in the regular release cycle.

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

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

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 for login with OIDC providers is stored encrypted in a cookie on the client. This prevents overload from a very large number of login requests.

For BPC module developers

If you have developed your own UserFlowIdentityProvider implementation, you need to adapt it. The function URI createAuthenticationRequestURI(String requestUrl) has been replaced with UserFlowLoginContext createAuthenticationRequestContext(String requestUrl) and now, in addition to the redirect URL for the OIDC login, also returns a cookie containing the login state. This cookie is set by the frontend during the 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 necessary. If the BPC is still not available afterwards, please delete the directory karaf/data and restart Karaf again. (You may want to back up your log files beforehand.)

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

If "useRendererValues" is true during the 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 setting 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, for example, if in subsequent versions more fine-grained permissions are defined for the endpoints instead of the "webtsm_edit" permission.

Duplicate setting groups are merged into one group

The error in the schema generation of some DTO classes has been fixed.

Filtering on the 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 those specified in dataIndex.

See also Configuration of the monitor columns

targetModule is automatically converted to a string in the viewConfiguration

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

When changing the process status, it is now also possible to use "preselectState": "_first" if "useDistinctValues" is false and custom states are used. See also Process Status Change Configuration

The spacing issues of checkboxes within a checkbox group have been fixed.

Previously, only columns in the child data were exported for which there are also columns in the parent monitor that use 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 guide

With this update, the version of Apache Karaf is raised to 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 guide.

Adjustment of the logging configuration

The configuration file etc/org.ops4j.pax.logging.cfg was adjusted as part of a Log4J update. Important: Do not simply copy this file unchanged from an existing (old) Karaf installation. If you have made individual adjustments, 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 so far used the variable ${jackson.version} (to reference the same version as in the BPC core modules), this needs to be adjusted. Instead, use ${jackson.annotations.version}.

The Data Management module no longer has its own backend component (bpc-be-vam.jar). It must be removed during the update. To use the module, it is sufficient to use bpc-fe-vam.war.

The Data Management module has been included in the regular release cycle.

In the frontend, it is now possible to manually start a tail sync for replication jobs. Additionally, a manual tail sync can also be started via the REST API; see Replication API.

Analogous to the import of module settings, we now offer the possibility to import preconfigured OpenSearch indices, see Installation with 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 find more information about this under Replication.

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

Fix for a potential DoS attack that leads to high memory consumption when there are a large number of parallel log-in requests.

The configured limit (max. number of records) for XLSX is now taken into account again during data export in the monitor. For CSV and JSON, a limit can now also be configured in the export mask. There is only an upper limit for XLSX, not for other file formats.
See also monitor:admin/configuration_monitor_export.adoc
Export of processes

When exporting monitor data with configured custom renderers, the following errors were fixed: - Custom renderers were only applied to data of type String. Now, custom renderers are also applied to the types Integer, Long, and Boolean during export. - For a column, you can set the value true as a custom renderer. In this case, a custom renderer with the same name as the dataIndex is used. If this does not exist, the custom renderer "defaultRenderer" 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 once again be created. Translations for the designation of a type no longer require a "CORE_" prefix. The schema for the translation keys is "<MODULID>_INSTANCE_TYPE_<VALUE>".

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

A faulty plugin configuration is now ignored during migration and logged as a warning.

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

See monitor:admin/configuration_monitor_export.adoc

The documentation of formatters in columns and formatters in export has been improved.

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

See Chart Editor

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

Extended description of the process action configuration. See Configuration of process actions

Two new plugins have been added to link to internal or external content. See also External Link and Internal Link

BPC now supports PKCE (Proof Key for Code Exchange) for OpenID Connect and Keycloak Identity Provider to enable a hardened login flow. To activate this, you need to set the PKCE method in the Identity Provider backend connection and, if necessary, configure this in your Keycloak client.

The marking of settings that have values differing 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 it as a label in the monitor. Previously, values of 0 were not displayed.

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

The values of the different options in combo boxes are now no longer generally supplemented with a  . This makes automated testing of the interfaces easier.

The driver provided via pax-jdbc-mssql is no longer delivered.

Please ensure that the MSSQL driver used has at least one of the following versions: 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 pax-jdbc-mssql or the driver itself. Then install a current driver (without the pax-jdbc-mssql feature). See also: Databases

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

If an error occurs during the migration of an index, the newly created index for the migration will be removed again in order to avoid subsequent errors or to revert to a stable state.

If the configured identity provider is not reachable, it is no longer incorrectly logged that the local Karaf identity provider has been selected as a fallback. Instead, it is indicated that this could be enabled as a fallback.

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

Changes to the valid value range have a direct impact on the validation of the default value.

Ein Fehler wurde behoben, dass der Endpunkt GET /cxf/bpc-core/im/organisations nicht mehr KeyCloak-Gruppen listet, die als Untergruppen definiert sind. Grund war eine Änderung im Verhalten von KeyCloak ab Version > 26.

In the central configuration file (bpc.env.sh), an error in the commented-out option DE_VIRTIMO_BPC_DECANTER_APPENDER_OPENSEARCH_DELETEENTRIESOLDERTHAN was fixed. Previously, activation did not work because the value must be enclosed in quotation marks. The Windows variant was not affected.

A bug was fixed where changing the language in the Keycloak screen had no effect when being redirected from BPC to Keycloak via logout.

The status endpoint returned a faulty response when incorrectly configured loggers were stored.

With this update, the Karaf version is upgraded 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 delivering CXF 3.6.8 instead of 3.6.7, which provides Jackson in version 2.19.2.

Please update the CXF version (3.6.8) and Jackson version (2.19.2) in your pom.xml. Check whether you have an Import-Package statement for this version. This must be added or adjusted if you use Jackson features such as the ObjectMapper class.

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

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

The cells in the dashboard’s table layout make better use of their available space and maintain proper spacing from other cells. Errors no longer occur when enlarging or resetting the size of cells.

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

A new filter type json has been added, which displays filtered structured data in the column header. See Filter columns

The tooltips for cron patterns in replication have been supplemented with a reference 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 is shown. The value can be changed by clicking, pressing the space bar, or pressing Enter.

Buttons can now use the classes arrow-spacing-sm (small) and arrow-spacing-xs (extra small) to reduce the spacing of the arrow.

For checkboxes and radio groups, the mouse pointer is now displayed in such a way that it is clear the user can change the state by clicking.

The setting licencedModules 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, in order to prevent false-positive blocking by Web Application Firewalls (WAF).

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

For new backend connections of the type HTTP-Proxy and Flow, the option Filter BPC Session 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 therefore more secure.

It could happen that replication got stuck in a certain time window if this window bordered on the present and no records were found.

Views are correctly marked as changed when the views object contains new values or objects. If there are new columns or added grids in additional tabs, the view is automatically saved for the user, provided the user has permission to save the view. There is a notification 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 then need to be saved once.

A problem was fixed where errors could occur when creating several new users, roles, or permissions at the same time and Karaf was selected as the identity provider.

The resizing of widgets in the dashboard’s table layout has been improved and susceptibility to errors has been reduced.

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

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

The documentation has been supplemented with a description of the Frontend URL parameter.

For the Identity Provider (Backend Connections), a large part was previously configured via a JSON setting. This has been split into individual settings. Existing configurations are migrated automatically. If older deployment exports of Identity Provider components are used, it is best to recreate them.

See also: Create, configure and use an identity provider, Database as identity provider, Keycloak as an identity provider, Keycloak and dynamic redirect URIs, Deployment constraints

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

In the bundle installation file, BPC is now delivered with a configuration directory outsourced to INSTALLATION_DIRECTORY/opensearch_config.

It is recommended to set OPENSEARCH_PATH_CONF in the bpc.env.

A configuration interface for identity providers is now available.

With this update, it is necessary to update the Karaf.

The BPC provides OpenApi-compliant specification files for our APIs. These can be found under Downloads and can alternatively also be accessed dynamically via the BPC, provided this option is enabled. You can find more information in the section BPC-API.

If a BPC module used a different versioning than the BPC core, the project.version property affected the dependencies in the BPC core and caused problems. The dependencies within the BPC core are now no longer influenced by the project.version property in the module.

The readability of large numbers in the number of records has been improved by using thousand separators. The "Remove filter" button now also contains information about the currently applied filters.

The moving and resizing of widgets in the dashboard, with the table layout enabled, has been improved.

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

In the bundle installation file, BPC is now delivered with a configuration directory outsourced to INSTALLATION_DIRECTORY/opensearch_config.

It is recommended to set OPENSEARCH_PATH_CONF in the bpc.env.

For the Identity Provider (Backend Connections), a large part was previously configured via a JSON setting. This has been split into individual settings. Existing configurations are migrated automatically. If older deployment exports of Identity Provider components are used, it is best to recreate them.

See also: Create, configure and use an identity provider, Database as identity provider, Keycloak as an identity provider, 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. Additionally, the text and icon can now be freely configured. See also Process Starter Plugin

The option for grouping settings is now initially enabled. It is recommended to use this view, as the settings are displayed together in a common context.

The names and tooltips of settings have been revised.

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

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

See Process Starter

When exporting from the monitor, empty columns are also exported for which there is no OpenSearch mapping yet.

For the process status change, it is now possible to configure the preselection of a value. The preselection is controlled via the configuration preselectState in the setting function_changeStateConfig.

"preselectState": "_first": Always selects the first available value from the dropdown. "preselectState": "<search value>": 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 correspond to the current status.

Example configuration

Any path specifications are ignored to prevent path traversal attacks.

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

The ProzessStarter 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 shown in the monitor grid if full-text search is enabled.

For limitations when filtering, Complex search has been added.

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

For storage space reasons, the fields with binary data are now excluded from the result data of the OpenSearch queries.

A bug was fixed where newly arriving notifications were incorrectly hidden by the "Show only unread" filter.

When using the DB2 database, the log no longer issues a warning with Did not recognized the used database.

If the BPC is operated in a cluster, it was sometimes not possible to deactivate maintenance mode via the GUI.

See also Module and module instance settings

See Core Services settings and Create-Index relevant BPC settings

In the HTML editor, "Expired copy of the Froala Editor" was sometimes displayed.

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

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

with the following lines

Since with Keycloak and OIDC the session tokens 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 loaded via INUBIT or another backend system, it could happen that the files were corrupted when downloading or viewing them.

A bug was fixed when switching between states in the monitor that affected the tooltip update, which occurred when multiple grids are disabled.

The field Monitor_FileReferenceColumn was missing in the editor.

When calling up a monitor via a deeplink including filters, it could happen that these filters were still displayed in the column header even after being removed.

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

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

A bug was fixed that prevented users from editing a monitor view even though they had the bpcMonitor_editMonitorViews permission and the necessary write access.

For existing Karaf installations, add the following value to KARAF/etc/custom.properties:

The missing first or last name of a user is no longer displayed as "null".

See Log Service API and Storage API

Dashboard widgets now only display the configuration icon if the user is allowed to edit the dashboard. For this, they need the bpcDashboard_editDashboard permission. Users without this permission can no longer edit dashboard widgets. If editing options (e.g., for custom widgets) should still be offered, the corresponding permission must either be granted or the configuration must be provided through alternative means (e.g., via the widget header).

In the Identity Provider Backend Connections, a health check endpoint can now be configured if the identity provider in use provides such an endpoint. If this is configured, the 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 Configure Identity Provider and Status API. Information on providing the health endpoints in Keycloak can be found in Keycloak as an identity provider.

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

See also Monitor quick functions

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

setFormState can now also handle labels in multiple languages correctly. In this context, a bug was fixed that caused bindings to be removed when using setFormState, so that after setFormState, only data from before setFormState was present in the submit. In addition, all components can now be used in combination with setFormState, including Combobox and Table.

The current language is now stored under /language. The date formats are now handled the same way by the date field and the table and are formatted appropriately for the user depending on the language.

Dashboard widgets now only display the configuration icon if the user is allowed to edit the dashboard. For this, they need the bpcDashboard_editDashboard permission. Users without this permission can no longer edit dashboard widgets. If editing options (e.g., for custom widgets) should still be offered, the corresponding permission must either be granted or the configuration must be provided through alternative means (e.g., via the widget header).

In cluster operation, backups only need to be initiated by one node. As a result of the changeover, the metric "bpc_backups_scheduled_jobs" was removed. It contained the number of existing backup jobs.

The start script no longer waits 30 seconds after starting OpenSearch and Karaf. If problems occur where OpenSearch is not available in time, the Watchdog should be used.

The start 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.

For the period during which the export takes place, a loading animation is now displayed. In addition, error messages are now also shown in the event of an error.

The Status API has been extended with an endpoint /cxf/bpc-core/status/license, which returns 200 OK for a valid, non-expired license, otherwise 503 Not Available. The /cxf/bpc-core/status/health endpoint includes the license status in the health check. See also API Documentation

In the navigation settings, the rows are now alternately colored differently to improve readability.

The descriptive texts during upload have been adjusted to accommodate the different contents (modules, license, and DB driver).

The users are now retrieved from Keycloak in blocks. When using external identity providers in Keycloak (e.g., LDAP), longer loading times may still occur if Keycloak performs a synchronization during this process.

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. The default operator is defined as "=" and, additionally, the default operator can be changed in the filter configuration within the column configuration. See also Configuration of the monitor columns

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

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

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

The right bpcMonitor_editMonitorViews 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 indices view

See Develop BPC module and Module and module instance settings

There is now a description of the internal model_version of the BPC at Versioning of the internal BPC configuration. It also explains that this can have an impact on a Downgrade of the BPC and on Deployment between different BPCs.

The changelog now indicates when there is an update to the internal configuration.

Additionally, an overview of all versions in which a change to the model_version took place is now displayed in Administration changelog. In this context, an overview of versions with Karaf and OpenSearch updates has also been added.

The documentation on the creation and use of monitor deeplinks has been expanded. Monitor deeplink

See MinIO as an S3 backup for OpenSearch

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

Notes added that usually only read permissions are necessary for database connections.

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 Develop BPC module

Correction of spelling mistakes and improvement of wording

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

Update OpenSearch according to the update guide

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

See also: BPC → IGUASU

Scripts are provided that allow BPC or Karaf and OpenSearch to be started and stopped.

See Download - Virtimo Fileserver

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

See also Add additional organizations/roles/rights and other data to the user session

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

See also sourceCommonTableExpressionQuery in Replication

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

See also API documentation: Log Service API

In the OpenSearch log, there are many logs such as "QueryGroup _id can’t be null, It should be set before accessing it." This is a known bug in OpenSearch that was introduced with version 2.18.0. We have reduced the output as much as we could from our side.

Note: If users already have existing installations of the default instance (BPC Default Reports) in the Analysis Module, it is recommended to set the chart background color to full transparency (RGBA alpha value: 0) under Chart Configuration → Settings → Background Color. This improves visualization when used with the Dark Theme.

The setting Common Table Expression Query 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 the backups.

If the HTTP proxy used an HTTP/2 connection, the pseudo-header ":status" was forwarded to the client. This leads to an error if interpreted strictly. For example, in this case, nginx reported a 502 Bad Gateway error to the client.

Different loading times of plugins led to a deviating order. Now, regardless of loading time, the order from the configuration is maintained.

If a deployment was carried out 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 was fixed that prevented instance-specific HTML content editing rights from being granted via the role htmlcontent_editor_<MODULE-ID>.

If an editor field was displayed in a popup window, the initial value of the field was shown in this window. Previous changes made by the user were ignored.

If an element with sub-elements was created in the navigation, short pauses could occur in the application if a sub-element pointed to the same module as the element above it.

Update OpenSearch according to the update guide

For the hardening of the TLS settings, properties were set in 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 supplemented with the following entry:

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

When using a bpc.env, it is recommended to update it. If not already present, the file custom.java.security should be added. The following must be added for this purpose.

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 of the filter settings is displayed. With AND, only data that meets all filter settings is displayed.

See also Restrict visibility of monitor data

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

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

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>_<InstanceId>_<SettingName>

If it is a setting of a module and not of an instance/component, then the value noinstance is to be used for <InstanceId>. You can find 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 in the Core_IndexTemplates setting to 1. This is also the default setting that Elasticsearch/OpenSearch has been using for new indexes for a few years. This only affects newly created indices. Indices that have already been created are not affected.

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

By optimizing access to the OpenSearch Backup API, fewer accesses to the data storage are performed. This reduces the corresponding costs, for example, when using Amazon S3.

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

Performance increased and heap memory usage reduced. Java has to perform significantly fewer garbage collector calls. This is especially true when the log levels for the BPC packages are set to their default (WARN). This affects 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 arrange the order according to your own criteria.

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

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

When using a bpc.env, it is recommended to update it. If not already present, the file custom.java.security should be added. The following must be added for this purpose.

See also Central configuration file

The file name of the license can 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 at the same time.

When using dark themes, charts now apply a dark theme-compatible styling.

The loading of the BPC configuration in the client is accelerated by the change.

For the hardening of the TLS settings, properties were set in 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 supplemented 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 because several BPCs may be installed on the server, the appropriate session cookie is now taken into account.

In cases with frequent changes to the data, 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 manually reloaded.

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

The page Develop BPC module has been translated into German.

See BPC Cluster

The documentation Chart Editor has been updated to provide clarity regarding the necessary configuration of data types on the axes and data series.

See Data Management installation and update

We used CXF version 3.5.4 in our previous Karaf releases. This CXF version provides Jackson in version 2.14.3. Now we ship Karaf with CXF 3.6.5, which provides Jackson in the version 2.17.2.

Please update the CXF version (3.6.5) in your pom.xml. And more important is to update also the used Jackson version (2.17.2). For this check if you have an Import-Package statement for it. This must be added or adjusted when you use Jackson functionality like the ObjectMapper class.

Replace

with

Update OpenSearch according to the update guide

New data in the "Frontend Log Monitor" monitor is now displayed directly or loaded subsequently.

In selected code editors (JSON, CSS, …​), you can now display the content in a popup window using the icon . This provides more 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: Develop BPC plugins

The interface for configuring and creating replication components has been standardized. It is now no longer possible to (de)activate individual replications directly in the list of replication components. This is now 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 generating deep links to monitors can now handle various query parameters to set appropriate filters in the monitor.

A deeplink to the audit log monitor can be retrieved via the Auditlog API.

In the bundle info, which can be accessed via the Karaf console, the time of the last change to the underlying source code is now displayed instead of the build time.

Forms in the detail view now receive changed data when the monitor reloads. To suppress this behavior—because the changes to the data may not be relevant for the form—the option ignoreUpdates can be set on the form in the detail configuration. See also: Configuration of the monitor detail views

AuditLog and LogService API documentation supplemented. See: APIs

The possible query parameters for the AuditLog and LogService API for opening a monitor via deeplink have been added to the documentation.

See APIs

Update OpenSearch according to the update guide

You can use the Log Service API to be redirected directly to the Log Service configuration or to connected monitors. There are two new LogService endpoints that redirect the user to the corresponding BPC pages when called:

See also API documentation: Log Service API

From IGUASU version 3.0.6, it is possible to jump directly from the BPC Flow Processor overview to the IGUASU processor. “Frontend URL” and “System ID” are now available in the Flow Manager. “URL” has been renamed to “Service URL.” Username and password are no longer required. Long descriptions of the processors are displayed in a shortened form, with the full text shown in the tooltip.

For some chart types, it is now possible to enable an export function.

See Chart Editor

Module developers must ensure that no additional parameters are specified in the Bundle-SymbolicName.

Incorrect: de.virtimo.bpc.module-id;blueprint.aries.xml-validation:=false

Correct: de.virtimo.bpc.module-id

The incorrect variant was included in earlier templates for BPC modules.

The behavior of validateOnChange has been adjusted so that validation is now only triggered when the user shifts focus elsewhere.

The order of the fields for configuring dashboards has been rearranged so that the most important parameters are at the top. In addition, more descriptive labels have been set.

If the available disk space falls below defined thresholds, shards are redistributed to other nodes. It can also happen that indices are set to read-only to prevent the disk from filling up.

The value of cluster.routing.allocation.disk.threshold_enabled is now true. This corresponds to the OpenSearch default value.

If the HTTP headers system.id and instance.id are set, the values are written into a new JSON object externalReference under the fields iguasuSystemId and iguasuInstanceId.

The function setProperty - Set the value of a variable is now available.

Fields that contain nested JSON objects receive "formatter": "jsonStringify" in the initial column configuration. This converts the contents into text and displays them in the monitor.

The browser function JSON.stringify is now available as an ExtJS format function.

This allows it to be easily used in various places to convert JSON into text.

The print dialog can now be triggered externally.

A bug was fixed that caused individual replication jobs not to be correctly distributed across all available nodes when changes were made to the nodes in the BPC cluster.

Both URL configurations must be filled in to enable the jump to the processor (e.g., in IGUASU)

Although the OpenSearch connection was configured with http, an attempt was made to establish the TLS context based on the configuration. However, if this configuration was incorrect, an error occurred.

The configuration is now ignored, as it is not relevant for http connections.

Nevertheless, it is recommended to use secure connections at this point.

An application area can now only be switched if it is not empty and the user has permission to view the contents of the application area.

It is now possible again to use value to set the content of the HTML components.

A dedicated prefix is now used for the values in LocalStorage. As a result, the contents of other applications are not deleted.

There were various problems when the time zone of the "last update column" in the database table is set to UTC: - The tail sync did not always delete all records. - Instead, it updated all records on each run. - The interaction with replication also became confused.

If several deployment files were placed in karaf/deploy, not all of them were sometimes processed. The cause was the automatic backup of the existing configuration. The names of the backups are now unique to the millisecond.

The error in the ExtJS framework was fixed by an override.

At Sencha, the issue is tracked under EXTJS-29685.

The documentation for configuring secure network connections has been revised.

See in particular Secure connection (TLS/HTTPS)

Update OpenSearch according to the update guide

The mode for notifications about feedback from process starters and actions can be set in the “Function_ProcessNotificationDisplayMode” (“function_processNotificationDisplayMode”) setting: Toast: Short overlay PopUp: Window that must be confirmed Silent: No visual notification (notification appears in the list when you click on the bell at the top right) See also: Configuration of Process Monitoring

The setting applies to all processes (process starters and actions), but not to status changes. In “Function_ProcessStarterConfig”, the notificationDisplayMode can be changed for individual processes (toast, popup, or silent). (Case sensitivity does not matter) See also: Process Starter

A dark theme is available for the BPC. It can be downloaded from the download page.

To switch between installed themes, you can use, for example, the plugin Theme Switcher.

The dynamicList filter with "queryMode": "remote" is now case-insensitive

Via the context menu in the monitor, it is now possible to change the sorting of the grouping.

The HTTP status codes for responses to the REST API have been documented in greater detail. See: APIs

The core now automatically searches for a configuration for indices that are to be created and managed.

See also Creating indices