# Page: Rule and Code Builder

## Purpose

This page explains how the rule and code builder is used to configure logic for fraud and AML behavior inside the application.

## What the builder is used for

The rule and code builder is used when administrators or advanced users need to define:

- decision logic;
- rule conditions;
- score influences;
- model-related parameters;
- custom expressions or scripts.

## Typical building blocks

A builder usually includes:

- rule name or label;
- conditions or expressions;
- action or outcome definition;
- validation or execution logic;
- save and publish actions.

## Example usage

Example: an administrator creates a new rule that increases risk when a transaction comes from a high-risk country and exceeds a certain amount. The rule is then tested and applied to future decisions.

## Recommended workflow

1. Define the objective of the rule.
2. Add the required conditions.
3. Review the resulting logic for clarity.
4. Save the rule.
5. Test or validate the effect before full deployment.

## Operational cautions

- review rules carefully before activation;
- avoid overly broad conditions;
- document the purpose of each rule for future maintainers.

## Notes

The rule builder is powerful, but it should be used carefully. Poorly defined rules can change review outcomes and create false positives or missed detections.