Introduction to Journey Brokers

Journey Brokers is a Workspaces extension offering a self-service portal for authenticated applicants to manage application creation, respond to follow-up requests, and monitor application progress. Journey Brokers provides an efficient, digital-first method for authenticated non-bank users to have a greater involvement in the application process. By giving applicants (or their representative) more direct involvement in the application process, Journey Brokers helps to improve the speed and accuracy of the application resolution process.

Journey Brokers works in conjunction with other Workspaces back-office business process functionality including:

• Application processing: Review pending applications that require manual intervention as part of the application workflow.
• Helpdesk: Assist customers with their enquiries on application preparation and progress.
• Assisted channel: Relationship managers can initiate and manage customer applications throughout the application lifecycle.
• Task management: Features that allow task group managers to manage applications in their group.

This guide explains how to set up Journey Brokers in Journey Manager, and how to develop and deploy a Journey Brokers client application, including the steps required to configure collaboration jobs to work with Journey Brokers.

Prerequisites

To deploy and configure Journey Brokers in your JM environment, you need access to the following resources.

• Journey Manager 21.11 or later with the Workspaces REST API installed.
• A JM user account with privileges for deploying and configuring WAR files.

The Workspaces REST API is included in the Workspaces installation (WAR) file which is bundled with the Journey Manager installation file as an optional package. While this is the easiest way to install Workspaces, the Workspaces installation file is available to download from the Journey Manager resources website (login required).

note

If you're deploying Workspaces in a Temenos cloud hosting environment, contact the Temenos cloud hosting team for assistance in configuring the Apache proxy settings to access Journey Brokers after deployment.

It is assumed you are proficient with the Journey Manager platform, collaboration jobs, scripting with Groovy and Fluent functions, and setting up forms in Journey Manager. If you're unfamiliar with any of these, use the links above to learn about them, or contact us to discuss e-Learning and instructor-led training options.

Supported web browsers

Journey Engage has been designed for and tested against the following web browsers.

• Chrome
• Firefox
• Microsoft Edge

For the best Journey Engage experience, we recommend using the latest version of a supported web browser, and that you keep your browser updated, especially through the application of security patches. While you may be able to access Journey Engage using other browsers, there's no guarantee that everything will work, and you may not enjoy the same great user experience that is available when using a supported browser.

Known limitations

One active session

JM allows only one active Journey Engage session per user. You can login to Journey Engage on multiple browsers, but only the first browser in which you perform an action will be successful. The second and subsequent browsers in which you attempt an action will report an HTTP 403 Forbidden status code.

IE11 not supported

Journey Brokers support for Internet Explorer is discontinued. For details, see Update on TJM Support for IE11.

Frequently asked questions

Journey Brokers is highly configurable, so you may have questions about deploying, configuring, or using Journey Brokers in your environment. We've captured some commonly asked questions in the Workspaces FAQ, and you might find answers to your questions there.

About this documentation

Conventions

The following conventions are used in this documentation.

Convention	Example
Defined terms are displayed exactly as shown in the Terminology section below.	To display the Details Screen, click a Txn.
Named user interface elements are displayed in bold font.	Click Import to complete the WAR file deployment.

Terminology

The following defined terms are used in this documentation.

Term	Meaning
Configure	Establish how a Workspaces instance behaves by defining application-level parameters, attributes or properties; for example, defining the Workspaces Global Txn property in JM. Note that only users with appropriate permissions can access and make changes to configuration options.
Custom cards	A Details screen section that presents different kinds of custom information such as applicant details, background check details, or any other custom information not included in the default configuration.
Details screen	A Workspaces screen showing comprehensive information for a selected Txn. To display the Details screen, click a Txn item in the table on the List screen.
Key Info card	A section at the top of the Details screen that shows key information about the Txn.
List screen	A Workspaces screen showing a configurable list of Txns available to the logged-in user.
SLA	Service Level Agreement.
Txn	A single item in a List screen table. The Details screen shows comprehensive information for a single Txn. Also referred to as a Task.