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 inDRAFT, submit, cancel before approval.Reviewer: review-accept (SUBMITTED -> REVIEWED), reject fromSUBMITTED, cancel fromSUBMITTEDorREVIEWED.Approver: final-approve (REVIEWED -> APPROVED), reject fromREVIEWED, cancel fromREVIEWED.Viewer: read-only access.
Actions depend on the current draft state and an exact dataset role. Approver does not imply Reviewer or Editor for mutations, and Reviewer does not imply Editor.
Standard flow¶
- Create a draft from the current official parcel version (or as a new chain).
- Edit draft geometry/attributes while state is
DRAFT. - Submit draft (
DRAFT -> SUBMITTED). - Reviewer accepts (
SUBMITTED -> REVIEWED) or rejects. - Approver final-approves (
REVIEWED -> APPROVED) or rejects. - Final approval creates a new official Parcel version.
A source-version draft may be saved without changes while an editor is working, but it cannot be submitted until at least one authoritative parcel attribute or its geometry materially differs from the source version. Geometry uses the database-backed parcel topology tolerance so storage/display CRS round trips do not become false changes. Notes, workflow timestamps, and snap provenance do not count as parcel changes. The submission service checks this invariant against the source row inside the locked database transaction; the browser also withholds the submit control and explains why it is unavailable.
Draft geometry can also be edited in QGIS without changing this workflow. See Edit parcel drafts outside LandWeave.
Attribute changes and boundary editing¶
The browser drawing tool supports parcel boundaries with 3 to 500 vertices. If two editors open the same parcel, the first save records the draft. A later save from the stale form displays a conflict and keeps the second editor's input on screen. Leave that tab open, follow Review current draft in a new tab, and reapply the changes you want to keep to the current version.
Changing attributes on an ordinary parcel update preserves the exact stored boundary when you have not edited its geometry. For a first draft, that boundary comes from the current official parcel. When reopening a saved draft, its own boundary is retained, including earlier deliberate edits and saved new-chain drafts with no official source. Repeated Save Draft and reopen cycles do not move coordinates. This also works when the drawing controls fail to load.
Panning, zooming, inspecting coordinates, changing label precision, and confirming an edit without moving a vertex do not change the boundary. Cancelling an edit session restores the geometry and snap bindings from the start of that session.
Dragging, redrawing, applying a coordinate, nudging by a centimetre, or confirming a snap or traced boundary remains a deliberate edit. The server validates it in the installation's storage CRS and resolves snap and trace coordinates against the current authorized targets. Unedited vertices and interior rings retain their available precision during a partial edit; converting an edited polygon between display and storage coordinates can still introduce very small projection residuals. Existing overlap limits remain in force. Later attribute-only saves preserve that edited boundary exactly.
A small coordinate edit can be saved even when it is too small to count as a material geometry change for source-version submission. Such a draft still needs a qualifying parcel attribute change or material boundary change before Submit is available. Notes and binding changes alone do not qualify. New-chain drafts retain their existing submission rules.
Recovering an unsuccessful edit¶
Correct invalid attributes and retry using the retained form. Invalid or deleted geometry must be corrected or redrawn; saving cannot silently substitute the old boundary. If saved geometry has an invalid CRS, it is not displayed as editable coordinates. The existing validation message remains available.
If the saved boundary or an authorized snap target has changed since the form opened, reload the current draft and targets, then repeat or explicitly correct the edit. Pending or failed snap work must finish or be resolved with the existing retry/keep-unsnapped controls before saving. Cancelling an edit prevents its late responses from changing the restored geometry.
These checks do not change workflow permissions, actor separation, overlap advisories or transition restrictions. Rejected saves retain the previous stored draft; ordinary saves never change the official parcel. This correction prevents drift on future saves. It does not repair historical drift or authorize historical data changes. Any such repair or data-changing rollback needs separate owner authorization and must preserve official records and audit history.
State model¶
- Active states:
DRAFT,SUBMITTED,REVIEWED - Terminal states:
APPROVED,REJECTED,CANCELLED - No transitions are allowed from terminal states.
Important rules¶
- The creator or submitter cannot review their own draft.
- The creator, submitter, or reviewer cannot give final approval.
- Another eligible person must perform each decision stage.
- Cancellation is role-based; an eligible non-owner may cancel an active item.
- 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.
- Draft saving remains available when overlap notices exist. Yellow identifies expected source overlap, blue identifies permitted legacy overlap, orange identifies another draft, and red identifies a blocking authoritative or reserved-area conflict.
- Submit and review recompute current evidence. Final approval also checks every authoritative validity interval that would coexist with the new parcel version.
- Select an overlap notice to zoom to the affected area. Conflict overlays are independent of surrounding-parcel visibility and never move or repair draft geometry.
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.
Act on a selected set of drafts¶
On Workflow Tasks, select ordinary parcel drafts in the active dataset. The set may include manually created drafts and drafts from different uploads. Selection is preserved across pages and display modes; changing membership filters or the active dataset clears it with a notice. Select all, with the intended stage chosen, selects eligible drafts across every matching page. Deselect all clears the entire selection. Show all matching drafts changes display only, reports progressive loading and preserves selection when you return to pagination. Interrupted loading is not a complete list.
Display-based sorting (parcel, task, state or action) supports up to 10,000 matching rows by default. Above that boundary, narrow the filters or choose a timestamp sort. This display limit does not cap Select all or acknowledged actions.
Choose the action allowed by your exact dataset role:
- Editor: Submit selected, from Draft to Submitted.
- Reviewer: Accept selected for final approval, from Submitted to Reviewed.
- Approver: Approve selected, from Reviewed to Approved.
The existing separation rules still apply, including when you hold several roles. The confirmation lists the exact draft identities, presented revisions, selected and eligible counts, and known exclusions. Examine the parcels in the tool or externally, then check the initially unchecked examination acknowledgement. Export for checking is optional; a download does not acknowledge examination or advance a draft. Changing the selection or action discards its confirmation.
Confirm records that stage-specific acknowledgement and advances eligible unchanged drafts individually through the usual validation. One confirmation authorizes only the named stage. Final approval creates the official version through the existing parcel workflow.
Outcomes distinguish completed, skipped, failed and unfinished items. A draft changed since confirmation is skipped and needs fresh examination and a new selection. Validation failures stay available for individual handling; other eligible drafts continue. Skips and failures are terminal for that selection and are not silently retried. Counts include known exclusions and account for every confirmed identity. Individual links appear only while access remains available.
If processing is interrupted, reopen Workflow Tasks and choose the receipt under Previous selections. Merely opening the page reads outcomes and performs no transitions. Continue unfinished explicitly resumes eligible, unchanged work from that receipt. It does not repeat completed transitions or retry terminal skips/failures, even when the earlier response was lost. Current permissions are checked for every item; an old acknowledgement does not preserve revoked access.
Each advanced draft retains its own actor, timestamp and history. Final approval links both the approval event and official-version event to the same receipt. Expand Bulk selection in the existing Workflow Events table to see the recorded acknowledgement and receipt identity. The original actor can open its outcomes. Deleting an underlying draft later preserves the receipt's historical result and counts, while its individual link and ordinary draft history become unavailable.
If an item reports loss of the required stage role, automatic processing stops. That skipped item remains terminal; other unfinished items remain unfinished. After access is restored, read the outcomes and explicitly continue unchanged unfinished work. A changed, skipped or failed draft needs a fresh selection and examination acknowledgement before another attempt.
Changing the active dataset, disabling the account or deactivating the original dataset stops execution. The original actor can still read personal historical receipt counts and opaque draft identities when dataset visibility is lost, provided the account remains active. Draft links are hidden until the original dataset is active, selected and accessible again. Previous selections keeps personal receipt summaries for datasets that are no longer accessible, including when the application switches to another accessible dataset. Receipts in other accessible datasets remain scoped to that dataset. Reading these summaries never restores permission or resumes processing.