Edit

Kongsi melalui

Case management for administrators

  • Artikel

This article explains how to work with case management as an administrator in Microsoft Dynamics 365 Fraud Protection.

To complete administrator-specific tasks in case management for Fraud Protection, you must be assigned one of the following roles:

  • Product admin
  • All areas administrator
  • All areas editor
  • Manual review fraud manager
  • PSP administrator (available only in payment service provider [PSP] environments)
  • Fraud manager (available only in PSP environments)
  • Fraud supervisor (available only in PSP environments)

If you're assigned one of these roles, you can complete the following tasks:

Define cases for manual review agents

You can define the criteria that specific purchase transactions must meet to qualify for manual review. You can create assessment rules that generate a Review() decision as output. For more information about how to create these rules, see Manage rules. You can use any criteria that meet your business requirements.

The following example shows all transactions that must be selected for review. The risk score of the transactions is more than 600, and the user's country or region is US.

RETURN Review()
WHEN @"riskScore" > 600 and @"user.country" == "US"

Create queues to store cases

You can use queues to organize purchase transactions that the assessment rules mark for review. Transactions that appear in the case management queues are referred to as cases. You can create up to 29 queues for each environment.

Follow these steps to create a queue.

  1. In the left navigation pane, select Case management > Queues, and then select New queue.
  2. Select the assessment type.
  3. Enter a name that helps you identify the purpose of the queue.
  4. Enter a description that explains the types of cases that are stored in this queue.
  5. Select your preference for the review sequence. If you select Unrestricted queue, you can review any case in the queue in any order. If you select Restricted queue, you must review cases in a predefined order.
  6. Select the default ordering and order by to define the order in which cases appear and are presented to review agents. In a restricted queue, your selections define the order in which agents can review the cases.
  7. Select the time-out duration and default action to define the maximum amount of time that a case can be in the queue without being reviewed and the default action that is taken when that time is reached.
  8. You can also assign this queue to a specific set of Microsoft Entra users and groups by adding them to the queue. When users go to their Case management > Queues page from the left nav, all the queues assigned to them are displayed. The “Queues assigned to me” filter is selected by default. The filter can help users to focus and work on the queues that are assigned to them. Users can view all the available queues by applying the “All queues” filter in the Queues page.

You can edit or delete any queue that you created. You can also add or remove the assigned users and groups from the queue. To edit the name of a queue or delete a queue, remove the routing rules that have a dependency on the queue. For more information about routing rules, refer to the next section.

Note

  • Before changing the ordering settings of a queue, to make sure the new ordering is correct, review all existing cases until the queue is empty. Then change the ordering settings as needed. New cases will then have the correct order.
  • Alternatively, you can create a new queue which has the new ordering and point to it from a new or existing routing rule. That way, new cases will have the correct order.

All your environments have a system-created queue that is named General. Cases that don't qualify to be routed to a specific queue are routed to the General queue. The General queue has the following settings:

  • Timeout: 24 hours
  • Default action: Approve
  • Default ordering: Event timestamp
  • Order by: Ascending (oldest cases are shown first)

These settings can't be edited.

Define the criteria to route cases to the appropriate queue

After the queues are created, define the criteria that will be used to route cases to them. These criteria make up the routing rules. Routing rules resemble assessment rules, but they don't result in a decision. Instead, they result in a routing action. Although each queue can have multiple cases, each case can be routed to only one queue. You can write multiple routing rules for the same queue.

After cases pass through the routing rules, there's a five-minute hold before they appear in the appropriate queue. During this time, the cases are updated with supplementary events. If a supplementary event that has any statusType value is received through the purchaseStatus application programming interface (API), the case isn't routed to a queue. In this case, the statusType value that is received in the purchaseStatus API event is recorded as the transaction's latest status.

Routing rules can be created in either a visual editor or a code editor. In the code editor, you can create routing rules by using the Fraud Protection language. For more information, see Language reference guide.

Follow these steps to create a routing rule.

  1. In the left navigation pane, select Case management > Routing rules, and then select New rule.

  2. Select the relevant assessment type.

  3. To add a top-level condition that can be applied to the rule set, add it under the condition segment. For example, you might want the rule set to be run for a specific product category.

  4. Select New clause to define a new clause for the routing rule.

  5. In the drop-down list, select the queue to route the cases to.

  6. Define the routing criteria by using the drop-down lists for attributes and operators and providing the desired values.

  7. To switch to the code editor, select Code view in the upper right of the clause.

  8. Use the command RouteTo Queue("<Queue name>") WHEN <Condition>. The following example shows the code view for the command to route transactions where the total amount is more than 1,000 to a High Value Orders queue.

    ROUTETO Queue("High Value Orders")
WHEN @"purchase.request.totalAmount" > 1000

Note

The routing rules that you create by using the visual editor are translated to the code view when you switch to the code editor. However, after you edit the rules by using the code editor, you can't switch back to the visual view.

To customize the order of execution for routing rules, drag the routing rules to define which rules must be executed first. When you are done, select Save on the Routing rules page.

View the case management report dashboard

Case management administrators have access to view the case management report dashboard. This dashboard lets managers analyze the queue and agent performance. The case management report is updated every 24 hours. You can select the assessment name, queue name, and agent name on the drop-down menu, and set the date range. The report shows the performance of several key metrics over daily, weekly, and monthly periods. To review specific cases, you can use the search feature to search by case management-specific attributes such as Queue name, Agent name, Review decision, and Reason and Review notes.