Execution Strategy
Execution strategy allows you to change the outcome produced by the rule solver. There are several options for the execution strategy described below.
- Standard strategy (default)
- Array strategy
- First Match strategy
- Evaluate All strategy - Available only in decision tables
You can easily set the execution strategy for solver API by adding the X-Strategy header. If the header is not specified, the system automatically chooses the STANDARD strategy.
HTTP Header | Possible value |
|---|---|
X-Strategy | STANDARD |
X-Strategy | ARRAY |
X-Strategy | FIRST_MATCH |
X-Strategy | EVALUATE_ALL |
Rule Flow always uses the first match strategy.
Execution strategy can be also chosen in Test bench.
The distinct types of execution strategies are described below.
If 2 lines are matching the input, the output will be all the matching rows. The order will be the same as the order of rows in the rule.
The output looks like this:
[
{
"client": {
"segment": "affluent"
},
"profitability": 1
},
{
"client": {
"segment": "top affluent"
},
"profitability": 1.6
}
]
If 2 lines are matching the input, the output is returning just the first matching line from the rule (table, script).
The output looks like this:
[
{
"client": {
"segment": "affluent"
},
"profitability": 1
}
]
If 2 lines are matching the input, the outputs are returned in the array format.
The output looks like this:
[
{
"client": {
"segment": [
"affluent",
"top affluent"
]
},
"profitability": [
1,
1.6
]
}
]
This execution strategy allows you to obtain satisfiability based on the input conditions of all rows in the decision table. If your decision table has N rows, the evaluation response will also be N objects. For each output, you will have an indication of whether the line was met or not.
The output can looks like this:
[
{
"client": {
"segment": "affluent"
},
"profitability": 1,
"_match": true
},
{
"client": {
"segment": "top affluent"
},
"profitability": 1.6,
"_match": false
}
]
Last modified 9mo ago