How do I deactivate the Edit Feature function after I make an edit in Web Experience Builder?

[CPaulman]

Hi - 

My users are drawing polygons in the map in Web Experience Builder. We have noticed that once they make an edit to the feature geometry, they cannot deactivate the edit "mode".

Workflow:

In a Web Experience Builder App with a polygon feature class (attributes and geometry editable) in the web map, 

1) Click on the Edit Widget

2) Highlight Select under Edit Features

3) Click on a polygon feature and edit the geometry

4) Click "Update"

5) Click Back in the Edit Feature widget "<"

6) Clear the highlighted feature (clear selection in map frame)

7) Close the Edit Widget

😎 Click on another polygon in that editable hosted feature layer. 

*****AHHHHH!!!!***** 

This is where I would expect the popup window to open and the feature to highlight. 

***Instead, I get the orange box around the feature. And I can move or edit it! This is not what I want.***

I would appreciate any help: How do I deactivate the "Edit Mode" so that my users can go about viewing popups without fear of moving their polygons around?

[lah]

Does this include Enterprise 11.3 or just AGOL?

[jmfr236]

After you open the edit widget from the widget controller and then close, the editing feature persists. Would like an option to disable editing if the widget is not open/active. 

[ZachBodenner]

I agree, there should be multiple ways to disable editing. Have you posed this as an idea yet? If so I'd like to Kudo it.

[MarianaCalabrese]

How about having the edit mode not activated no matter where the edit widget is placed? Some consistency would be greatly appreciated. This limits how the edit function can be placed into templates and goes against the configurability that experience builder is supposed to offer.

[JWatkins]

Having it in the widget controller works well when the experience first opens, though once editing has been activated from the widget controller it remains functional even once the widget controller pane has been closed. Are you able to add a manual on/off button like you have with the Swipe widget to allow users to disable editing when they don't want to use it?

[CaseyWilson1]

We are on Enterprise 11.2 and we are still having this issue.

[EdwardMcFarlin]

The editing experience using the edit widget in Experience Builder is not ideal. I much prefer the experience of the editor in the Map Viewer than Experience Builder.

In Experience Builder after updating a feature, the edit form stays open on the selected feature, so the user needs to back out of the selection. In Map Viewer, the edit tool automatically goes back to the previous view (either the multiple records selected or the main edit view) after updating a feature and the edit tool stays active. In Experience Builder after updating a feature, the user needs to back out of selection and then re-select the edit tool every time. Also, if you try to back out of the edit form, it asks if you want to discard your edits, even if you already made edits and submitted them. This is really annoying if your workflow is making lots of edits and requires several extra clicks between each edit.

In addition to the above frustration when the edit widget doesn't unselect the record after it is submitted, if there is a filter on the layer that would cause the record to be filtered out of the map, the edit widget will just spin forever and the user needs to refresh the entire app and navigate back to where they were to make another edit. So, trying to change an asset from "active" to "retired" for example to remove it from the map is deeply frustrating and seems like a bug.

My organization recently upgraded our ArcGIS Enterprise portal to 11.3 and it seems like the edit widget experience in Experience Builder has gotten worse. Hopefully my organization will install the Web Editor app soon so I can see if that is a viable alternative.

[ZachBodenner]

To all of those who build custom widgets, it seems like it should be possible to tweak the widget so that it deselects after backing out of the edit form. Has anyone tried that? I've never built my own widgets so I honestly have no idea, but it feels like it should work.

[coryeicher]

We are pursuing this avenue. Once you have 1 custom widget (we are in this boat), you are in a place where you can listen for events, such as when the Edit widget closes. I know how to do this specific "listening". I would definitely be open to hearing from Esri @AlixVezina  on what logic I should then implement to deactivate editing

for us, deactivation would be equivalent to going back to no widgets active on this widget controller... and no lingering tools or state still active. we'd also be happy returning to a zero state where the default/hidden MapView pan/zoom/popup tool is active.

thanks if you can point me in the right direction. 

. which specific tool should I deactivate or state should I change? 

[RVRAdmin]

It's March 2025 and I'm still getting this behavior, even though the Edit widget is in a Widget Controller. Once I have opened the Edit widget, and closed it (and opened a different widget), a polygon is activated for geometry editing whenever we click to get a popup.