SpringboardThis topic is related to Springboard. | Form Builder | Retail DAO 4.0 This feature was updated in Retail DAO 4.0.
Springboard is a highly configurable product. You can further customize it as per your requirements. For faster to market implementation, Temenos recommends using the standard offering rather than a customized solution.
It’s important to carefully review the details in the Springboard US DAO SOW and supporting product documentation. Springboard projects are extremely prescriptive. Certain changes are permitted and 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 Statements of Work (SOW), as configuration. Certain other changes are still permitted, however, they require additional funding and must be explicitly added to the project scope via additions to the SOW or Change Requests (CR).
Any other changes, whether added to scope via a SOW change, CR or any other means are unsupported. If any of these unsupported changes are made, the solution will no longer be eligible for upgrades and may not be supported by the Springboard Engineering team.
For these reasons, it is obviously important to carefully consider any changes to the application, whether they’re in scope and what impact they might have on support or future maintenance.
| Feature | Standard | Custom |
|---|---|---|
|
Product selector with shopping cart |
||
|
New customer account opening |
||
|
Application prefill with Prove |
|
|
|
Application prefill with Mitek |
||
| Credit Union eligibility | ||
| Existing customer account opening | ||
| Joint applications | ||
| In Branch experience | ||
| Device fraud check | ||
| IDA / IDV | ||
| Auto approve new accounts | ||
| New account funding via ACH (Automated Clearing House) | ||
| New account funding via card | ||
| New account funding via internal transfer (existing customers only | ||
| Styling to match financial institution brand | ||
| Back-office support in Workspaces | ||
| Status emails | ||
| Save and resume |
When in doubt you should assume a change is unsupported until you receive confirmation from the Springboard Engineering team or find an appropriate reference to the change in the product documentation.
You can add several products to your Springboard solution. Products are added to a JSON file via the Journey Setup Tool. During project initiation, the client will complete a Product Specification for use by the Implementation Partner to build the product configuration. There is no hard limit to the number of products, but we recommend not exceeding 10 products. 3 to 5 products are ideal as this has been thoroughly tested. The number of products is also related to the number of product selectors you can have, which has no hard limit as well, but we recommend not going over 25.
This describes the default configuration of the Job Controller, associated components, and the workflow that connects them.
This describes the default configuration of the Job Controller, associated components, and the workflow that connects them.
1. The Springboard DAO form is submitted.
2. Job Controller is invoked.
3. Job Controller invokes the Determine Initial Route Job Action. This Job Action assumes that the Decide (Decision Framework) service has been run, and that the decision configuration for the DAO form includes the following destinations:
The Job Action inspects the results of the Decide service, and returns the result, which is then used to route the Job Controller to the next step.
4. The Job Controller proceeds to the next step, there are several possibilities depending on the result of the previous step:
Next, learn about Springboard components.