Runtime S20.5.x

You can find below the major changes and improvements of the Stambia DI Runtime 2020 (S20.5.x) version.

This article only highlights the most important changes.

If you need further information, please consult the full changelog and/or reference documentation.

 

Prerequisites

Migration from S17

Stambia DI Runtime 2020 (S20) major version changes some important part of the software which require your attention.

Migrating from Stambia DI Designer S17, S18 or S19 require to follow the migration guide, which can be found in the following article.

If you are simply updating from another Stambia DI Runtime 2020 (S20) version, simply follow the minor version upgrade guide, as usual.

 

What's new in Stambia DI Runtime 2021 (S20.5.1)?

JSON reading decode

When reading JSON data, the unicode character such as "\u0000" is no longer interpreted/decoded to avoid issue during the reading.

However the JSON writing keep encoding some forbidden characters.

This version embeds also some fixes issues. Have a look at the Changelog for further information.

 

What's new in Stambia DI Runtime 2021 (S20.5.0)?

Process Actions improvements

Concat Files

Append Line Separator

When using append mode, a new additional parameter named "Append Line Separator" has been added to specify if a separator should be added or not before appending the new data.

Refer to this article for further information.

 

Sort Order

A new parameter has been added "Sort Order" to choose in which order the files should be processed.

Until now, depending on the operating system, the files might be listed in different order, and not always alphabetically.

Refer to this article for further information.

 

Other improvements

Multi Configurations Web Services Deliveries

When working with multi-Configuration Deliveries, you can usually choose which configuration to use at execution, using the dedicated parameters for that.

However, when publishing a multi-Configuration Delivery as web service, it was currently not possible to choose the configuration when trying to invoke it, producing such response message:

"You have to set configuration code on externalized deliveries, available code: INT_001 INT_002"

 

Therefore, we added a new HTTP Header which can be passed alongside the invocation request to choose the Configuration that should be used for the invocation:

X-Delivery-Configuration-Name

 

Example with Postman:

 

When working with multi-Configuration Deliveries, you can use this HTTP Header to define the Configuration to use.

Note that this HTTP Header is ignored when invoking a standard Delivery.

 

Uberize the runtime

We provide a new command to create a JAR shipping a configured runtime containing all its deliveries.

This command transforms the runtime to one jar with deliveries and module and properties inside the jar.

The generated JAR is executable using ‘java -jar fileName’.

The first version works with start delivery only.

Refer to this article for more information.

 

Minor improvements and fixed issues

This version also contains some other minor improvements and fixed issues, which can be found in the complete changelog.