Skip to main content

Version: 21.11

Introduction to the Workspaces Applicant Portal

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.

Workspaces also offers functionality for non-bank users. The Applicant Portal is a self-service portal for authenticated applicants to manage application creation, respond to follow-up requests, and monitor application progress.

This guide explains how to set up Applicant Portal in Journey Manager, and the steps required to configure collaboration jobs to work with Applicant Portal.


To deploy and configure the Workspaces Applicant Portal 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, if required, you can download the Workspaces installation file from the Journey Manager resources website (login required).


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, use the links above to learn about them, or contact us to discuss e-Learning and instructor-led training options.

Supported web browsers

The Workspaces Applicant Portal has been designed for and tested against the following web browsers.

  • Chrome
  • Firefox
  • Microsoft Edge

For the best Applicant Portal experience, we recommend that you use the latest version of Chrome, Firefox, or Edge, and that you keep your browser updated, especially through the application of security patches.

While you may be able to access the Applicant Portal 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. We strongly recommend that you use a supported browser for the best Applicant Portal experience.

Known Limitations

Journey Manager allows only one active Workspaces session. While you can login to Workspaces on multiple browsers, 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.

Frequently Asked Questions (FAQ)

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

About this documentation


The following conventions are used in this documentation.

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.


The following defined terms are used in this documentation.

ConfigureDetermine 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 cardsA 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 screenA 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.
FAQFrequently Asked Question
JMJourney Manager
Key Info cardA section at the top of the Details screen that shows key information about the Txn.
List screenA Workspaces screen showing a configurable list of Txns available to the logged-in user.
SLAService Level Agreement
TxnA single item in a List screen table. The Details screen shows comprehensive information for a single Txn . Also referred to as a Task.
WorkspacesJourney Workspaces