Decisions by Account
The Decision by Account report shows how often decisions are made on a particular account for a specified date range.
This report provides managers and supervisors information on whether rules are acting on transactions as intended. It also provides the chronological order of rules that acted on the transactions in a particular account. Finally, because this report shows transactions in both Test and Production modes, different rules can be tested out and their effect on transactions viewed using this report.
 | Note: The time values shown in this report reflect the time in the database server, not necessarily the time zone set in the
Case Manager
User Settings page. A time that is shown as 8:15 PM PST, January 1 in the
Case Manager is shown in the reports as 4:15 AM January 2 if the database server is set to GMT. That same time would be shown in the report as 11:15 PM January 1 if the database server is set to Eastern Standard Time.
|
- Client
- Rule Set
- Rule
- Mode
- Decision
- Account (type the full account number)
- Report period (Start Date and End Date, optional)
| Field name | Description |
|---|---|
| Report Period |
Date range for the report. The format on the report includes the text Report Period: <From Date> to <To Date>. |
| Rule |
Name of the rule. |
| Decision Type |
The decision made by the rule when it was triggered. |
| Decision |
Optional Decision code related to this transaction. This is also called the Response Code or Authorization Decision. This are used to provide additional information about the decision, for example, force for create account case. |
| Transaction |
The transaction number is a Unique ID for this particular transaction. |
| Date/Time |
The date and time when the particular rule acted on the transaction. |
| Transaction Type |
Code that describes the type of transaction that was made. (Transaction Type codes vary by Product Type.) |
| Amount |
The Amount of each transaction in the account. |
| Case Created |
This is the indicator that specifies that this transaction created the initial case. Subsequent transactions could fire a create case decision, but they are not the transaction that generated the case. Fill in the case # created. |
| Mode |
Mode in effect when the rule acted on the transaction. Modes can be Production or Test. |