Developer-Changelog

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.

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

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.

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

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

See Develop BPC module and Module and module instance settings

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

Revised instructions. See Develop BPC module

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

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

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.

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

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

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.

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

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

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.

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 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 format function.

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

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

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

Paths in themes should now always be specified as absolute.

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

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

See also: Develop BPC theme

See Develop BPC theme

It is now possible to specify references to external resources when writing audit information. For example, it is possible to refer to the IGUASU instance that created the entry.

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

For instance types, labels 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 composed as follows: "CORE_<MODULE_ID>_INSTANCE_TYPE_<INSTANCE_TYPE>" or, for example: "CORE_BACKENDCONNECTION_INSTANCE_TYPE_HTTP_PROXY": "HTTP Proxy"

The documentation has been updated to include information about the dependency on "theme-triton" for custom CSS in custom frontend modules.

Develop BPC module

Only relevant for module developers When using the BPC JsonEditor (xtype bpcJsonField or bpcCodeEditorWindow.json), the optional JSON schema is now passed via schema and no longer via jsonSchema.

Only relevant for module developers When using the BPC JsonEditor (xtype bpcJsonField or bpcCodeEditorWindow.json), the optional JSON schema is now passed via schema and no longer via jsonSchema.

See HTML Sanitizing and the setting sanitzeHTML

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

Only relevant for BPC module developers

BPC modules previously obtained the ExtJS framework either via our own NPM repository or it had to be provided separately. Now, ExtJS can be obtained directly from Bitbucket via npm. For this, 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]" must be set in the package.json. It should be noted that the part at the end #c728d7e2 corresponds to a GIT commit ID. This should be chosen so that it matches 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 shown that npm does not consider newer commits in this case when updating.

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

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

BPC modules can now react to restored indices via events.

See also Backup of indices

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

See also Creating indices

See also Creating indices