Drafts and version history
Every change starts as a draft. You test it, a person publishes it, and every published version is kept, so you can go back.
- DraftDiscard
Claims over $10,000 need a second approver.
- PublishedIn use
Ask the claimant for photos before review.
- Earlier versionRestore
Send the adjuster a form instead of an email.
- Earlier versionRestore
First version.
Runs that started on the published version finish on it.
Changes start as drafts
Editing doesn't touch the live version. Runs keep using the published one while you work.
Test it first
Run the draft end to end, the way a real user would. You choose whether the test really changes things in your other apps.
A person publishes
A change goes live only when someone publishes it, even one the reviewer suggested.
Runs finish on their version
A run in progress stays on the version it started on. Only new runs use the new version.
See what changed
Each version has a plain-language summary of what changed.
Go back in one step
If a change doesn't work out, restore an earlier version.
For example
An operations lead tightens an approval rule in a draft and runs a test claim through it before publishing. A few weeks later the team decides the old rule worked better, so they restore the previous version. Claims already in progress finish on the version they started on.