QA evidence
Record testing evidence against the exact revision, keeping the person recording evidence distinct from the external approver.
RELEASE WORKFLOW
Bring QA, UAT, independent approval, scheduling, and recovery into an explicit form-release journey.
The V2 demo demonstrates the governed release journey. Customer Production deployment remains subject to qualification.
Record testing evidence against the exact revision, keeping the person recording evidence distinct from the external approver.
Promote the tested package into UAT and record its approval before requesting Production.
The normal Production requester and approver must differ. Role eligibility does not bypass separation of duties.
Review local date, time zone, and the resulting publication instant alongside effective-date guidance.
Changing a package or schedule replaces the request and invalidates its previous approval.
Needs-attention findings identify the problem, responsible role, remedy, and supported recheck path.
The history of what happened stays intact even when the current release changes.
See the current stage, next action, actor, role, time, reason, retries, approvals, and release outcomes.
The model offers the last three eligible prior Production releases—not the last three uploads—and restores a complete package.
Authorization, current state, and compatibility checks decide whether a prior release is a valid target.
The later V2 refinement bundles compatible metadata and exact form revisions. Its production and recovery validation remains pending.
An explicit release portfolio separates active and historical work and avoids overlapping release trains.
Freeze the schema and affected form revisions together so environment activation does not expose a partial combination.
Restore a compatible prior bundle without restoring the whole database; stale candidates need withdrawal or revalidation.