This article provides step-by-step guidance on implementing Two-Factor Authentication (2FA) in Journey Manager for enhanced security.

This article provides troubleshooting steps for resolving the error 'Multi Factor Authentication is not required for this user' when resetting a 2FA key in Journey Manager.

This article provides guidance on how to modify a Groovy script in Temenos Journey Manager (TJM) when it appears as read-only.

This article addresses the issue of the background save feature failing in Maestro forms when using the Form.backgroundSave() API. Customers may encounter the error message 'Possibly unhandled rejection: Save is disabled.' on certain pages. This article explains the root cause, provides reproduction steps, and offers resolution and a workaround.

When working with Temenos Journey Manager (JM), there may be instances where specific files cannot be directly uploaded to the platform. To address this, hosting files externally through a CDN, AEM, or your web server ensures accessibility and security.

This article explains the functionality of the Update Design from Maestro feature in Temenos Journey Manager (JM) and addresses the issue of 401 Unauthorized errors that users may encounter. 

This article explains how the Server Uptime (System > System Information) value is passed, and when it is actually reset.

This article explains the issue where users, despite having all necessary roles and permissions in Temenos Journey Manager (TJM), are unable to view other users. It outlines the possible causes, highlights how to check for proper Global Access settings, and provides references for further troubleshooting.

This article addresses issues encountered during Journey Manager upgrades, where services fail due to enhanced static type checking in newer versions. It provides examples of such failures and explains both the immediate and permanent fixes.

This article provides a diagnostic script to validate outbound connectivity and whitelisting from the Journey Manager environment. It helps identify whether the destination endpoint is accessible, or if IP or URL whitelisting is required by Temenos to enable successful communication.