SMB DAO Components

   SpringboardThis topic is related to Springboard. |   Form Builder |  SMB DAO 1.4 This feature was updated in SMB DAO 1.4.

The SMB DAO solution consists of multiple components, all of which work together to provide the required functionality. The common components are listed below.

Forms

There are several forms which comprise the Springboard DAO solution. Each form represents a different chunk of functionality.

Product Selector Form (optional)  |   v3.0 This feature was updated in v3.0.

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 have the ability to enforce mandatory or optional bundles, configure the ‘Learn More’ hyperlinks and restrict the number of products, if required.

SMB DAO Form (Primary Applicant)

This is the Deposit Account Opening form which collects personal and business details of the applicant. The application is run through the Alloy Decision Engine on submission and may be approved, denied, or placed in a review queue. This form is the primary entry point into the application for the Primary Applicant.

SMB Owners DAO Form (Owners/Signatories)

This is the Deposit Account Opening form which collects personal and business details of any Owners or Signatories that were identified by the Primary Applicant. The application is run through the Alloy Decision Engine on submission and may be approved, denied, or placed in a review queue. This form is the primary entry point into the application for any Owners / Signatories.

Review Form

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 and make a final Approved/Declined decision for the Application.

Email Unsubscribe Form

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.

SMB Kickoff Form

This is used to speed up the testing and debug process for the US SMB DAO form. It allows testers to bypass the US SMB DAO form to simulate approved, declined or pended applications and kick off the Job Controller.

Narrative

The SMB DAO Solution is based on our 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 Transact Manager servers hosting the solution.

The solution 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 SMB DAO.

For more information, see developer documentation.

SMB DAO Project

This project provides the services required for the Springboard 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 SMB DAO project can do things such as:

  • Product data pre-fill
  • Applicant IDV/IDA through Alloy integration
  • Populating application used by Workspaces
  • Fetching customer data to be prefilled

Workflow /Collaboration Jobs and Testing Form

The SMB DAO solution 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.

Maestro Template

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 some ways. Colors, backgrounds, and some other items 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.

Exchange Services

There are a number of exchange services used by the Springboard DAO Project:

  • Google Places API - Address Details - v1.1.2 - Fluent Function that gets additional information for the address select from the list of addresses provided by Google Places API
  • Google Places API - Address Search - v1.1.2 - Fluent Function which calls Google Places API to get list of possible address for the user to select from.

Next, learn about SMB DAO workflows.