A distributor changed the agreed fee. The rule has to be adjusted today, without stopping tomorrow’s reports from being validated.
And if the change wasn’t right, there has to be a way back without redoing anything.
What you write
«Change the inspection fee rule: for Distributor B it’s now 95,000. Test it before saving.»
And then
- «Show me this rule’s version history.»
- «Go back to the previous version.»
Why it matters
-
Every change is tested
Changing the condition requires simulating again. The assistant works on the version it read: if someone changed it in the meantime, it doesn’t overwrite it.
-
Every version is kept
The history shows the rule’s versions. Restoring one creates a new version; nothing is lost.
-
Adjusting isn’t reactivating
Editing a rule someone switched off doesn’t turn it back on. Activating it is still a separate decision.
The engine flags and the person decides. Rules only run when they’re active and linked to the form. How they’re configured
Rules change with the business. What matters is that every change is tested and recorded.
