Block versioning

Platform: Portal

Archer keeps a version history of every block's geometry. This prevents accidental edits from disrupting field work already underway, and gives you a clean way to change block mapping without losing the history of what was there before.

The three statuses

Every block version has one of three statuses:

Draft — in-progress. Not visible to field devices for operational work. Use drafts to capture or revise a boundary without affecting live work.
Released — the live, operational version. This is what mobile devices and terminals use.
Deprecated — an older released version that has been superseded by a newer release.

At any time, a block has exactly one released version (or none, if it's never been released yet) and zero or more drafts and deprecated versions in its history.

When a new version is created

A new draft version is created automatically when you:

Map a new block from the mobile app (the first capture is always a draft).
Re-capture or edit the boundary of an existing block.

Attribute edits (name, variety, notes) don't create a new version — they update the current one in place.

Releasing a draft

Releasing a draft makes it the version field devices will use.

In the portal, open Manage → Vineyards and choose the vineyard.
Find the block in the list. Blocks with pending drafts are marked so you can spot them.

📷 Screenshot: Block list with an "Has draft" indicator next to a block.
Open the block and select the draft version you want to release.
Review the draft — boundary, variety, and any attributes.
Click Release.

📷 Screenshot: Block version detail view with a Release button.

When you release, the previously released version (if there was one) becomes deprecated.

Rolling back to a previous version

If a release introduced a problem, you can roll back by re-releasing an earlier version. Find the version in the history, open it, and click Release again. This creates a new released version that's a copy of the older one.

Tips

Don't leave drafts lying around forever. If a draft exists, field staff may assume it's the intended new boundary. Either release it or discard it.
Coordinate releases with operations. If a crew is actively spraying against a released version, releasing a new one mid-run can surprise them. Best to release outside of active work windows.
Deprecated versions are kept for history, not for work. They'll still show up in reports for past operations, which is how you answer "what did the block look like when we sprayed last month?"