SpringboardThis topic is related to Springboard. | Form Builder | 23.10This feature was updated in 23.10
The Decision Framework is a dynamic decision service driven by configuration rather than code. It allows for easy modification of the rules that leads to application decisions, without the need to write or deploy code.
This service is currently driven by JSON configuration files, with future plans for an editor user interface (UI).
These documents cover the following:
To use Decision Framework outside of Springboard, this guide assumes intermediate knowledge of the Temenos Journey Manager (TJM) platform, including:
If you're unfamiliar with any of these, we recommend you learn the basics of each before using the Decision Framework outside of Springboard.The Decision Framework is intended for use with Journey Narratives. However, it can be used with any application that has Fluent Functions enabled.
There are two primary inputs to the Decision Framework, the configuration that defines all of the decision rules and outcomes, and the data that is combined with the rules to determine results.
The results of the Decision Framework are called Destinations. Destinations act like flags, indicating which decision rules evaluated to true and what should be done with the application as a result.
An example result might look something like this:
{
"destinations" : {
"approved": {
"isActive": false,
"reasons": []
},
"manualReview": {
"isActive": true,
"reasons": [ "addressMismatch" ]
},
"declined": {
"isActive": false,
"reasons": []
}
},
"calculatedDate": "2018-01-13T18:25:43.511Z"
}Next, learn about configuring the Decision Framework.