IDEA
|
The functionality described by the original post would be very helpful. Currently, the search associated with the list and the search associated with the map are separate, which may be confusing to users. In addition, the search widget on the map cannot be set to automatically "expand" when you enter the page, and its position within the map cannot be changed. Because of this, users who are unfamiliar with these environments may fail to notice or utilize the search widget. Having more control over the placement and expanded state of the search widget would be incredibly helpful in improving the end-user experience.
... View more
07-23-2020
02:53 PM
|
0
|
0
|
1000
|
IDEA
|
In working with multiple pages in Experience Builder, there are sometimes changes that need to be made across all pages for consistency - for example, the appearance and placement of a menu, or buttons. While Sections can allow Views to be used within the same page for that type of consistency, I sometimes need things outside of the Section to be different between different pages (eg. having a Filter widget appear on the sidebar). Having some way to establish a "framework" element that could be edited for all pages simultaneously, or applied to all pages (similar to how, within the List widget, alterations to the 'Regular' appearance can be applied to the 'Selected' appearance) would be very useful.
... View more
07-16-2020
01:44 PM
|
7
|
1
|
156
|
IDEA
|
In the Experience Builder list and text widgets/elements, it would be nice to have options to allow text elements to scroll, rather than only having the tooltip display for longer text (as shown below). Scrolling feels cleaner and more user-friendly. This could be presented as a style option to set the CSS values of overflow-x (and possibly overflow-y) to scroll, hidden, auto, or visible. Alternatively, overflow could automatically be set to scroll.
... View more
07-10-2020
02:37 PM
|
4
|
0
|
139
|
IDEA
|
So, I am currently struggling to understand Actions and their interplay with each other in Experience Builder. Some examples of issues I have run into are: 1. Actions conflicting with each other / strange Action loops. Ie. an action in the map triggers an action in the framework, which then triggers an action in the map. 2. Actions not following through. I have tried setting it so that a record selection change on the map changes the framework, as well as a map on a separate page. But, when I click a button to go to that separate page, the record selection reverts to the first record in the attribute table, rather than the record that was originally selected. I cannot find any rhyme nor reason for this. It is difficult to describe the issues I am having as they seem specific to the dataset / aren't repeatable across separate EB projects. I am also struggling to make sense of Actions in general, which brings me to the "idea". I am not sure exactly how these types of issues could be resolved, but if there was a way to 'prioritize' Actions (eg. one Action will always occur over another when there is conflict), or to see an overview of all current actions and change them in one space, rather than needing to go through each element, that might help a lot. Especially if that overview had some built-in error checking to prevent users from setting conflicting Actions. The element-by-element approach becomes difficult to keep track of after a certain point. In addition to that, I am wondering if there is some documentation somewhere that goes into detail about best practices for using Actions. Actions are a very powerful and exciting concept, and I really love the potential of them, but at the moment I can't tell if they are still rather buggy, or if they just aren't intuitive to me.
... View more
07-09-2020
02:54 PM
|
4
|
0
|
131
|
IDEA
|
Currently in the Filter widget, the 'contains' operator only returns features where a given field contains all selected values. I would like to see an operator that would return features where a given field contains any of the selected records. For example, with a field containing a list of values: ObjectID Land_Use 1 agricultural, industrial 2 residential, agricultural 3 educational 4 recreational, industrial, residential Land_Use contains any of agricultural, industrial would return features 1, 2, and 4.
... View more
07-08-2020
08:36 AM
|
6
|
2
|
222
|
IDEA
|
Currently in the Filter widget, the 'contains' operator only returns features where a given field contains all selected values. I would like to see an operator that would return features where a given field contains any of the selected records. For example, with a field containing a list of values: ObjectID Land_Use 1 agricultural, industrial 2 residential, agricultural 3 educational 4 recreational, industrial, residential Land_Use contains any of agricultural, industrial would return features 1, 2, and 4.
... View more
07-08-2020
08:36 AM
|
6
|
2
|
219
|
IDEA
|
Currently in the Filter widget, the 'contains' operator only returns features where a given field contains all selected values. I would like to see an operator that would return features where a given field contains any of the selected records. For example, with a field containing a list of values: ObjectID Land_Use 1 agricultural, industrial 2 residential, agricultural 3 educational 4 recreational, industrial, residential Land_Use contains any of agricultural, industrial would return features 1, 2, and 4.
... View more
07-08-2020
08:36 AM
|
6
|
2
|
217
|
IDEA
|
I have noticed some discrepancies in how the Filter widget functions in Experience Builder vs. Web App Builder. The "idea" is that I would like to see consistent functionality for the Filter widget; I have two examples of areas where they seem to differ significantly. The first is that Filter doesn’t seem to have an option to ‘zoom to selection’ in Experience Builder. I have tried to find a way using Actions, but the Filter does not have any ‘Action’ options, and the map cannot be made to zoom to itself through Actions (which makes sense, as Actions are set where the event occurs, not where they are carried out). I am not sure if I am missing something with this, or if it is just currently unavailable, but it would be a useful option to have. The second difference is that you cannot set a ‘predefined’ input type (or any input type) for the filter value in Experience Builder, which is an option that is available in Web App Builder: My use case for this is essentially working with spreadsheets where a field contains a list of values. The ‘predefined’ values option allows list items to be separated, and also allows a label to be set to reference each value. Survey123 results are a good example, as without predefined values they will display like this: With predefined values, I can make them display like this, which is more user friendly: Edit to add - I found another inconsistency. In Web App Builder, it is possible to have an expression filtered by a previous expression. This does not seem to be possible in Experience Builder, but would be fantastic to have!
... View more
07-08-2020
08:26 AM
|
26
|
4
|
504
|
POST
|
Hey! I've been trying to figure this out, but it seems I don't have permission to view your survey - does the shape text translate to a shape on a map within the Survey123 form, or is it simply saved as text?
... View more
01-09-2020
02:09 PM
|
1
|
7
|
174
|
Online Status |
Offline
|
Date Last Visited |
12-02-2020
03:05 PM
|