Adding an Action
The then portion of the rule consists of action statements.
You can add up to five actions per rule in Falcon.
To add an action click the round blue operation icon that is displayed to the left of every action in your rule.
- Decision Action performs a decision on the transaction if all conditions are met. For example, a rule says if the transaction is high dollar (more than 1000) and high score (greater than 900), then decline the transaction and create a case. You would select the TriggerCase() action from the Decision Action drop-down list. Scroll down the menu to view additional actions which you can add, such as called SendAuthAdvice(DECLINE).
The Force actions are executed when you have a series of conditions which approve a transaction but one condition which overrides the approvals and creates a case.
The Suppress actions are executed when you have a series of conditions which decline a transaction but one condition which overrides the decline action and approves the transaction.
- Free Form Action, like a Free Form condition, enables you to enter free form text (the same choices as Decision Action) to indicate what action will be performed if your rule conditions evaluate as true.
Custom Decisions
The decisions shown in the previous figure pass hard-coded decision types and codes in the scoring response message to case management applications via the database. For example, when you specify SendAuthAdvice(APPROVE), Falcon includes in the scoring message the decision type/code pair: (). The decision type is the name of the decision, and the decision code is the value of the decision type. In this case, the advice is to approve the transaction. All of the decision conditions in the previous figure have similar hard-coded decision types and codes.
You can create custom decision type and code pairs using the SendCustomAdvice() Expert function. For example, you could define a custom decision type to be CreditLimitChange and the associated decision code could be the dollar amount of the credit limit change. Being able to define decision types and codes enables you to take actions based on anything provided in the data feeds.
The developer must communicate with the rule author what the customized decision types and codes are. This communication can be as simple as a three-column table where the first column lists the decision types, the second column lists the associated decision codes, and the third column describes the semantics of the pair.
The scoring response message contains up to ten decisions. The FICO® Falcon® Fraud Manager [AIX/RHEL Server or Mainframe (z/OS)] Developer's Guide describes decision priority and the rules Falcon uses to decide which decisions to include in the scoring message.