Changelog

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

The configured limit (max. number of records) for XLSX is now taken into account again when exporting data via 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

For GUI modules that offer types, components with types can once again be created. 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 "Users" section on the "BPC Administration" documentation page is described in more 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

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 expanded.

See Chart Editor

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.

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

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

Make sure 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 the wrong process starter was displayed when exactly two process starters were configured, one of which is hidden.

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 clearer text labels.

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 this option did not work because the value must be enclosed in quotation marks. The Windows version was not affected.

A bug has been fixed 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 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 adjusted 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 provided. (In this case, it would be better to store a fixed BPC API key within the INUBIT process.)

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 no longer returns OpenSearch internal indexes. These are all indexes named with a . 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 used on buttons to reduce the arrow spacing.

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

The mouse pointer now appears over checkboxes and radio groups in a way that clearly indicates You can change their 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.

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 store a fixed BPC API key within the INUBIT process.)

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

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

Views are correctly marked as modified 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.

Fixed an issue 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’s table layout has been improved*,* and the likelihood of errors has been reduced.

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

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

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 option for grouping settings is now enabled by default. It is recommended to use this view, as it displays the settings in a common context.

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

You can now configure the preselection of a value for the process status change. The preselection is controlled by 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.

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.

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

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

See also Module and Module Instance Settings

See Core Services and Create-Index-related BPC settings

In the HTML editor, "Expired copy of the Froala Editor" might have been displayed.

ID columns are now set via combo boxes in the Log Service configuration interface. The configuration can only be saved if at least one ID column is defined. Additionally, the system checks whether all ID columns are included in the field configuration. If this is not the case, the form is marked as invalid and saving is prevented.

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 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—which happened when multiple grids were disabled—has been fixed.

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

A bug was 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 monitorView.

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

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

Dashboard widgets now only display the configuration icon 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 via alternative methods (e.g., via the widget header).

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 translate Labels for all components, including those 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, a bug was fixed that caused setFormState to remove bindings, resulting in the submit after setFormState containing only data from before setFormState. In addition, 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 authorized 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 via alternative methods (e.g., via the widget header).

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. Additionally, error messages are now displayed in the event of an error.

Rows in the Navigation Settings are now highlighted in alternating colors to improve readability.

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

The ProcessStarter 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, the Administration Changelog displays an overview of all versions in which a change to the 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 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 the 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

The LogService endpoint for opening a monitor now also supports scenarios where there are multiple monitors for a single 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 dark theme without a white background, the chart background color should be set to full transparency (RGBA alpha value set to 0) under Chart Configuration → Settings → Background Color.

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, in this case, nginx reported a 502 Bad Gateway error to the client.

Varying plugin load times resulted in an incorrect 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 was fixed that prevented instance-specific HTML content editing permissions from being granted by the role htmlcontent_editor_<MODUL-ID>.

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 have been set in the custom.java.security

If you are not yet using an ` 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 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 this, add the following:

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 criteria is displayed.

See also Restrict Visibility of Monitor Data

The JVM security.properties settings can now be configured (e.g., DNS cache TTL for cloud environments; see link). To do this, the entry in bpc.env.sh/BPC.env.cmd must be configured as follows:

export EXTRA_JAVA_OPTS="-Djava.security.properties=../custom.java.security"

 SET EXTRA_JAVA_OPTS=-Djava.security.properties=..\custom.java.security

Additionally, the custom.java.security file must be downloaded.

You can find the file in the download section at Download - Virtimo File Server.

More information at: Central configuration file

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 `, which contains 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 a few years now. This only affects newly created indices. Existing indices are not affected.

By optimizing accesses to the OpenSearch Backup API, fewer accesses are made 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.

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 the 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 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.

This change speeds up the loading of the BPC configuration in 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 substituted 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 involving 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 reloaded manually.

Filters at the top of the monitor columns are now displayed correctly again.

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 on the 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 Jackson version 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 adjusted 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"are now displayed or reloaded immediately.

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 LogService API for creating deep links 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 available query parameters for the AuditLog and LogService APIs used to open a monitor via deep link have been added to the documentation.

See BPC API

Update OpenSearch according to the update instructions

Starting with IGUASU version 3.0.6, you can now 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 abbreviated form, with the full text available in a tooltip.

For some diagram 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 version was included in earlier templates for BPC modules.

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

