Latest Contributions by ZorbaConlen1

The layer list widget in WAB is problematic. End users often struggle to figure out how to use it. My organization has a public facing map viewer with numerous layers grouped into several themes and we configure the layer list to be collapsed by default. The most common problem is that end users dont understand that they can expand the top level group and see the sub-layers to turn on. A secondary probelm is that they turn on a sub-layer while leavng the parent layer un-checked and conclude that the app is not working correctly.  Proposed fixes: Make layer list more intuitive by improving the styling. For instance, the arrow that expands the group should be much larger. Also, groups should be styled differently from layers, perhaps with a folder icon. Also, its confusing that the arrow expands groups but also displays symbology for layers.  More configuration options. As it stands, one can either expand all or collapse all. It would be helpful if one could have more fine grained control over this. For instance, if the layer list widget opened with most groups collapsed, but one expanded, this would help users understand how to use the widget.  Context sensitive help. There should be an option for admins to input description of how to use the widget. This could be a text (html) area toward the top, or perhaps an 'info' icon that displays the content when the user hovers or clicks (note that this would be a useful enhancement to all widgets accross the board). One click to show layers. If a user toggles a sub-layer visible, all parent layers should automatically be checked visible. Help users understand scale dependant visibility. The grey text is ok, but not enough. Again, there should be a hover or an icon to get more info, in this case a message explaining that the layer is not visible at the current scale. Context menu should have option 'zoom to visisble scale' for scale dependant layers. Show layer description on hover (or click on info icon), rather than making users take the effort to use the context menu and open a new tab, which is not a great user experience. Also, this feature does not work if the service directory has been disabled.  ... View more

It seems there is no way within an arcade expression (in AGOL) to formatt text. Please allow markdown or some method to format the returned text.  I'm aware that I can format values returned via an expression in the html mode of the popup configuration interface, but this is insufficient for some purposes. I often need to format different parts of an expression differently, and this needs to be done in the expression itself. Thanks ... View more

Hi, I'm new to this realm of esri software. Can anyone clarify the difference between Geoevent Server and ArcGIS Analytics for IOT. When I read the descriptions, they seem quite similar. It's clear to me that the former is an on-prem software while the latter is SaaS. Beyond that, how do they differ in terms of capabilities, licensing cost, etc.? Thanks ... View more

The mobile popups in WAB are not that user friendly. The initial popup is too small and lacks sufficient info to be useful, but after expanding, its too large, covering the entire map.   I would propose the following: Initial popup larger, showing the popup title and a portion of the body of popup. In many cases this would be large enough to provide the key info a user needs and they would not need to expand it. The popup can be expanded to show more, but it will cover only half or 3/4 of screen, allowing user to still see the map. This expanded popup should be scrollable in case content exceeds size of popup. Also, some formatting improvements like not cramming content against top and left border. Map should pan automatically so that selected feature is visible on the portion of map not covered by popup. Popups should not be anchored to feature. Rather, the initial popup should be anchored at bottom of screen, or top. Expanded popup should likewise be anchored to bottom or top. Perhaps this could be a configuration that admins can decide.   ... View more

It would be very useful to be able to create arcade expressions that are available to more than the layer they are configured for in a webmap. Ideally, one could create and save arcade expressions for the organization which could then be accessed by any user. Perhaps as a template. Or optionally, re-use the same expression within a webmap.  For example, let's say I create a title case expression, which returns a given field value in title case. I might want to use it in numerous layers within the webmap. Currently, I would need to copy and paste that expression to each layer, and if I wanted to edit the expression later, I'd need to make the edit to each layer individually. Additionally, if one could create arcade expressions that accept input parameters such as field names or similar, that would make this much more powerful. Good if one could access the global arcade expressions via the arcade editor.  Thanks ... View more

Hi. WAB table widget has a config option to "Synchronize with layer visibilities" option which is nice, but it does not work how one would expect. The problem is that if one has group layers like shown in the screenshot below, sub-layers that are not visible on the map still show up in the table widget. For example, sewer inlets is not visible because the parent group in unchecked, yet it would still show in the table widget.  So, the idea is to make this widget smarter so that it honors actual layer visibility on the map. Thanks ... View more

Hi. Is there a way to configure a webmap such that search works only on a layer and excludes any organizational locators and the arcgis world geocoding service? I have it configured like this in the settings. Note that "by address" is unchecked. I'm still seeing several geocoders in the address search dropdown. My assumption is that unchecking the 'by address' box would configure the app to only use the layer search. If that's not the case, could anyone explain the purpose of that checkbox?  Thanks ... View more