workflow Available
Dynamic Forms Engine
Tenant-authored NGX-Formly JSON schemas publishable to any portal — programs build their own data-collection forms without code changes.
Key benefits
- · NGX-Formly schema-driven forms, tenant-authored
- · Publishable to any combination of portals (VBO, VCA, SPA, ADV, LEA)
- · Token-secured invitations link to the right user without login friction
- · Versioned instances tracked as responses
- · Drives the generic UserRequest workflow when a form requests something
The problem this solves
Every state program needs custom data-collection forms — intake addenda, satisfaction surveys, provider credentialing questionnaires, conditions-of-award attestations. Without a form engine, programs either wait for a developer to build each one or fall back to paper. Both are friction.
What VCPMS provides
A tenant-authored form engine:
- Schema. NGX-Formly-compatible JSON describes fields, validation, conditional logic.
- Per-portal publishing. A form can be published to VBO, VCA, SPA, ADV, LEA — any combination.
- Versioning. Each schema is a versioned template; instances record which version a respondent saw.
- Token invitations. Staff invite a specific user (or external email) to fill a form. The invitation link carries a one-time token — no login friction for external recipients.
- Responses.
DynFormInstancecaptures every response against its parent WorkItem (claim, payee, etc.). - User Request workflow. When a form requests something — “I want to request X” — it produces a
UserRequestthe back-office processes.
No deployment
New form today, used tomorrow. No developer ticket, no deploy, no release wait.