| Version | Date Released | Features & Enhancements | Resolved Issues | Downloads |
|---|---|---|---|---|
| 24.02 | 15 February 2024 | ✓ | ✓ | ✓ |
Overview
The 2024 Springboard Winter release, also known as the 24.02 release, is primarily an upgrade of Springboard services, libraries, forms, and Workspaces to be compatible with the 23.04 release of Temenos Journey Manager (TJM) and Journey SDK (where Jakarta EE replaces Java EE; see below), Journey Maestro, and Journey Workspaces.
Solution versions
- Retail DAO 24.2.0
- Lending with LMS 24.2.0
- SMB DAO 24.2.0
Upgrades
All three solutions received the same upgrades.
- Journey Manager 23.04.2
- Journey SDK 23.03
- Journey Maestro 23.04.2
- Journey Workspaces 23.04
Jakarta EE
As mentioned in the Journey SDK 23.04 release notes, Jakarta EE 10 replaced Java EE. This is a requirement for WildFly and affects all Groovy services within TJM for customers upgrading to TJM 23.04. It's important to become familiar with the Jakarta changes, whether upgrading an existing implementation to 23.04 or deploying a new implementation. For further information, see the Journey SDK 23.04 release notes.
All Springboard Groovy services in Retail DAO 24.02, Lending with LMS 24.02, and SMB DAO 24.02 have been upgraded to use Jakarta packages and don’t need extra Jakarta transformation.
However, if your team has custom services, Security manager scripts, or Exchange services that need to be updated to use Jakarta packages, TJM 23.04 comes with some pre-installed solutions:
- Execute the Jakarta Transformer service from the TJM 23.04 console.
- Execute the Jakarta Transformer service as a scheduled job.
- Transform multiple services to use Jakarta packages. TJM 23.04.2 comes with a deployment property called Enable transforming javax to Jakarta in System > Deployment Properties which is disabled by default.
To update old Javax references of a single service to use Jakarta packages:
- Login to Journey Manager as an administrator.
- Select System > Deployment Properties.
- Select the option Enable transforming javax to Jakarta.
- Export the individual service that needs a Jakarta update.
- Import the service you just exported.
- Repeat steps 4 and 5 for each service you need to update.
- Once services are imported, disable the deployment property Enable transforming javax to Jakarta so that other imports or Jenkins deployment performances are not impacted.
As always, it is advised to back up services and perform these steps in lower environments first. For more information, see Migrate to Jakarta EE.
Documentation
- Updated and improved documentation is available on the TJM documentation website.
- Updated documentation for partners is available to download from the Springboard downloads area.