What's new?

In this release, we re-designed the integration namespaces in order to make it easier to work with and to reduce the amount of mapping effort while implementation.

Therefore, the SDK now provides access to the auto-generated methods to call external APIs from every type of namespace. This means, you can now call an operation of an external REST API directly from within your API namespace or domain namespace. Before, this was only possible within integration namespaces and with the use of integration services. This also required a lot of mapping attributes which is now unnecessary.

In case you build an API that only loads data from an external source and provides it as the response, you can directly call this operation on your own API's operation. If you need to do aggregation or some more complex processing of the data, you can do this within a domain namespace by directly calling the operation there.

This is especially saving time when integrating with other microservices built with IBM Financial Services Workbench when you can provide the external source's API specification.

If you want to integrate external APIs that don't provide an API specification you can still model integration services as before in order to provide self-written operation calls to those external sources.

Read more about integration namespaces.

This tech preview version of IBM Financial Services Workbench also includes a new persistence mechanism to create, read, update and delete root entities, entities and external entities from and to a relational database. This is only available for low-code projects based on Java Spring Boot.

You can find detailed information on this feature in the tech preview overview.

APIs built within a low-code service project offer an option to add annotations to be used with IBM API Connect. This allows you to add special labels to the auto-generated API specification in order to use the API management capabilities of IBM API Connect.

Read more about the support for IBM API Connect.

We re-designed all overview pages, namespace pages, CI/CD pages and the Admin/User Settings page to align with IBM Carbon Design. Also, we moved the most important content of each namespace to the first tab of a namespace's overview page (e.g., APIs: operations, Domains: entities, Integrations: API dependencies).