Validation rules and routing decisions
Updated 19/11/2026
Validation determines whether inputs are acceptable; routing decides who should work on valid requests. Keep the policies distinct so a routing fallback does not conceal invalid data. Server-side validation remains necessary when forms also validate input.
Business rules express policies independently of individual screens. A decision table evaluates structured combinations of conditions. A decision tree makes a sequence of branching decisions explicit. A when rule expresses a reusable true-or-false condition. Keep inputs, outputs and boundary behavior explicit so business stakeholders can review the policy.
Reject non-positive amounts before routing. Then route valid amounts around a threshold and verify that the boundary uses the intended comparison.
Return to curriculum