Decision Priority
If a decision stack contains multiple decisions of the same type, the most recent decision overrides all previous decisions of that type unless there is a ForceCase function, which forces case creation. The following example, which shows a Falcon Expert decision stack, illustrates this behavior.
- SendCustomAdvice(A, 1)
- TriggerCase(ACCOUNT)
- SendCustomAdvice(B, 2)
- SendCustomAdvice(C, 3)
- SendAuthAdvice(DECLINE)
- SendCustomAdvice(D, 4)
- SendCustomAdvice(D, 5)
- SendCustomAdvice(E, 6)
- SendCustomAdvice(F, 7)
- SendCustomAdvice(G, 8)
- SendCustomAdvice(H, 9)
- SendCustomAdvice(A, 10)
- SendCustomAdvice(B, 11)
- SendCustomAdvice(I, 12)
- SendCustomAdvice(J, 13)
In this example, decision 12 overrules decision 1, decision 13 overrules decision 3, and decision 7 overrules decision 6. The scoring response message would contain the following decision type/code pairs:
- A, 10
- origAcctCase
- B, 11
- C, 3
- authAdvice, decline
- D, 5
- E, 6
- F, 7
The scoring response message does not include decision type/code pairs (I, 12) and (J, 13) because the other pairs occupy the 8 available slots.
To extend the previous example, if the sixteenth decision was SuppressCase(), the response message would contain the following decision type/code pairs:
- A, 10
- B, 11
- C, 3
- authAdvice, decline
- D, 5
- E, 6
- F, 7
- G, 8
In this example, SuppressCase() suppresses the TriggerCase() decision, which was the second decision.