MENU
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
Scenario Overview:
The organization has ArcGIS Enterprise and requires versioned editing.
The project mandates tracking which user deleted a feature from the default version.
Why Branch Versioned Editing?
Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions. (ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers).
Option C: Nonversioned editing does not support versioning workflows or user tracking.
Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.
Currently there are no comments in this discussion, be the first to comment!