In this 2nd onboarding article, we look at putting the Apply button on the home page to improve the completion rate of your application.

In this 1st article of our 10 part onboarding series, we look at different paths to purchase different products. It's not one size fits all.

One of the most critical areas of the customer journey in banking is the application process. This is the process whereby the customer will apply for a particular product or service.

This article describes the issue that occurs when using the Maestro attachment component with forms containing the Narration Controller and Narratives Service. It provides steps to resolve the issue by updating the components to their latest versions.

This article describes an issue found in Maestro forms built on the maguire-template, where a Page Load Rule is executed twice when using the Narrator controller component.

This article provides details about issues resulting from special characters being embedded in template image names, resulting in CSS modifications not being rendered after publishing in Journey Maestro.

This article provides best practices and troubleshooting guidance for importing projects into Journey Maestro and Journey Manager. By following these recommendations, you can avoid common pitfalls such as library version conflicts, oversized project files, and missing components.

This article provides guidelines for configuring Mutual TLS (mTLS) authentication in Temenos Journey Manager. It explains the differences between one-way and two-way TLS authentication and outlines the steps required for a successful setup.

This article covers the frequently asked questions (FAQs) related to Open UX for Temenos Journey Manager. It includes documentation access, supported frameworks, available SDKs, exchange component compatibility, sandbox availability, Postman collections, and the latest version information. Additionally, it outlines Temenos’ roadmap for Open UX improvements in upcoming Journey Manager (TJM) releases.

This article outlines how to properly update a transaction’s status via a scheduled job when a form uses the Submission Completed Processor Service, and provides guidance on using REST API calls to resolve the following error: