Test the Rules and Evaluate the Performance
- Estimate the number of cases you expect to see within an appropriate time period based on this rule. (Rule reports are not real-time.)
- Check the Test Mode and Is Active options to ensure that the rule will be deployed in test mode.
- If you do not have permission to deploy, have the appropriate personnel deploy the updated ruleset into production.
- Run the Decision Frequency of Rules report for your test rule.
Administrators can determine which rules they want to record with transactions. These rules are recorded in the rules fired tables. Whether the rule is in test mode or in active mode, the Track Decisions check box will record the rule actions that were or would be performed on the transaction. When a rule is in active mode with the Track Decisions check box selected, Falcon uses the rule to evaluate and make decisions against the live production data. When a rule is in test mode with the Track Decisions check box selected, Falcon uses the rule to evaluate against live production data, but only records the actions it would have performed. In some instances, no actions are actually taken. The decisions will be recorded to evaluate the rule's performance; for example, the number of cases that rule would have created.
If an approved rule is active and has been deployed to the Scoring Server, certain actions will occur regardless of whether it is in test mode or production mode.
- QAVs are written to the Case Manager
- Create Notice is written and viewable
- RETURN statement
- UDVs are written to the profile
- UDPs are written to the profile
- Force Case
- Trigger Case
- Suppress Case
- SendCustomAdvice does not send custom codes
- SendAuthAdvice does not send a decline or other authorization code
![]() | Note: All other common actions
will occur if a rule is in test mode. Therefore, it is recommended to use comment markers (
// ) to comment out any actions you do not want to occur, until your rule is out of test mode.
|