Workspaces release compatibility
WorkspacesThis topic relates to Journey Workspaces | Platform Developer | This feature was introduced in the 18.11 releaseThis feature was updated in the 22.10 release
Each Temenos Journey Manager (TJM) release includes compatible versions of Journey WorkspacesJourney Workspaces is a business portal designed to support resolution and customer service activities related to account opening and onboarding., Journey ManagerJourney Manager is a server application, deployed in the cloud or on-premise, that hosts forms, controls interaction with customers, calls on specialized services like identity verification or risk analysis and exchanges data with back office systems of record. (JM), and the Workspaces REST APIThe Workspaces REST API provides the integration with Journey Manager that Journey Workspaces needs.. For example, the Temenos Journey Manager 22.10 release includes Journey Workspaces 22.10, Journey Manager 22.10, and the Workspaces REST API packaged with Journey Manager 22.10.
By default, Workspaces is designed to be both forward- and backward-compatible with Journey Manager and the Workspaces REST API in all TJM product suite releases. Nevertheless, some incompatibilities may arise; where known, these are identified below.
To avoid any incompatibility issues, we strongly recommend using Workspaces, Journey Manager, and the Workspaces REST API from a single release of the TJM product suite.
If you have a specific need that requires deployment of Workspaces from one release with Journey Manager or Workspaces REST API from a different release, we strongly recommend not mixing Journey Manager and Workspaces REST API releases. This is because, it is highly likely that incompatibilities exist between Journey Manager and Workspaces REST API from different releases.
Generally, more recent Workspaces releases haven't been tested with older TJM product suite releases; in particular, recent Workspaces releases haven't been tested with TJM product suite releases that have reached end-of-life. While any combination of Workspaces, Journey Manager, and the Workspaces REST API from supported TJM product suite releases may be compatible, we recommend that you test any critical features when deploying a Workspaces release with Journey Manager or Workspaces REST API from a different TJM product suite release.
Supported releases
To learn about supported releases, see Temenos Journey Manager End-of-Life Policy.
Workspaces was not updated in the TJM 20.11 and TJM 21.05 releases.
Compatibility
The table below summarizes compatibility between supported Workspaces releases and Journey Manager and the Workspaces REST API included in supported TJM product suite releases. It is assumed that Journey Manager and Workspaces REST API are always from the same TJM product suite release. For example, if considering compatibility between Workspaces 21.11 and TJM 22.04, this is equivalent to considering compatibility between Workspaces 21.11, Journey Manager 22.04, and Workspaces REST API 22.04.
The table also identifies when the following release-related incompatibility issues are applicable. Additional detail about these incompatibility issues is available below.
- CSRF token issue: A TJM 21.05 or earlier environment upgraded to TJM 21.11 or later may be affected by a CSRF token implementation. For more information, see CSRF token issue.
- New 22.10 features: Some new features introduced in Workspaces 22.10 require Workspaces REST API 22.10. For more information, see Features that require Workspaces REST API 22.10.
- TJM 21.11 breaking changes: The Workspaces REST API packaged with Journey Manager 21.11 introduced changes incompatible with Workspaces 20.05 and earlier. For more information, see Breaking changes in TJM 21.11.
| Workspaces release | TJM release compatibility | Incompatibility issues |
|---|---|---|
| 22.10 | Compatible with all supported TJM product suite releases.1 | |
| 22.04 | Compatible with all supported TJM product suite releases.1 | |
| 21.11 |
|
|
| 20.05 |
|
- Assumes Journey Manager and Workspaces REST API are from the same TJM product suite release.
CSRF token issue
After upgrading a TJM 21.05 or earlier environment to TJM 21.11 or later, you may be presented with an HTTP 403 Forbidden status code when you attempt to access Workspaces. This may be due to a CSRF token implementation.
To fix this, you need to add the CSRFCross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious exploit of a website where unauthorized commands are transmitted from a user that the web application trusts. token to the following Workspaces portal pages:
- Login
- Change Password
- Forgotten Password
- Two Factor Authentication Setup
Failure to add the CSRF token to these pages prevents users with valid credentials from passing login authentication.
To avoid incompatibility issues when using CSRF tokens to mitigate CSRF attacks, your Maestro version must be the same as or later than your Manager version. For the best experience, we recommend using Manager and Maestro from the same release.
To add the CSRF token to a Workspaces portal page:
- Login to Manager
- Select Forms > Form Spaces and click
Work Spaces. For more information about form spaces, see View Form Spaces. - Select the Pages tab, locate the page to update, and click
Edit. For more information about form space pages, see View Form Space Pages. - Add the following code to the page's content inside the HTML
<form>element.#if ( $csrfParamter ) <input type="hidden" name="${csrfParamter}" value="${csrfToken}"/> #end - Click Save.
Repeat this process for each page that needs to be updated.
Features that require Workspaces REST API 22.10
The following features introduced in Workspaces 22.10 require the Workspaces REST API 22.10 or later.
- Bulk actions
- Support for invoking fluent functions
Breaking changes in TJM 21.11
Changes to the Workspaces REST API introduced in TJM 21.11 (and retained in later releases) are incompatible with earlier Workspaces releases. Consequently, the Workspaces 19.11 application can no longer be used in a TJM 21.11 or later environment, and you must upgrade your Workspaces application to an Open UX form. For information about developing and deploying a Workspaces Open UX form, see Journey Workspaces form development and Form deployment and security.
Unsupported releases
Workspaces 19.11 and earlier releases have reached end-of-life and are officially unsupported. For more information about TJM product support, see Temenos Journey Manager End-of-Life Policy.
Compatibility
Workspaces 19.11 and earlier releases are only compatible with Journey Manager and the Workspaces REST API included in the TJM 21.05 and earlier releases. This is due to breaking changes in the JM security model and WAR file structure introduced in TJM 21.11.
A TJM 19.11 or earlier environment upgraded to TJM 21.11 or later may be affected by the CSRF token issue mentioned above.
Open UX form
Workspaces 20.05 replaced the Workspaces client application with an Open UX form. So, when upgrading a TJM 19.11 or earlier environment to TJM 20.05 or later, we recommend you migrate your Workspaces client application to an Open UX form. To learn more about developing and deploying a Workspaces Open UX form, see Journey Workspaces form development and Form deployment and security.
While we don't recommend a mixed-release deployment using a non-Open UX Workspaces client application in a TJM 20.05 or later environment, you can make this work if you really need to keep using a non-Open UX Workspaces client application. However, there are a few things you should know before proceeding down this path.
- To install a non-Open UX Workspaces client application, you need to download and import the Workspaces 19.11 WAR file into a TJM 20.05 or later instance.
- Importing the Workspaces 19.11 WAR file will also install the 19.11 version of the Workspaces REST API into your TJM instance, replacing any existing later version of this API.
- Consequently, you won't have access to any improvements introduced in later versions of the Workspaces REST API unless the Workspaces 19.11 WAR file is installed with a different name and context path.