Introduction to Journey Workspaces

Overview

Journey Workspaces is a Journey Manager (JM) module providing web portal functionality for application management. Workspaces has been completely redesigned, adding powerful filtering capabilities (based on new JM REST APIs) that will enable users to find and manipulate applications quickly.

Currently, Workspaces supports 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.

Prerequisites

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

• Journey Manager 19.05 or later.
• A JM user account with privileges for deploying and configuring WAR files.
• A Workspaces installation (WAR) file.

You can download the Workspaces installation file from the Temenos Journey Manager resources website.

note

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

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

Supported web browsers

Workspaces works with current versions of the following web browsers.

• Chrome
• Firefox
• Microsoft Edge
• Internet Explorer 11

Known Limitations

JM allows only one active Workspaces session. You can login to Workspaces 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.

About this documentation

Conventions

The following conventions are used in this documentation.

Convention	Example
Defined terms are displayed exactly as shown in Terminology 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
Applicants card	The section of the Details screen that shows key information about the applicants.
Configure	Determine how a Workspaces instance behaves by defining application-level parameters, attributes or properties. Examples of configuration include defining Workspaces Global Txn property in JM. Note that only users with appropriate permissions can access and make changes to configuration options.
Custom cards	The section of the Details screen which shows custom information cards that are configured in Workspaces.
Details screen	A Workspaces screen showing comprehensive information for a selected Txn. To display the Details screen, click a Txn in the List Screen.
Integrations card	The section of the Details screen that shows information for the various integrations that are configured in Workspaces. This is referred to as the Background Checks card in the Workspaces User Guide.
JM	Journey Manager
Key Info card	The 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.
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.
Workspaces	Journey Workspaces