# Chapter 4 — Rules and Model Configuration

## Purpose

This chapter explains where rule authors and administrators configure the logic that drives scoring, case creation, and other fraud behaviors.

## Main configuration areas

The Model Configuration and Rules areas are the control points for fraud policy. They are used for:

- request XPaths; use these when you need to extract transaction data from incoming requests.
- inline functions and scripts; use these when you need lightweight logic without creating a separate component.
- lists and dictionaries; use these for shared reference values such as countries, merchants, or risk categories.
- gateway rules; use these to define how gateway-level decisions should be handled.
- abstraction rules; use these to simplify and organize more complex logic.
- activation rules; use these to decide when a case or workflow should be created.
- TTL counters; use these to control how long a signal or state should remain active.
- suppression and watcher settings; use these to manage how activity is suppressed or monitored.

## How to approach configuration changes

1. Review the model or rule before changing it.
2. Confirm the rule is scoped correctly to the right tenant or entity model.
3. Test changes carefully before broad rollout.
4. Monitor the impact on cases and scores after publication.

## Typical administrator workflow

- Start in Rules or Model Configuration when a new fraud behavior needs to be introduced.
- Use the relevant rule type to define the condition and outcome. Example: create an activation rule when you want a case to open for specific transactions.
- Validate the logic carefully before enabling it in a live environment.
- Review the resulting scores and cases after the change is published. Example: if the new rule is intended to increase review volume, confirm that the expected cases appear.

## Screen walkthrough

### 1. Open the configuration area

Use the Fraud & AML navigation to reach the Rules or Model Configuration pages.

### 2. Review the rule context

Inspect the rule or model definition, including the condition, action, and any supporting data references. If the UI opens a side panel or modal from a rule entry, use that view to review the full definition before editing.

### 3. Publish changes carefully

After testing, publish the change and monitor downstream outcomes in Scores and Cases. If a configuration change affects scoring or case creation, return to the relevant list view to confirm the impact.

## Screenshot reference

The relevant areas are:

- Model Configuration: http://demo.ctrmv.com:4010/admin/fraud/model-config
- Rules: http://demo.ctrmv.com:4010/admin/fraud/rules

## Notes

This area is the operational control center for fraud policy. Changes here directly affect how transactions are scored and how investigations are triggered.