SpringboardThis topic is related to Springboard. | Form Builder | Retail DAO 4.0 This feature was updated in Retail DAO 4.0.
The Retail DAO Springboard solution consists of multiple components, all of which work together to provide the required functionality. The common components are listed below.
For more information, check the specific project documentation for each of the components, such as the Narrator, US Retail DAO Project and Exchange Components.
You must be familiar with Journey Manager and its framework creating services, Maestro, Narratives, SCM and Git. For more information on our products, visit our documentation website. Training in developing solutions for the Temenos Journey Manager is also available.
There are several forms which comprise the Springboard DAO solution. Each form represents a different chunk of functionality.
The Product Selector Form allows bank applicants to view product details and select one (or many) products that they would like to apply for. The shopping cart functionality makes it clear what the applicant has selected and then (unknowingly) transitions them to the DAO Form to complete their application. Banks can enforce mandatory or optional bundles, configure the ‘Learn More’ hyperlinks and restrict the number of products, if required.
This is the Deposit Account Opening form which collects the personal and financial details of the applicant. The application is run through the Alloy Decision Engine and may be approved, denied, or placed in a review queue. This form is the primary entry point into the DDA application and is accessed by bank new account applicants.
When an applicant has been approved for a new account, they’re typically expected to deposit some initial funds into the account. This form allows the user to fund the new account using Credit, Debit, ACH, Internal Transfer (from an account at the same bank), or Check by Mail.
In the standard US Retail DAO, Credit, Debit and ACH funds transfers are all processed using the Payroc payment processing platform. In addition to Payroc, an integration with Plaid Auth allows applicants using ACH to retrieve and verify their account details by logging into online banking, rather than typing them manually.
Internal Transfers are performed by the Core Banking API and allowed for existing bank customers.
When applications are sent to the Manual or Fraud Review queues they need to be manually assessed and a decision is made by a staff member of the bank.
The Review Form is used by bank staff to perform these review operations to request more information and make a final Approved/Declined decision for the application.
This form allows the user to unsubscribe from nurture email notifications, such as application reminder emails. It will not unsubscribe them from transactional emails required to provide details about their application or account(s), such as an Approved Confirmation or Declination email.
The US Retail DAO is based on the Application Framework and relies on Narratives to control the flow and actions of each of the forms. As a result, the Narration Controller (Narrator) must be installed and active on the Manager servers hosting the solution.
The Springboard is preconfigured to include Narratives services in your deployment, and comes with a predefined Narrative which includes all of the standard pages and actions required for DAO.
For more information, see the Narrator Developer Documentation.
When a user is applying for a Deposit Account, the Decision Engine can be used to calculate the eligibility of the applicant. The Decision Engine can access the Transaction and Form Data of the application and use this data to determine whether an application should be accepted, rejected, or placed in a review queue. For example, the application can be rejected if the user’s credit score is too low.
For more information, see the Developer Documentation in Gitlab.
This project provides the services required for the Springboard Retail DAO form, as well as the Core Banking API. The Narrative provided is designed to call each of these services as required to support the application.
The Fluent Functions in the US DAO project can do things such as:
The US Retail DAO comes with a predefined Collaboration Job Definition (Workflow). This Workflow controls what happens to the application once it is submitted, such as forwarding the application to one of the workspace queues or sending it on for delivery.
This workflow should not be modified for standard implementations.
The Springboard Maestro Template serves as a starting point for configurations and customizations. The Template implements our current UX best practices and provides client-side support for the Narrator.
The template can be configured in various ways. Colors, backgrounds, fonts and images can be easily configured without major modifications. The template can also be customized more deeply depending on a customer’s specific needs, but these deeper customizations are distinctly custom development and may result in the customer’s implementation forking from the base, making it no longer eligible for upgrades.
There are a number of exchange services used by the Springboard Retail DAO Project: