How to implement multi-level editing workflow in ArcGIS

Question

Hi everyone,

I’m working with a React ArcGIS application and need to set up an editing workflow.

* When an Editor makes changes, those edits should not immediately update the final data.

* Instead, the edits should go for Admin review.

* Only if the Admin approves should the updated data be visible to all users.

* If the Admin rejects, the layer should continue to show the previous data (as if no edit was applied).

Is there a recommended approach in ArcGIS for handling this type of process.
Any guidance, best practices, or examples from others who have solved this type of workflow would be very helpful.

Sage_Wall · Answer

Hi @CharanpreetKaur ,

Sorry for the late response I've been out on vacation.  There shouldn't be any sort of data loss unless something is misconfigured or there is a bug. I'm not really a versioning expert and wouldn't be a qualified person to help debug what may be happening.  If your having issues with the documented versioning and reconciliation process I'd suggest getting help from technical support.

CharanpreetKaur · Answer

Hi @Sage_Wall ,
Just checking in to see if you had any updates or additional thoughts on my query regarding versioning and data loss during the merge process. Your guidance would be greatly appreciated.

CharanpreetKaur · Answer

Hi @Sage_Wall,

Thanks for pointing me towards versioning and the Version Management Service. I did try this approach - setting up versioning so that editors make changes in their own version and then the admin merges those changes.

The issue I’m running into is that during the merge process there seems to be data loss. Is there a way to prevent this?

Also, are there any other recommended approaches we should explore apart from traditional versioning.