CA RiskMinder Administration Guide › Managing Cases › Understanding RiskMinder Cases › Case Management Components › Queue Monitor Thread

Queue Monitor Thread

The Queue Monitor (referred to as Scheduler) thread runs at the Queue Server-end and is responsible for creating the Case Schedule, populating the Case Queues with cases, and prepares the Queues for Case Dispatcher Module.

This thread works as follows:

1. It wakes up at a pre-defined interval and fetches the list of all the latest cases from the database where:
   • At least one transaction shows the Fraud Status as Undetermined.

   and

   • The case has not expired.
2. Caches the Queues with cases.
3. Based on the case state and other criteria (such as Transaction Date, Transaction Amount, or Next Action Date), the thread assigns the cases into the Case Queues.
4. For more information on case states, see "Case States".
5. When a case is assigned to the Queue, an in-memory list is created for the Queue.
6. On completion of the case assignment to a Queue, the state of all the assigned cases is changed to OPEN.
7. When the Customer Service Representatives (CSRs) click the Save and Go to Next Case or the Go to Next Case button:
   1. A request to fetch the next case in the Queue is sent to the Queue Monitor Thread via Queue Server.
   2. In response, the Case Dispatcher Module picks the case from the memory queue and returns its Case ID to the Administration Console instance from where the request originated.
8. The state of the case is then changed to IN PROGRESS, and the CSRs can work on the case.
9. On receiving the Case ID, the Administration Console instance fetches all the transactions for the case from the database and displays the same to the CSR.

   Based on the case review process, the case state can change. See "Case States" for more information.