If free disk space falls below defined thresholds, shards are distributed to other nodes. It may 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 to a new JSON object named externalReference under the fields iguasuSystemId and iguasuInstanceId.

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

Fields containing nested JSON objects receive the following in the initial column configuration: "formatter" : "jsonStringify". This converts the contents to text and displays them in the monitor.

The browser function https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify][JSON.stringify] is now available as an ExtJS formatting function.

This makes it easy to use in various places to convert JSON to text.

The print dialog can now be triggered from outside.

A bug has been fixed that caused individual replication jobs to not be distributed correctly 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 to use HTTP, attempts were 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 in this context.

An application area can only be switched to if it is not empty and the user has permission to view the application area’s content

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

A dedicated prefix is now used for values in LocalStorage. This ensures that content from other applications is not deleted.

There were various issues when the time zone of the "Last Updated" column in the database table was set to UTC: - Tail Sync did not always delete all records. - Instead, it updated all records on every run. - Interaction with replication was also disrupted.

If multiple deployment files were stored in the karaf/deploy, not all of them were processed in some cases. The cause was the automatic backup of the existing configuration. The names of the backups are now unique down to the millisecond.

The bug in the ExtJS framework was fixed via an override.

Sencha is tracking the issue at EXTJS-29685.

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

The documentation on configuring secure network connections has been revised.

See in particular Secure Connection (TLS/HTTPS)

See Developing Button Types Provided by BPC

Update OpenSearch according to the update instructions

The mode for notifications regarding confirmations from process starters and actions can be set in the “Function_ProcessNotificationDisplayMode” (“function_processNotificationDisplayMode”): Toast: Brief on-screen notification PopUp: Window that requires confirmation Silent: No visual notification (notification appears in the list when you click the bell in the upper right corner) See also: Configuring Process Monitoring

