Latest Contributions by LarryYoung

The release of Web Editor came at an unfortunate time as it was in the middle of the updating of user types and the combing of GIS Professional Basic with Creator.  With Enterprise 11.3 you will not be able to use Web Editor without at least a GIS Professional Basic user type.  With the Enterprise 11.4 release this drops to a minimum of a Creator user type. Hopefully that helps. Larry Young Esri Product Management ... View more

@mthompson if basic editing workflows are all you need on the web, then I would suggest using MapViewer or an Experience Builder app with the editor widget.  Both would offer basic editing workflows with a Contributor or Mobile Worker license.  Things like batch attribute update and ability to use group and preset templates will be coming to those environments too in 2025. We are continuing to review the licensing requirements around Web Editor.  Thanks for the feedbakck. ... View more

Hi Jeffrey, Interesting idea given the changes you noted on the web side when moving from 11.3 to 11.5, but i'm afraid that's not something we can support.  We don't want to start down the path of releasing new software on older versions of Enterprise, as that creates more test environments, etc., which further spreads out resources that could stay focused on the current releases. thanks, larry ... View more

Yes, Web Editor can use shared templates (templates in the database) today.  The plan for the other web applications is to add support in 2025.  Pro 3.5 will be needed in order to write templates to an Online database, so hopefully the capabilities for other apps will be available with Enterprise 11.5 and the Online release around the same time.   ... View more

Hi, Sorry for the slow reply. This AddIn is one of the initial aspects of sharing editing templates (including group and preset) through a set of tables in the geodatabase.  Once the templates are written to the tables, web clients (such as the new Web Editor with an early September 2024 release on Enterprise 11.3)  will be able to use those templates.  Future releases of the Editor widget in the Maps SDK for JavaScript will also be able to use the same set of templates from the database.  As will Experience Builder, Instant Apps and Map Viewer as they all use the Editor widget. Once the templates are in the database authors can create web maps that point to the layers the editing templates are for.  The clients (Web Editor, etc.) will show the templates from the database in the add feature dialogs. larry ... View more

Hi All, I'm told the potential work around for this is to go ahead an enable the Version Management Service, but then after the service is published go to Server Manager > Services > Capabilities > select Version Management and uncheck all Operations allowed. Give that a try.  It is something we want to address in Pro at some time, but the concern is over the potential unexpected ramifications.  larry       ... View more

Hi All, Again, appreciate the comments and feedback.  The mobile worker collecting data in the field and then coming back to the office to clean it up is not a workflow we had considered with Web Editor, so we will take that under consideration.  What i've heard mentioned in that context is simple geometry updates, along with bulk attribute updates.  Those capabilities should be possible with Map Viewer or the Editor widget in Experience Builder in the next release or two.  We are in the process of designing bulk attribute updates now. As for the road map of Web Editor, think in terms of Pro editing capabilities as we will move in that direction with all the editing tools for extend/trim, replace geometry, copy parallel, vertex editing dialog, etc.  Also a lot of work planned around shared edge editing and topology, and more capabilities for parcel management and utility networks.  Additionally we have plans to support creating and saving application configurations with Web Editor to allow the creation of more streamlined applications for specific workflows.  Web Editor will be the premier editing application on the web. thanks, larry ... View more

Hi All, Thanks for the feedback on this topic.  We put a lot of thought into the user type requirement for Web Editor, but are receiving a lot of responses based on the decision.  The basic thinking is we will offer much more with Web Editor than we have before for editing on the web which translates into a higher license requirement. As we consider your feedback, was wondering if you could elaborate on why you are advocating for mobile worker as the minimum user type for Web Editor?  Is the plan to have your users edit in the field with Field Maps and then come back to the office and clean the data up with Web Editor?  The expectation is not to use Web Editor in the field on a phone is it? Thanks, larry   ... View more

Hi All, First off, much time and thought went into whether to augment existing applications or create a new application.  In the end we decided a separate application was best and i'll give you two main reasons: 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. Configuration - In a future 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 (i.e., does it make sense for the application and its purpose) and in the context of those applications. ... View more

Please bear with us with Web Editor as this is the initial release.  There is a lot more editing functionality still to come including things such as auto-complete. One of the advantages of Web Editor is that it is a focused application specifically for editing.  As i mentioned in an earlier post, if we start adding additional functionality not specific to editing, then we over complicate things for those just looking to edit.  Not all organizations have the same workflows and personas within their organization, so we believe the simplified editing experience we can create with Web Editor is appropriate on the web as opposed to a single do everything application. Experience Builder is designed to allow organizations to create applications targeting the specific workflows they need to address.  These workflows can include editing, geoprocessing, etc.  The workflows you can target with Experience Builder can be very specific hence the need for a large variety of widgets including editing. We are aware of the need for similar capabilities within the Edit Widget for Experience Builder as what users are accustomed to with WebApp Builder and the Edit, Smart Editor, and Batch Attribute Editor widgets.  Expect those capabilities to be available with the Edit Widget and possibly other widgets for Experience Builder in the next release or two.   ... View more

Thanks for the input.  We've put a lot of thought into capabilities like this.  We realize the number of steps involved in adding a layer and similar processes.  Web Editor is meant to be a focused editing app, though, so the moment we open the door to that type of functionality you have to ask about changing symbology, defining the Feature Form and popup, etc.  Start adding too much and you complicate the editing experience. We will most likely support adding layers in a later release as part of the configuration process, but as with other topics, waiting for more feedback. ... View more

Hi,  It is true the utility network is not yet fully support in offline workflows for editing purposes, but we do plan on having that in place by the end of 2024. That said, there are many different levels to your workflow and i strongly suggest you begin with your Esri partner coordinator or sales manager for a more in depth discussion.   Once you go offline, what do you plan to edit with?  Are you going to try and use FIeld Maps, a custom Maps SDK application, or a partner solution?  Field maps has editing capabilities, of course, but not at the level you are talking about for utility networks.  Some of that will also come in the future, but may not be enough for your requirements. Sync and taking data offline in general can support taking subsets of the data offline, but again you have to wait for full support of the utility network in that capacity.  If you leave out the offline part, we've seen organizations implement restricting work in certain areas through SOE/SOIs and/or attribute rules. One good source for utility network info is here:  https://www.esri.com/en-us/arcgis/products/arcgis-utility-network/resources.  Click on the blogs link to find blogs on offline, etc. thanks. ... View more

Hi @JimmyBowden  The check for a UTE license was removed from the trace call on the Utility Network Service with ArcGIS Enterprise 11.2.  Depending on what client you are using, you should now be able to trace without a UTE as long as you move forward to ArcGIS Enterprise 11.2. thanks, larry ... View more

@shildebrand Just as an FYI, you can also create a selection layer from the Subtype Group Layer and then do a join to that. ... View more

Thanks for the feedback.  This is not the first time we've gotten this request.  We are taking a look at this and other licensing changes with the next couple of releases. ... View more