This release contains a number of bug fixes primarily relating to:

• Documentation for Duplicate Batch, KPI Management, Web Interface, Ultra, SAP RFC, Database Profile, JWT APL function, Kafka, Pico, SAP CC and License

• SAP RFC

• SAP CC

• Ultra

• Aggregation

• Open API Profile

• HTTP/2

• Database Profile

but also in various other areas, see Bug Fixes for more details.

Please check out the Release Information here for more details: Release Notes 8.3.

To obtain your release, please, post a support case with a request in our https://digitalroute.my.site.com/s/.

💛

During the last quarter, we have released the following new capabilities; enhanced SAP Subscription Billing Forwarder, and Stream Groups. We also made some updates that could affect existing streams, see Important information for details.

SAP Subscription Billing forwarder enhancement

DigitalRoute's pre-integrated library for the SAP ecosystem has been a valuable tool for processing usage data to the Subscription Billing (SB) platform and to streams in Usage Engine Cloud Edition. The enhanced forwarder function for SAP Subscription Billing represents a significant improvement by leveraging the Batch Upload API to optimize the performance and reduce the overhead associated with large-scale data transmissions.

Additional capabilities

• Response handling - Once the usage data batch is sent to the SB platform, the forwarder can capture every API response sent back from the SB platform and route them to a subsequent stream. This response handling mechanism allows the system to track the status of each usage data batch post-transmission which is crucial for businesses to ensure accurate billing or trigger additional actions based on the processing state.

• Retry on fail - If a batch fails to upload due to a server issue, such as a 5xx server error or a network timeout, the forwarder can be configured to retry the request automatically. This reduces the need for manual intervention and enhances the overall reliability of the data transmission process.

Stream groups

When working with multiple data streams, there are often dependencies between them that require careful coordination. Stream groups offer an efficient way to manage these dependencies by allowing you to run or schedule two or more streams in a specific sequence. With the enhancements for stream groups, the Stream groups page has been improved to make it more intuitive.

You can now edit a stream group, so streams can be added or removed from a group without having to delete and re-create the entire group.

Streams in a stream group can now be viewed individually in the Streams View, with a new Group column showing which stream group the stream is a member of. You can still view the streams as a stream group in the Stream Groups page.

A new Configuration column has also been added to show whether streams are valid, or if they have configuration issues that need to be resolved before they can be run or scheduled.

Display options have been added in both the Streams and Stream groups pages, so you can select which columns you want to see.

Important information

In Q3, we introduced three changes that may have impacted your existing streams. As a result, some of your streams may need to be adjusted before they can be executed.

Improved stream validation

We have added additional validation to streams. Previously, any function with multiple outputs, like Route or Deduplicate, could have one or more disconnected outputs. This has been improved with a new validation rule that flags streams with functions that have one or more unlinked outputs as invalid. These streams will be flagged as invalid until you fix them by linking unlinked outputs to another function. See Validation in https://infozone.atlassian.net/wiki/x/gOF3 for more details.

Fast XML- parser code update in the Script function

We have updated the fast-xml-parser used in the Script function to align with the latest changes in the JS npm Library. If your streams use this package in the Script function, it is important to update the code to the latest version. You can find an updated example here: https://infozone.atlassian.net/wiki/x/UYd4.

Validation added to Field organizer function

We have introduced new validation to the Field organizer function, ensuring that the Source and Target fields in the configuration are populated with at least one character. Previously, blank fields could be passed to downstream functions, but empty fields are now no longer permitted. You must remove any empty fields from your Field organizer functions to make your configurations valid. For more information, see https://infozone.atlassian.net/wiki/x/sPl3

🌟

We hope you enjoy these new enhancements. As always, we appreciate your feedback. If you have any questions or concerns, please do not hesitate to reach out to us through our Self Service Portal.

This release contains several bug fixes relating to:

• Access Control

• Aggregation

• APL

• Core

• Desktop Launcher

• Devkit

• Documentation

• Jackson

• JSON Decoder

• Liquibase

• Merge Files Collection

• MZ Installation

• Pico Management

• MZSH

• SAP RFC Profile

• SSO

• Swing Desktop

• Ultra

• Upgrade

• Vaadin

• Workflow Bridge

among other things. SeeBug Fixes for more details.

Please check out the Release Information here for more details: MediationZone 9.2 Release

The release can be accessed from InfoZone: Release Information