The setting applies to all processes (process starters and actions), but not for status changes. In “Function_ProcessStarterConfig,” the notificationDisplayMode can be changed for individual processes (toast, popup, or silent). (Uppercase and lowercase letters do 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 the plugin Theme Switcher, for example.

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

You can now change the sorting order of the groups via the context menu in the monitor.

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

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

See also Creating Indexes

Some plugins in the Monitor module header were displayed with an incorrect background color.

Paths in themes should now always be specified as absolute paths.

Correct: $CompanyIcon: "/bpc-theme-customer/resources/images/favicon.png"

Incorrect: $CompanyIcon: "../resources/images/favicon.png"

See also: Developing a BPC Theme

When impersonating other users, the language can no longer be changed in the impersonated user’s Keycloak profile. For this to work, Keycloak must be correctly configured to ensure that Impersonator information is provided via an active scope.

The configuration grid_showHeader is obsolete because it causes errors. The header’s behavior has been controlled for some time now using the Parameter moduleHeader_enabled. This setting will be automatically removed during the BPC update.

See Network

See also:

See Creating Indexes

Karaf access via SSH is described in greater detail, and useful notes have been added.

The following documentation pages have been updated.

See OpenSearch

The dashboard documentation has been expanded to include the layout (columns and table).

See Configuring the Process Dashboard and Customize the Dashboard View.

Documentation has been added on how to create custom loggers.

The following documentation pages have been updated: Logging

See Karaf Console Commands Cheat Sheet

See Developing a BPC Theme

Update OpenSearch according to the update instructions

When loading the BPC, the version number of the Core Common Package (Fe-Core) is determined and stored in Local Storage. If this version number differs from the one saved during the previous load, Local Storage is reset.

An endpoint for sending events has been provided See also: Event API

It is now possible to include references to external resources when writing audit information. For example, this allows you to reference the IGUASU instance that generated the entry.

Date format setting added. See also Monitor Widgets for the Dashboard

The large number of subpages has now been largely divided between "Processes" and "Data View."

See Developing a BPC Theme

Labels for instance types can be defined using language keys. The language key is composed as follows: "<MODULE_ID>_INSTANCE_TYPE_<INSTANCE_TYPE>" The language key for core modules is structured as follows: "_CORE__<MODULE_ID>_INSTANCE_TYPE_<INSTANCE_TYPE>" or, for example: "CORE_BACKENDCONNECTION_INSTANCE_TYPE_HTTP_PROXY": "HTTP Proxy"

It is now possible to replace the "User Account Menu" with an avatar. This is a circular display of the user’s initials or, if configured correctly, an image stored with the identity provider. See also User Account Menu

See System Monitoring (Metrics for Prometheus)

Instance-specific roles for editing can now be assigned for the HTML Content Module: htmlcontent_editor_<MODUL_ID> See also: HTML Content Module (User-Defined Content)

See Submit - Form Submission

Documentation updated at Monitor Widgets for the Dashboard.

JSESSIONID cookie has been disabled

Fixed: An issue where the list of available filters was displayed as empty even though a selection should have been present.

Information regarding the dependency on "theme-triton" for custom CSS in custom front-end modules has been added to the documentation.

Developing a BPC Module

On the page Configuring Process Monitoring, the settings function_gridMultipleViews and function_gridMultipleViewsConfig now correctly link to Configuring Multiple Grids/Views.

Update OpenSearch according to the update instructions

The Process Dashboard has a new layout setting that allows you to switch between a column and a table layout

If an IP pinning error occurs, you can now log in normally after reloading the page in your browser. The error will not be displayed again (unless the IP address changes again).

Split View in Process Monitoring can now be displayed automatically upon opening by setting DetailView_EastInitialShow to true. (DetailView_East must also be set to true) Configuring Process Monitoring

When switching organizations, you can now configure the system so that the user is redirected to their home page instead of remaining on the current page.

See also Switching the Active Organization

The Storage API now returns an empty result set when querying content for stores that have not yet been created.

See also: Storage API

In the drop-down list for the organization change, you can now configure the system to display already active organizations as deactivated items.

See also Switching the Active Organization

Names of configuration parameters in Log Service corrected.

In recent Karaf versions, Karaf-specific environment variables for setting JVM memory have been removed and must be replaced with an alternative.

Linux

Please replace `

` with ` bpc.env.sh

` and adjust the values accordingly.

Windows

Please replace bpc.env.cmd

with

in the file and adjust the values accordingly.

See also Central configuration file and Karaf

When the navigation bar is collapsed, the icon no longer shifts to the left if there is a submenu

In current Karaf versions, Karaf-specific environment variables for setting the JVM memory have been removed and must be replaced with an alternative.

Linux

Please replace `

` with ` bpc.env.sh

` and adjust the values accordingly.

Windows

Please replace bpc.env.cmd

with

and adjust the values accordingly.

See also Central configuration file and Karaf

Added appropriate icons next to titles for various notification types Titles for notifications adjusted based on notification type

Empty values in a combo box are no longer displayed as

Components are now automatically centered when inserted into the Application Toolbar. This affects, among other things, HTML Content Plugins that use the Global Application Toolbar left/right hook. As a result, components that have padding and margins defined on only one side are no longer centered. For these elements, padding and margins can now be set to 0.

It is now possible to download an SBOM file for each module via the GUI or API.

When uploading modules, the system now checks whether a potentially affected module can actually be updated via an upload. If this is not the case, the download is rejected.

Additionally, the system prevents modules from being deployed multiple times simultaneously if different filenames are used during the upload.

The BPC Bundle now contains additional content. For details, see Download - Virtimo File Server

Only numeric environment variables in BPC.env.cmd may be set using SET /a. The parameter /a has been removed from the template and examples for non-numeric values.

"Required" and "readOnly" can now also be bound to a container or fieldset, just like "hidden" and "disabled." See Examples.

curl Examples for calling OpenSearch have been updated to include username and password. See also Migration from BPC 4.0 to BPC 4.1 and Troubleshooting

Data binding within forms has been revised. Combining multiple data bindings now requires an operator such as +.For more information: Binding Form Component Attributes

Update OpenSearch according to the update instructions

Adjustment of the "About" icon (from circle to square)

It is recommended to move customized keystore and truststore files out of the Karaf and OpenSearch folders.

More info at: core:/admin/configuration/bpc_env.adoc#keystore_truststore

The BPC cookie name can now be set in the [karaf]/etc/de.virtimo.bpc.core.cfg using the property de.virtimo.bpc.core.cookieName (also via bpc.env.sh). The default is still BPC_J_S.

See also BPC Configuration File

BPC modules can now respond to restored indexes via events.

See also Backing up indices

If a managed index was deleted during or shortly before a write operation, it was automatically recreated. However, the general index configuration was not taken into account. This behavior is now avoided.

See also Creating Indexes

Data binding within forms has been revised. Combining multiple data bindings now requires an operator such as +. For more information: Binding Form Component Attributes

Due to an interaction with the PAX JDBC Feature Installer, BPC might not start correctly after a Karaf update.

When starting Karaf with plaintext passwords in users.properties, a " java.lang.IllegalArgumentException: Detected a Non-hex character at 1 or 2 position " error could occur.

See Configuring the Monitor Data Export and Configuring Process Monitoring

See also Creating Indexes

Update OpenSearch according to the update instructions

Karaf logs are now provided via a monitor (see also Karaf Log).

The additional component 'Decanter' is used to write Karaf logs to the OpenSearch index bpc-logs. In a new Karaf installation, this component is already pre-installed and no action is required. If an existing Karaf installation cannot or should not be replaced, it can also be installed later via the Karaf console (Internet connection required).

For configuration instructions, see Karaf Log.

As a result of this change, the use of Java 17 is now mandatory, and support for Java 11 has ended.

Karaf must be updated with this update.

A "Watchdog" module is now available at Download - Virtimo File Server. This module monitors the core application (Core module) and attempts to start it if necessary. This is only relevant in scenarios where it is possible that Karaf is started at a time when a connection to OpenSearch is not yet possible. The Core module attempts to establish a connection for approximately 90 seconds and then enters an error state from which it cannot recover on its own. The Watchdog ensures that a restart is performed regularly thereafter, or that an attempt is made to establish an OpenSearch connection.

Karaf logs are now made available via a monitor (see also Karaf Log).

The additional component 'Decanter' is used to write Karaf logs to the OpenSearch index bpc-logs. In a new Karaf installation, this component is already preinstalled and no action is required. If an existing Karaf installation cannot or should not be replaced, it can also be installed later via the Karaf console (internet connection required).

For configuration instructions, see Karaf Log.

New status endpoint for querying the role of individual nodes in cluster operation. This endpoint can now be used to check whether a node has the "Leader" role or not. See also BPC API /cxf/bpc-core/status/clustermaster

A new "anyMatch" parameter allows you to filter options differently in combo boxes. See Process Starter.

As a result of this change, the use of Java 17 is now mandatory, and support for Java 11 has ended.

Relevant only for BPC module developers

Previously, BPC modules either obtained the ExtJS framework from our own NPM repository or it had to be provided separately. Now, ExtJS can be obtained directly from Bitbucket via npm. To do this, set the dependency "@virtimo/sencha-extjs-sdk": "git+ssh://git@bitbucket.org/virtimo/sencha-extjs-sdk#c728d7e2 [git+ssh://git@bitbucket.org/virtimo/sencha-extjs-sdk#c728d7e2]" in the package.json file. Note that the part at the end, #c728d7e2 `, corresponds to a Git commit ID. This should be chosen to match the current branch or BPC version. `c728d7e2 corresponds to the current BPC 4.1 branch "support/4.1.x". Alternatively, you can also specify the branch name. However, this is not recommended, as it has been observed that npm does not take newer commits into account during an update in this case.

After adding the dependency, the path to the ExtJS framework can be set in the file workspace.json as follows:

A directory or symlink named "ext" is no longer necessary.

The selection options in the Export Monitor are now consistently implemented using radio groups, and the labels have been improved.

The status page now provides a clearer description when a configured base URL is involved.

The filter for licenses in "About BPC" now works

Objects for values in instance settings no longer prevent existing instances from loading or new instances of a module from being created

The emojis in the Froala Editor have been removed. You can still use the emojis from your keyboard or operating system.

Karaf must be updated with this update.

An update of the OpenSearch plugin (os-BPC-plugin).

During deployment, content provided by modules in the Storage Service can now be deployed selectively. This applies, for example, to monitor views.

It is now possible to use the “print” action within a form, which opens the print preview and thus enables the creation of a PDF file. See Print - Print the form as a PDF.

See Log Service API

See Log Service API

An update to the OpenSearch plugin (os-BPC-plugin) is required.

"null" values in combo box lists are displayed more clearly

In existing installations, the file bpc-be-dashboard.jar can be omitted entirely and deleted from the KARAF/deploy directory. The Dashboard module now consists solely of the file bpc-fe-dashboard.war.

As of de.virtimo.bpc.module.monitor.api.service.MonitorService, it is now possible to check via isAcccessible(…​) whether a user is authorized to access certain monitor functions.

Fixed a bug where navigation was no longer displayed due to an old configuration