Developer Changelog

The Storage API’s ` GET` endpoint can now also filter by ` value ` and ` customFields ` using the parameters ` query ` and ` filter . To filter by subfields, use dot-separated syntax: `value.name:Alicia filters entries where the name field in value has the value Alicia.

Since Storage indexes do not contain timestamp fields, the parameters timezoneOffset and timezoneName have been removed from the GET endpoint.

For BPC Module Developers If you use the ` StorageService class and its ` `getItems functions in your BPC modules, please note that these have been marked as deprecated and replaced with a variant that does not include the ` `timeZoneId` Parameter.

This change allows for better automated testing of tables in the GUI.

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

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

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

Code that was marked as deprecated has been removed from BPC.

The query string parameters gridId, gridExtId, multiRecords, buttonId, and the form parameter tablePrefix have been removed from process action requests. To send additional context or configuration information, "Process Action Metadata" can be configured in the monitor settings.

In process starters, the XML that was sent along with the request has been replaced by JSON. As a result, portletArchiveName, operation, mandant, gridID, key, bpcModule, bpcModuleInstanceId, and custom have been removed. key has been uniformly renamed to id. Additional context or configuration information can be reliably included by using the "metadata" configuration in the process starter settings within the monitor settings. The process parameters are grouped under config.parameters in the request payload. File uploads contain ` filename, ` `type `, and ` `data. Grids contain a list of their records. `

` For Change State, tablePrefix, mandant, and changeStatusBox_<Spaltenname> have been removed. command has been uniformly renamed to type and is assigned the value "statusChange". columnsstring has been renamed to column. newStatusCombo_<Spaltenname> has been renamed to newStatus. commentfield has been renamed to comment. childStatus is no longer set to "Info" by default in the Change State configuration and, if configured, is migrated to metadata. Additional information can be passed in the "metadata" object in the Change State configuration.

See also Migration from BPC 4.* to BPC 5.0 Configuring Process Actions Process Starter

The unused settings inubit_aperakEndPoint, inubit_dbGridId, and inubit_pmMandant have been removed. The settings inubit_actionEndpoint, inubit_changeStateEndpoint, and inubit_VpsEndpoint have been replaced by actionEndpointProcessor, changeStateEndpointProcessor, and vpsEndpointProcessor.

HTTP proxy backend Connections and flow Connections now always filter the session cookie so that a recipient cannot make requests in BPC within the user’s context. The setting ` filterSessionCookie ` is therefore no longer needed. Instead, the new setting ` sendSessionId ` allows you to include the user’s session ID, which can be verified at the endpoint ` GET /cxf/bpc-core/authentication/session/{sessionid} . When the " `injectUserSessionJWT " setting is enabled, a self-generated JWT is no longer sent; instead, the signed ID token from the OpenID Connect provider is sent. You can find more details in Backend Connections - HTTP Proxy.

Users of the Log Service API must replace all instances of childs with children in their POST data. During a transition period, childs can still be used for incoming requests. This backward compatibility will be removed in a future release. Please also note that the responses from the Log Service endpoints now contain children instead of childs.

This update requires updating Karaf.

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

You can use the LogService API to be redirected directly to the LogService configuration or to connected monitors. There are two new LogService endpoints for this purpose, which redirect the user to the corresponding BPC pages when called:

See also API documentation: Log Service API

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

A new setting has been added that allows you to select the endpoints or processors of Flow & Backend Connections. This selection generates a BPC URL following the schema BPC://<FLOW/backendconnection>/<instanceId>/<endpointOrProcessor>. There are separate settings for Process Actions, Process Starters, and Change State.

Validation results are now stored at state. This means they can also be used for binding, for example. See also validate

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

The 'link' type no longer exists for notifications; instead, all notifications can now specify links. The field linkData is used for this (previously typeSpecificData). The field url is still used for links to external websites; for internal BPC navigation, the hash component of the BPC URL is now specified in the field navigation. For more information, see Notification Types and the Notification API.

In the notification interface (BPC → Configuration → Overview → Notifications), you can now also configure a link (see Notifications to Users).

The query string parameters gridId, gridExtId, multiRecords, buttonId, and the form parameter tablePrefix have been removed from process action requests. To send additional context or configuration information, "Process Action Metadata" can be configured in the monitor settings.

In process starters, the XML that was sent along with the request has been replaced by JSON. As a result, portletArchiveName, operation, mandant, gridID, key, bpcModule, bpcModuleInstanceId, and custom have been removed. key has been uniformly renamed to id. Additional context or configuration information can be reliably included by using the "metadata" configuration in the process starter settings within the monitor settings. The process parameters can be found grouped under config.parameters in the request payload. File uploads contain ` filename, ` `type `, and ` `data. Grids contain a list of their records. `

` For "Change State," ` tablePrefix`, ` mandant , and ` `changeStatusBox_<Spaltenname> ` have been removed. ` command ` has been uniformly renamed to ` type ` and is assigned the value "statusChange." ` columnsstring ` has been renamed to column. newStatusCombo_<Spaltenname> has been renamed to newStatus. commentfield has been renamed to comment. childStatus is no longer set to "Info" by default in the Change State configuration and, if configured, will be migrated to metadata. Additional information can be passed in the "metadata" object in the Change State configuration.

See also Migration from BPC 4.* to BPC 5.0 Configuring Process Actions Process Starter

The unused settings inubit_aperakEndPoint, inubit_dbGridId, and inubit_pmMandant have been removed. The settings inubit_actionEndpoint, inubit_changeStateEndpoint, and inubit_VpsEndpoint have been replaced by actionEndpointProcessor, changeStateEndpointProcessor, and vpsEndpointProcessor.

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

For BPC module developers:

If feature/feature.xml is used in the module sources, please remove the following resource block from pom.xml:

This entry defined feature.xml as a resource and embedded it in the JAR file. This is not necessary.

However, you must still use the maven-resources-plugin to replace placeholders in the feature.xml.

To do this, add the following plugin call:

Users of the Log Service API must replace all instances of childs with children in their POST data. During a transition period, childs can still be used for incoming traffic. This backward compatibility will be removed in a future release. Please also note that the responses from the Log Service endpoints now contain children instead of childs.

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

HTTP proxy backend Connections and flow Connections now always filter the session cookie to prevent a recipient from making requests in the BPC within the user’s context. The setting ` filterSessionCookie ` is therefore no longer needed. Instead, the new setting ` sendSessionId ` allows you to include the user’s session ID, which can be verified at the endpoint ` GET /cxf/bpc-core/authentication/session/{sessionid} . When the " `injectUserSessionJWT " setting is enabled, a self-generated JWT is no longer sent; instead, the signed ID token from the OpenID Connect provider is sent. You can find more details in Backend Connections - HTTP Proxy.

The Core is no longer transpiled to legacy ECMAScript, and polyfills are no longer added. This enables support for newer language features. This means that ExtJS packages should also have the following content in their ` packages/local/PACKAGENAME/package.json ` file: