Latest Contributions by LarryYoung

Yes, the patch that was mentioned (thanks @Menno_ter_Bals) is for Enterprise 11.5. We are not planning on an 11.3 patch for Web Editor to support the branch versioning change. Thanks, larry ... View more

Sorry, @RichardHowe, got my threads crossed. There have been other threads on the subject, so was just trying to keep the discussion in one place. For better or worse, i don't have anything more to add to the subject that hasn't already been said in this thread.  We do appreciate and hear your feedback. thanks, larry ... View more

Hi Richard, Please refer to this thread on the same topic: Make web editor available to mobile workers While Web Editor is a strong application for simple editing, it also has many advanced editing capabilities with more to come. Appreciate your feedback.  We will continue to evaluate the licensing of our products as feedback comes in. larry ... View more

Hi All, There is a patch specific to Web Editor that we still need to get out for Enterprise 11.5.  Working now to get clarification on the potential time line and will get back to you. thanks, larry ... View more

Hi All, We understand your concern about the minimum user requirement for Web Editor (either the main app or as an Instant Apps configuration) and appreciate the feedback. The overall intent of Web Editor is to be a focused editing application ultimately getting close to the capabilities of ArcGIS Pro as an editor.  While it supports simple editing workflows, it also supports more complex workflows with much more to come.  We believe there's value in Web Editor as a focused editing application for all levels of workflows.  If what you need is simple editing, then Experience Builder or one of the other Instant App templates for editing might be a better avenue for your organization. Thanks, Larry Young Esri Product Management ... View more

Hi All, Happy Holidays. Thanks again for the comments.  I still have one questions that i'm not sure has been answered yet.  The main use case on this thread has been around mobile workers collecting data in the field and then coming back into the office and needing an easy to use web application for cleanup. If that is the primary workflow, then can someone tell me what is missing from Map Viewer from an editing standpoint for that simple cleanup?  Yes, Web Editor may do it better/easier because it is a focused editing application, but it is designed to accomplish many advanced editing workflows as well.  This is the main reason for the higher user type requirement. The answer for a simple web editing application for data cleanup by a Mobile Worker user type would appear to be Map Viewer, particular with the newer capabilities recently added such as batch attribute update.  Other capabilities still to come include split and merge.   So what editing functionality is missing from Map Viewer (Experience Builder is also an option, but i understand that requires configuring the app, etc.) for simple data cleanup of field collected data? Thanks, larry ... View more

Hi All, Just put out a blog related to the licensing change and the patch highlighted in Dean's response above.  The blog can be found here:  Licensing Update for Branch Versioning  Hopefully it helps. larry ... View more

@RichardHowe the plan is to support split, merge, auto-complete and reshape as part of the Editor component which makes up the editing capabilities in Map Viewer and is also exposed as a widget in Experience Builder.   Copy/paste is a little different and therefore will be developed as a separate component within the JS SDK.  The Experience Builder teams will determine the best way to expose that component in their application, but no immediate plans to expose it within Map Viewer. ... View more

Hi @AnthonyJonesRSK, Yes, configuring Web Editor through Instant Apps is in beta with the latest Online release.  We have had many discussions on whether configurations should be available at a lower user type level.  One point that keeps coming up is the fact that somebody could create a configuration with the whole app. Before we released Web Editor or the Advanced Editing UTE we looked into licensing based on specific editing capabilities, but is a very slippery slope and something that would be even harder to explain than our current licensing structure. As mentioned previously, we continue to monitor and rethink our licensing structure and user responses in hopes of finding something that works for everyone.  Web Editor is an app solely for editing, so has some advantages over Map Viewer or Experience Builder for users that spend a significant portion of their day editing.  As always we provide the user community options (maybe too many), so simple workflows for casual editors can be accomplished in apps other than Web Editor with a lower user type as an alternative. thanks, larry   ... View more

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: 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 (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 ... View more

Okay.  Thanks for the response and explanation.  We will take your workflow into consideration as we work through our approach. larry   ... View more

Hi andreoudi, Can you outline in detail what your workflow is for copy/paste?  At this point, copy/paste is available in Web Editor, but as you mention, you have other aspects of your workflow that require capabilities outside of editing. This is part of our dilemma with copy/paste.  The examples we have seen from organizations wanting to do copy/paste include bringing in temporary layers (like census blocks), copying from them, pasting the results into one or more polygons in a different layer, maybe updating attributes, and then running some further analysis.  With a workflow such as this, could easily argue copy/paste is not really an editing workflow and as such should be handled outside of the Editor widget/component. Either way, important for us to understand exactly what you are trying to accomplish. Thanks, larry ... View more

Web Editor (WE) Is meant to be an easy to use editor for the web.  The functionality of WE will ultimately get close to the capabilities for editing in Pro, though we are not trying to replace it in that respect. As such, WE is intended for subject matter experts all the way up to GIS professionals depending on the workflows they need to accomplish. Map Viewer and Experience Builder are also viable editing alternatives on the web for simple editing workflows.  As mentioned, we continue to monitor the feedback on workflows users want to accomplish and how that fits into the user type model. Thanks for the feedback.   ... View more

@Scott_Sambell thanks for the feedback.  We are continuing to evaluate the licensing requirements for Web Editor, and will keep your comments in mind as we move forward. Thanks, larry ... View more

Hi Jenna, The check for the Advanced Editing UTE was added with Enterprise 11.3 and is on the ApplyEdits call with the Feature Service, meaning it is an Enterprise side check.  Having the UTE with Online would not help. Do you need to use branch versioning?  Are the edits from Survey 123 going directly into Default? larry   ... View more