Select to view content in your preferred language

Introducing the Web Editor (beta) Template

418
2
06-30-2025 09:52 AM
ShareUser
Esri Community Manager
0 2 418

We’re excited to introduce the Web Editor (Beta) Instant Apps template — a powerful tool designed to simplify and streamline data editing workflows for both GIS professionals and non-GIS users alike.

With this template, you can create a tailored version of the Web Editor application, enabling focused, efficient editing experiences. Whether you're managing spatial data or supporting field teams, the Web Editor helps you configure the right tools for the job.

Getting Started

To use the Web Editor template, you’ll need a web map that includes at least one editable feature layer. You can access the template from the Instant Apps home page or directly within the Web Editor interface. Please consider joining the Early adopter community to provide feedback on the Web Editor template.

SarahMcDonald_Esri_0-1750872059403.png

 

Configuration Options

The Web Editor template offers a wide range of customizable settings, grouped into intuitive categories:

App Details - Introduce your app and guide users with:

  • Header and Title
  • Introduction Window

Editing Tools - Fine-tune the editing experience by selecting which tools are available:

  • Feature Editing
    • Edit vertices, split, merge, move, reshape
    • Copy/paste features
    • Undo/redo
    • Create or delete features
  • Selection Tools
    • Choose selectable layers
    • Select by attributes
  • Snapping Tools
    • Define snapping layers
    • Enable snapping to grid
    • Show tooltips

SarahMcDonald_Esri_1-1750872059449.png

 

Map Interactions - Enhance map navigation with:

  • Home button
  • Zoom controls
  • Search functionality

Side Panel - Empower users with tools in the sidebar:

  • Layer Tools
    • Layer list, tables, basemap switcher, legend, bookmarks, shortcuts
  • App Defaults
    • Directional pad, map rotation, default units, delete confirmation prompt

SarahMcDonald_Esri_2-1750872059501.png

 

Theme & Layout - Customize the look and feel:

  • Light or dark mode
  • Preset themes
  • App logo

Tailor to Your Workflow

With these flexible configuration options, the Web Editor template can be adapted to support a wide range of editing workflows — from simple data updates to complex spatial edits. 

SarahMcDonald_Esri_3-1750872059534.png

 

 

2 Comments
RPGIS
by MVP Regular Contributor
MVP Regular Contributor

Just out of curiosity, what is the overall direction for esri regarding web editing capabilities? For as long as I can remember, web editing started out:

  1. The classic web map, Geoform, and a couple of others which I can vaguely remember.
  2.  Web App Builder, when it came out, has( or had) the editing widget which made it easier to configure editing using a simple web app like UI
  3. Map Viewer replaced by the classic web map by which Web App Builder had support and enabled editing
  4. Experience Builder is replacing Web App Builder and allows for web editing using a similar UI to Web App Builder.
  5. Floor Plan Editor for Enterprise Portal (11.2 - Current) also enables web editing.

 

So I just a few questions.

Is the purpose of this new web app designed to be a friendlier UI in terms of editing in the web, and what would the potential road map look like considering it could potentially replace several other web maps that also have editing capabilities?

Will arcade be supported by this new web app or will that capability exist only in field maps or as attribute rules?

LarryYoung
Esri Contributor

Hi RPGIS,

I'll try and answer your questions, using some of the text from a similar conversation on a different thread.

First off, much time and thought goes into whether to augment existing applications or create a new application (Web Editor, in this case).  In the end we decided a separate application was best and i'll give you two main reasons:

  1. Creating a focused app - by creating an application just for editing it gives us the ability to streamline workflows for that purpose.  If you create a single app to do everything, then you have to genericize some process as a result.  An example would be the toolbars across the top of Web Editor which are context based knowing the user is editing.
  2. Configuration - In a future release (out in beta in the June Online release) we will support configuration of  Web Editor to further support streamlining workflows.  For instance, you could configure Web Editor to support only updating attributes and save that as an instance of the application.  If the editing capabilities are rolled into Map Viewer, then the options for configuration are reduced if not eliminated.

Hope that helps.  Also worth noting much of the functionality of Web Editor will make its way into web components that will be available in Experience Builder and Map Viewer at the discretion of those teams and in the context of those applications (i.e., does it make sense for the application and its purpose).

As for the road map of Web Editor, we will continue to add new functionality based on user feedback and needs.  In addition to the configuration capabilities mentioned above, we plan to support things like true curves, annotation, dimensions, parcel fabrics, topology, reconcile and posting of versions, etc.  These things will obviously take time to add, but the overall direction for Web Editor is to make it a full function editing application on the web.

Arcade can already be used within Web Editor when part of attribute rules and other capabilities (symbology, for example).  We also plan to look into using Arcade as a way to extend the app itself.  Did you have something in mind when asking about Arcade in Web Editor?

Thanks, larry

Labels