Temenos Journey Manager Deprecation Schedule

   PlatformApplicable to all products in Temenos Journey Manager.  |   All Personas |  All versions This feature is related to all versions.

As the Journey Manager platform continuously aims to innovate, improve and stay current with security hardening, there is sometimes a need to deprecate some older or obsolete features of the platform.

The reasons for deprecating features include:

• Reliance on 3rd party components which have reached End-of-LifeEnd-of-life (EOL) is a term used with respect to a product supplied to customers, indicating that the product is in the end of its useful life (from the vendor's point of view), and a vendor stops marketing, selling, or rework sustaining it. and are no longer supported.
• Features which pose a security risk to the platform and our customers.
• Features which are not used or barely used by customers.
• Features which add significant complexity to the platform without delivering commensurate business value.

Feature	Last Supported Release of Temenos Journey Manager platform 1	Reason for Deprecation	Migration Strategy
Oracle JDK 8	18.05	Oracle EOL Policy (Jan 2019)	Upgrade to Temenos Journey Manager platform 18.11 or later to obtain OpenJDK Java 11 security updates
Payment Gateway APIs (2 party)	18.11	PCI Compliance & Gateway Vendor EOL Policies	Use redirect gateway integrations (3 party)
Eclipse BIRT Reports	18.11	Security Hardening Reasons	Use the Licensing reports and new Operational reporting features in Temenos Journey Manager platform 18.11
Adobe LiveCycle	19.05	Adobe EOL Policy	Migrate Adobe LiveCycle Forms to Maestro Forms. Migrate Adobe LiveCycle Output PDF receipts to use Manager dynamic PDF receipts.
Groovy Access to internal APIs	19.11	Security Hardening and Platform Support Reasons	Migrate scripts to supported Transact Fluent API
Work Space (v1)	20.11	Platform Support and Performance Reasons	Use Workspaces (v2) replacement module

Next, learn more about the Temenos Journey Manager End-of-Life Policy.