Springboard overview

     SpringboardThis topic is related to Springboard.   |     Form Builder |    23.10This feature was updated in 23.10     Retail DAO 4.1This feature was updated in Retail DAO 4.1.      SMB DAO 1.4This feature was updated in SMB DAO 1.4.      Lending 1.1This feature was updated in Lending 1.1.


Springboard solutions enable US banks to deliver an outstanding digital customer acquisition journey rapidly, using a ready-made solution on an extensible platform that grows with the financial institution. Standard Springboard can be implemented as the ready-made solution or can serve as a starting point for custom projects.

Several Springboard solutions are currently available.

Why choose a Springboard solution?

Springboard solutions provide a starting point for customer projects, offering an accelerated implementation schedule.

The standard Springboard solution provides value to our clients and implementation teams in several ways:

  • Offers a ready-made, quick to market, DAO or Lending experience.
  • Offers clients a head-start on developing a custom DAO or Lending solution.
  • Offers implementation teams a framework for implementing a custom DAO or Lending solution.
  • Demonstrates what a best-of-breed DAO or Lending solution should look like.
  • Serves as the reference architecture for a Temenos Journey Manager DAO or Lending solution.

Pre-built components

Springboard solutions require far less development than a custom Temenos Journey Manager project. This is achieved by pre-building many of the typical components required to support US solutions on the Journey platform. Examples of pre-built components include:

To learn more about the components supplied with each Springboard solution, see Springboard components.

Getting started

To start using Springboard and get the most out of it, we recommend you learn about the following.

  • Temenos Journey Manager platform: A platform for building, managing, and continuously improving onboarding journeys.
  • Journey Manager services:TJM software modules configured to perform specific business-related functionality.
  • Journey Maestro:TJM's customer experience development environment for building financial customer journeys.
  • Journey Narrative: A new way of thinking about TJM application design that forms the basis of a Springboard solution.
  • Maestro SCM: Integrate your Maestro projects with external source-code management (SCM) systems such as Git or SVN.
  • Git SCM: A free and open-source distributed version control system.
  • Journey Workspaces:TJM's authenticated review and approval portal for account opening and customer onboarding.
  • Journey Analytics: Capture and analyze behavioral and completion data for applications hosted on the TJM platform.

Information is available on these subjects and more in this documentation and on the TJM resources website. We also offer online courses and instructor-led training on developing Temenos Journey Manager platform solutions.

Implementing a Springboard solution

While substantial portions of a Springboard solution are pre-built, client-specific work is still required for every implementation. Typically, the bulk of the client work is focused into three main areas:

  • Configuration/Setup: Define style/brand, products, and other configurable options. Deploy and test components, and test integrations.
  • Core Banking Integration: Supports account and customer creation, and other critical onboarding activities.
  • Customization: Specific modifications to the project scope, added to the project statement of work (SOW) or via change requests (CR).

To learn more, see What clients need to know.

Integrated Development Environment

For Springboard development, you need an Integrated Development Environment (IDE) that supports Maven, Ant scripts, and writing services in Groovy. Eclipse and IntelliJ are two IDEs commonly used when building a Springboard project. Note that IntelliJ has native Groovy support while Eclipse requires a Groovy plugin.

You also need to install Maven and a JDK. The JDK version must match the version installed on Journey Manager. To learn more, see Journey Manager 3rd Party Libraries > Java.

Next, learn about Springboard architecture.