Change impact
See what depends on a rule before you change it.
The expensive failures are rarely in the line that changed. They are in the system three teams away that quietly depended on the old value.
What change impact shows
Before a rule changes, AppThentic shows:
- Every location of the rule: services, configs, jobs, help pages and contracts.
- What depends on it: other rules, reconciliations, reports and downstream services that assume its current value.
- The approved reason, and whether the change still respects it.
- The owner, who should be part of the decision.
Example
A product manager wants refunds to move from 30 to 45 days. Change impact shows five dependants. One of them, the daily finance reconciliation, assumes every refund settles within the payment partner’s 35-day chargeback window. At 45 days it would break. The approved reason says exactly why 30 was chosen.
The change can still happen. It happens with Finance in the room, and the reconciliation changes with it.
Where to see it
- In AppThentic, from the rule’s page.
- In pull requests that touch a known rule.
- In AI coding tools, before the assistant edits the code. See AI coding tools.
See the Product tour for this change step by step.