What's new?
See what new features and improvements are available in IBM Industry Solutions Workbench 4.1.0.
Java Spring Boot Stack 2.0
From version 4.1.0 on, IBM Industry Solutions Workbench Java Spring Boot Stack 2.0 is available. This stack is based on Java 17 and Spring Boot 3 version.
Saga Support for distributed transactions
From version 4.1.0 on, IBM Industry Solutions Workbench offers the Extension Saga Pattern Support for transactional use cases. It allows you to implement distributed transactions across multiple services by applying the Saga pattern. IBM Industry Solutions Workbench provides rich modelling and implementation support for such use cases, while establishing a secure connection to the lra-coordinator by default.
Read more about Saga Pattern Support.
IBM Business Automation Workflow integration
With version 4.1.0, the integration of the generated toolkits for IBM Business Automation Workflow integration has improved. It is now easier, to set configurations like the endpoint URL, SSL configurations or request and response timouts when using the generated toolkit.
Please check the related section in Modelling APIs for more details.
Branching Support
With the current version of IBM Industry Solutions Workbench, the Solution Designer and the CLI fully support branches of the projects. Now the user is able to create and/or checkout a remote branch from the repository, reset the local branch to the remote status or delete dedicated branches. Also, pipeline configurations can be created for a dedicated branch.
Read more about the new capabilities.
Other noteworthy improvements
Solution Hub now displays ARGO CD
For all deployed Application Composition Project you can now access the most important information directly in the Solution Hub. Either the overview of the deployed applications or a dedicated page for each application allow to simply check the status.
Read more about the displayed information.
Share your workspace with co-workers
You now simply can share your workspace with co-workers by simply handing over a token. Co-workers then easily create the same setup based on that token and later also can synchronize with the source workspace.
Read more about the sharing of a workspace.