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 is a highly configurable product. Much of what you need to do to make a Springboard solution meet your needs can be done though configuration of the pre-built components included with a Springboard solution. However, you may have requirements that aren't handle by Springboard out of the box, and in these situations your Springboard solution can be customized to meet your requirements.
For a faster-to-market implementation that's easier to maintain and upgrade, Temenos recommends using a standard Springboard solution rather than a customized solution.
It's important to carefully review the details in your Springboard statement of work (SOW) and supporting product documentation. Springboard projects are extremely proscriptive. Certain changes are permitted, while others are not. These constraints ensure solutions are implemented in a repeatable and cost-effective manner, as well as ensuring ease of support for future updates and maintenance.
We refer to permitted changes, which are included by default in all Springboard SOWs, as configuration. Certain other changes are still permitted but they require additional funding and must be explicitly added to the project scope via additions to the SOW or change requests (CR).
Other changes are unsupported, whether added to scope via a SOW change, CR, or any other means. If any unsupported changes are made, the solution is no longer eligible for upgrades and may not be supported by the Springboard Engineering team.
For these reasons, it is important to carefully consider any application changes, understand whether they're in scope, and assess what impact they might have on the support and maintenance of your Springboard solution.
To determine whether a change is in scope, check your Springboard project documentation or contact your Springboard implementation team. If you have any doubt about whether a change is in scope, assume it isn't in scope until either you find a reference to the change in your project documentation or you receive confirmation from your Springboard implementation team that the change is in scope.
The major features and common requests are summarized below. At a glance, you can determine how each feature is offered: as a standard Springboard feature, via configuration, or via customization. Any customization will add to implementation cost and timeline.
| Feature | Standard | Configuration | Customization |
|---|---|---|---|
| Product selector with shopping cart (Retail DAO and Lending only) | |||
| Product catalog | |||
| Styling, images, logos | |||
| Status message content | |||
| KYC questions | |||
| Credit Union eligibility | |||
| Application prefill with Prove | |||
| Application prefill with Mitek | |||
| Joint applications (Retail DAO and Lending) | |||
| Device fraud check | |||
| IDA/IDV | |||
| Auto approve new accounts | |||
| New deposit account funding via EFT | |||
| New deposit account funding via debit or credit card | |||
| New deposit account funding via internal transfer (existing customers only) | |||
| Status emails | |||
| Back-office support in Workspaces (except Lending) | |||
| Save and resume | |||
| Additional pages | |||
| Changing order of pages | |||
| Changing page logic or business rules | |||
| Alternative vendors for prefill, IDA/IDV, card processing, EFT account verification | |||
| Altering page content or layout |
A Springboard solution can include several products, defined by the client during project initiation by completing a product specification. This specification is used by the implementation partner when configuring the product catalog. The definition of each product in the product catalog includes the product type, the available options, any funding requirements, and disclosures.
While there is no hard limit to the number of product types or products in a product catalog, consider the following recommendations for the best user experience.
Next, learn about Springboard components.