ParcelDraft Workflow

Use ParcelDraft workflow for all ordinary parcel changes. Official Parcel versions are read-only in normal operations.

Roles and actions

  • Editor: create draft, update draft in DRAFT, submit, cancel before approval.
  • Reviewer: review-accept (SUBMITTED -> REVIEWED), reject from SUBMITTED, cancel from SUBMITTED or REVIEWED.
  • Approver: final-approve (REVIEWED -> APPROVED), reject from REVIEWED, cancel from REVIEWED.
  • Viewer: read-only access.

Actions depend on both dataset role and current draft state.

Standard flow

  1. Create a draft from the current official parcel version (or as a new chain).
  2. Edit draft geometry/attributes while state is DRAFT.
  3. Submit draft (DRAFT -> SUBMITTED).
  4. Reviewer accepts (SUBMITTED -> REVIEWED) or rejects.
  5. Approver final-approves (REVIEWED -> APPROVED) or rejects.
  6. Final approval creates a new official Parcel version.

State model

  • Active states: DRAFT, SUBMITTED, REVIEWED
  • Terminal states: APPROVED, REJECTED, CANCELLED
  • No transitions are allowed from terminal states.

Important rules

  • Only one active draft is allowed per (dataset, version chain).
  • Rejection requires a reason.
  • Approved/rejected/cancelled drafts are not editable.
  • Final approval fails if the draft source version is not the current official version anymore.

History and audit

For each draft you can view:

  • draft metadata (created_by, submitted_by, reviewed_by, approved_by, etc.)
  • ordered workflow events with per-draft sequence numbers
  • linked resulting official version after approval

This supports full reconstruction of who did what and when.