What this form does
This page creates one monthly-limit rule. Operators use it when a new deposit-count, deposit-amount, or fallback monthly-limit rule must be added.
Visible fields
From DepositTo DepositTotal Deposit Amount (EUR)Monthly Limit (EUR)Is ActiveDo Not Use Deposit CountDo Not Use By Amount
Important behavior
The create form can disable either matching branch
- with both
Do Not Useswitches off, the rule uses deposit count and amount together Do Not Use By Amountmakes it count-onlyDo Not Use Deposit Countmakes it amount-only- enabling both makes the create form behave like a universal rule with no deposit-history gate
Is Active is shown in FE, but current create backend does not persist it
The create page exposes an Is Active checkbox, but the verified create backend currently saves only:
fromDeposittoDeposittotalDepositAmountmonthlyLimitdoNotUseDepositCountdoNotUseByAmount
Operators should not rely on the create-time Is Active toggle as a persisted backend flag.
Because the stored model defaults new rows to active, treat new rules as active after create unless they are disabled later from the list.
Validation is presence-only in this flow
The frontend marks the four numeric fields as required, and the backend also requires those values. The verified create flow does not add range, non-negative, overlap, or ordering validation for the count and amount thresholds.
Save flow
Createsubmits the current form draft.- On success, the page shows a success toast, resets the form, and returns through browser history.
- On failure, the page shows a generic failure toast and stays on the form.
Cancelreturns through browser history without submitting.- The backend create action is authenticated and audit-tracked, but the separate permission middleware is commented out in the verified route.