Configurable Workflow Engine
Per-tenant state machines, assignment rules, notification rules, document generation — all configured via WorkItemManagerConfig without code changes.
Key benefits
- · Allowed state transitions configured per tenant
- · Assignment rules route claims to individuals, org units, or round-robin
- · Notification rules trigger email, SMS, in-app alerts
- · Document-generation rules auto-fire letters on state changes
- · ShortName number formatting configurable (VC-2025-0142 vs VC-20250142)
Why configurability matters
Every state runs its victim-compensation program slightly differently — review cadences, approval authorities, documentation requirements, number formats, notification preferences. A platform that hard-codes any of these forces programs into an “almost-right” workflow forever. VCPMS makes workflow rules data, not code.
What WorkItemManagerConfig drives
- State transitions. Which states a WorkItem can move to, from which states, under which conditions.
- Assignment rules. Who gets assigned when a state changes — individual, org unit, round-robin, load-balanced.
- Notification rules. What email / SMS / in-app alerts fire on state changes or assignments.
- Document generation. Which letter templates auto-generate on state changes.
- ShortName format. Human-readable identifier pattern (VC-2025-0142, etc.).
Per work-item type
Each of the 40+ work-item types in VCPMS — VcClaim, FrClaim, SafeClaim, Payment, Award, DeterminationDocket, Offender, and more — has its own WorkItemManagerConfig. Every configuration is tenant-scoped; Oklahoma and Maine can run the same WorkItem with different rules.
No deploy needed
Changes to workflow configuration take effect on save. No code change, no release, no restart.