SpringboardThis topic is related to Springboard. | Form Builder | SMB DAO 1.4 This feature was updated in SMB DAO 1.4.
Springboard is a highly configurable product. You can further customize it as per your requirement.
It’s important to carefully review the details in this document, the Springboard US SMB DAO SOW Template and supporting product documentation. Unlike other Client Services engagements, which are entirely composed of custom development, 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.
Permitted changes which are included by default in all Springboard SOWs are typically referred to 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.
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 customer’s solution will no longer be eligible for upgrades and may not be supported by the Springboard Engineering team.
For these reasons, it’s 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.
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 a number of products to your Sprindboard solution. Products are added to a JSON file, so there is no hard limit, but we recommend not to exceed 10 products. 3 to 5 products are ideal as it's been thoroughly tested. This 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.
For more information, check the specific project documentation for each of the components, such as the Narrator, US DAO Project and Exchange Components.
You must be familiar with Journey Manager and it’s framework creating services, Maestro, Narratives, SCM and GitGit is a version control system for tracking changes in computer files and coordinating work on those files among multiple people. It is primarily used for source code management in software development,[8] but it can be used to keep track of changes in any set of files.. For more information on our products, visit our community and documentation websites. Training on developing solutions on the Temenos Journey Manager is also available.
This describes the default configuration of the Job Controller, associated components, and the workflow that connects them.
Next, learn about SMB DAO components.