Out-of-the-box feature editing tools (i.e. no workflow required)
Completed
RELEASED: Web 5.17
In the Geocortex Web, it seems like it's currently only possible to edit a features geometry and attributes through a Workflow currently. Seems like it would be easier to edit features just by clicking on them and editing link in previous generations of Geocortex Products. i.e. click feature > map tip > edit feature > a contextual menu relating to editing appears.
note: workflow newbie so feel free to squash or reword this idea!
simliar:
https://communities.geocortex.com/s/question/0D55x000077qKKMCA2/edit-a-feature-layer
catalyst:
https://communities.geocortex.com/s/ideas?t=1588722603950#087f20000005EvmAAE
-
Another workflow newbie and honestly adding key functionality like editing, buffering, searching to a viewer through a series of workflows only instead of the way the Html 5 viewer works is not what I want to spend my time doing. I like the look and feel of the new viewer but if the tools from the HTML 5 viewers are all workflow dependent I don't see using it any time soon what a shame.
0 -
Thought I'd copy my comment here from the discussion in the Web community for context.
In the mid-to-long term there will be out-of-the-box tools for add feature and edit feature. It is important to have a clear, simple way to do these things without needing to build a workflow. I will be keeping these out-of-the-box tools very simple.
When it comes to Geocortex Web, even a simple tool requires a fair bit of thought because we need to ensure we are supporting both 2D and 3D use cases, and that the tools we provide are WCAG AA accessibility compliant. This means, in practice, that we can almost never use Esri's default implementation.
As Stefan said, the fact that these use cases CAN be accomplished today using a workflow has given us some discretion in the timing of these out-of-the-box tools.
I am mindful of the many, many times I've heard from our customers feedback on existing out-of-the-box tools where they want to:
* Limit editing to certain attributes (I want my field workers to change attributes a,b,c but NOT d,e,f)
* Limit editing to attributes only (don't let my field workers change the location, all they should be doing is updated the attributes)
* Limit editing to location only (my field workers should not be changing the attribute data, I've only sent them into the field to verify the correct location of the asset)
* Restrict different types of editing to different roles within the organization
* Provide instructional text within the editing experience to better guide users in what is needed for a particular attribute
* Provide a custom flow / guided interaction for a dedicated editing use case
... all these examples are things that can and should be accomplished using an editing workflow and that will NOT ever be part of a simple out-of-the-box editing tool
In principle most of our customer get and agree with the idea of having a simple out-of-the-box tool and then using workflow for more sophisticated use cases; but fun and consistent observation is that a particular customer's user case is often argued for as being 'the norm' and belonging in the simple out-of-the-box tool 😃
0
Please sign in to leave a comment.
Comments
2 comments