Many of you would like to know the priority list of widgets that Experience Builder team will be working on in 2021 and Beyond. Here it is. Please keep in mind that things are subject to change.
great product, are there any plans on enhancing expressions and text formating in the experience builder? I did a basic expression to divide two values and get a lot of decimals. That's not so great.
Also, would be great to see multiple columns in the list widget and more chart options to filter content. That would be amazing.
The most basic widgets are not available - Edit, Measure, Print. Why have these been overlooked? These are probably the most fundamental workflows for the most basic GIS applications. There seems to be a disconnect between esri and it's customers requirements. These need to be prioritized and a specific timeline for delivery released, how do you expect customers to plan without knowing if and when basic functionality will be released? This is beyond frustrating.
@QuantitativeFuturist Your comments are helpful, though perhaps somewhat extreme. Believe me, I fully appreciate your concerns about planning, but as someone who writes software I must say that things never go as planned or as quickly as expected when building something - much less something as amazing as Experience Builder will one day be. It is much, much better that Experience Builder was released when it was than if Esri were to wait until everything was perfected before doing so. Why? Because software never is perfected until after multiple iterations after it is released. Of course the product is no longer in beta, but it is still in version 1, so we can't expect it to be 100% ready to do everything that Web AppBuilder does. Right now Experience Builder should be considered to be a collaborative project between Esri and it's early adopters. Unfortunately, you either have to join now and deal with the good and bad that comes with being an early adopter or wait until it is a mature product - it is up to you. I, for one, am glad that Esri has allowed me to work with the product before it is fully matured. This gives me the opportunity to express my opinions about how the product is shaped early in the process. On the other hand, your comments will probably be helpful for others who are trying to decide whether or not now is the time for them to take the leap!
The bottom line is that we don't actually have a very good way of knowing when a product is mature enough for us to decide when it is ready for us to adopt (a real problem that should be addressed). ArcGIS Pro for example is getting close to a major release (2.x to 3.0). I would bank on ArcGIS Pro 3.1 being the benchmark where most users thought it had the green light on everything it needed for migration from ArcGIS Desktop. That is more than 6 years into the process.
@DaveFullerton thanks for your outlook on this - I do appreciate your opinion. You may be correct about the tone of my post however it is born out of frustration. ESRI has a huge amount of resources and probably have a fairly good idea of what widgets from WAB are most commonly used. I mean what's the point of having a version management widget but no editing widget, the prioritization seems off to me. It's not like this is an open source project, we pay a not insignificant amount of money for licensing so I would expect appropriate resourcing to migrate widgets from WAB to Experience builder. I do think that as customers we should be holding esri to account and demanding proper release schedules, not vague blog posts.
I agree with the frustration in priorities and communication. I have to base multi-million dollar decisions on random blog posts, slides, and geonet posts. I often pitch building new shiny tools only for users to wonder why it cannot even do the things the last one could do for years. I know it is a huge project to rewrite in JS 4 but I would rather wait then rush it out the door.
We planned to remake our whole system in the new Map Viewer and EB this year. But day 1 I found that there is no support for relationship classes. Umm like its the very first letter in RDBMS (Relational Database Management System). How can we have a RDBMS without it. I think I saw posts saying by end of 2020..then end of 2021..then no word. (It is not even on the roadmap above now.) Stopped the project on us day 1.
Design decisions can also be confusing. Like creating layer groups then splitting out tables to their own section - which has no grouping. I do not understand the use case here. Tables are mostly ignored across the board even though in almost every company I see they have more tables than layers. Part of getting companies to integrate with spatial data is linking tables. I believe Esri ignoring tables as been the biggest slow down in adoption that I have seen.
In other apps like Field Maps/Collector we have been asking for a simple filter for years now. I feel like Esri could use some experienced field testers on the team. (Or run things by Professional Services and they can help you relate it to the real day to day out there.) Us computer people are often bad at testing in the office vs outside and not really talking to the field crews. Again it is hard to explain to people why a 15 year old Access DB can do more than a Esri 2021 product. In this example I have posted (with lots of upvotes), spoken to our rep, and even talked to the team with Jeff himself and I still cannot get anywhere.
Consistency is also critical and I really hope using a common code structure now across apps will help. One simple example is that Editor tracking fields are named differently if added in ArcMap vs AGOL. How does that happen? There must be a Esri standards dept right? It is a programming nightmare. It is not even the first time - who remembers ETEdited?
This is all my opinion of course and don't get me wrong I love you guys. I just think you need to focus more on what is important vs creating all these tools that are half done and eventually abandoned. I would rather have a few thought out and tested tools.
Thanks for all you do!
I am chasing print functionality. I created a Scrolling Page with a Feature Info widget set to auto. Experience builder does a great job displaying the dynamic pop-up in the Feature Info widget (some can be hundreds of related records)
It seems like printing in Chrome is almost there (default ctrl-p) I just need the added functionary to print the scroll as multiple pages. Of course by print I mean Save as PDF, but I someone could print on paper.
@DavidRasner1, enhancing the format in Expression and Text and supporting for multiple columns in thee List widget are known issues. Your requests have been added. As for the chart, more chart types and options will be added through incremental releases.
@QuantitativeFuturist @DaveFullerton @DougBrowning, thank you for sharing your opinions and perspectives on the widget priority and communication. Could you shed some light on how we can improve the communication on what's coming? During the technical session at UC, we opened a poll to ask attendees about which next widget you would like to see the most. Would it be helpful if we do something similar through the community?
@QuantitativeFuturist, we are working on the Edit and Print widgets currently. Agree they are fundamental. As for the Measure widget, could you let us know what is missing in the Measure tool on the Map widget?
@DougBrowning, related tables are important. It is on the near future road map of the new Map Viewer. We will try to bring it over once it is available.
As some of you may know, the widgets in WAB are collaborative efforts from many Esri teams, and each team may focus on various areas. The widgets in Experience Builder follows the same collaborative pattern, and more are coming.
Thank you all for such candid conversation!
@Jianxia regarding Measure widget and what should be included:
All tools already available either in the basic map/scene viewer or the JS API.
What else I wish was available (but is nowhere to be seen): Measure Volume (based on a raster DEM or integrated mesh layer...one man can dream). That's such a highly requested feature from our drone operators.
Just on your charting comment. I have noticed when using charting with 3d scenes the map display does not render all 3d features. This is occurring from the top of the view. If you tilt the 3d view to a 2d perspective all information is rendered in the display. My question is, what is the chart displaying when this issue occurs? Is it only what's visible in the display or the extent of the map view regardless of what's displayed?
Looking forward to more charting options. Also the Line of sight widget would be a fantastic inclusion. I'm getting lots of requests for this corporately since we have been producing EB 3d apps.
Jianxia, any updates on the graphic you posted last March listing the widgets planned to be included in future ExB versions in 2021. Thanks.
Editing information via tables is something that I think could be improved on. The ability to select multiple features and edit together or run simple calculations vai the table widget would be very useful. Currently you need to click on each item and it makes the task very tedious.
@Jianxia Thanks for your response. Very much agree with @Geoeki comments regarding the measure widget. I think that in terms of understanding the roadmap, having a single point of reference that is kept up to date that provides release dates and updates would be extremely helpful. Having to dig around in presentations to find an out of date slide with vague dates makes planning impossible, especially in enterprise systems.
About the futur Add Data Widget. I would like to know if the widget is going to add the feature layers in group layer.
I think it is a better way because the ESRI JS API 4.x LayerList can show the feature layers as a group if the feature layers are in a group layer.
@Jianxia Thanks @henrilebon974 for bringing this up the Add data widget is one that I had missed in terms of importance - this is key functionality for flexible app design. Please make this available asap. Thanks
@Jianxia Have you seen any grids that layout the Web App Builder Widgets with their equivalent in Experience Builder or Configurable Apps basically a Java 4x version?
@QuantitativeFuturist @Geoeki, the measure tool on the map can do the distance and area measurement as shown below.
As for the measure volume capability, we will let the imagery team know.
Thank everyone for your input. To get your feedback more efficiently, we plan to do the followings:
1. Post a survey in community to collect feedbacks on which widgets you would like to see in the near term to help us prioritize the widget development.
2. Share a live document for the functionality matrix between WAB and ExB. Update it accordingly after each release.
3. Update the road map.
Have a great weekend!
@Jianxia , looking forward to seeing a functionality matrix! It will really help us see where the parities lie.
I for one (as do others) strongly feel that the volume measurement capability would be an app killer for the drone industry, and push ESRI towards the top of the market in this sector. It's been missing for too long 🤞
When this tool is in the development queue, i'd greatly appreciate providing some more detailed low-level input., if possible.
@Jianxia Sorry I had not been able to respond sooner to your direct request for ideas about communication. I think the things you are suggesting will be very helpful. It would be good to know if you plan to periodically redo the survey, and if so, how often. Seeing the results of the surveys would be helpful too.
Regarding the road map and the live document for the functionality matrix, it would be good to have something in the matrix that tells you where the widget is on the road map so we don't have to try to use both to find everything we need to know.
Finally, I think that what user's really want is to know your goal for exactly when (for example, 2021 Q4) you think it is possible that a widget will be released. I would not like doing that myself, but I could feel comfortable with it if I were also able to specify a level of confidence in reaching that goal (1-3 perhaps). And of course some (or many, or most) widgets could have no such specific goal listed (maybe indicate somehow if widgets are awaiting completion of work from another team?). Providing this kind of information would deviate from what Esri does for the rest of it's products. The road maps for all products seem to reveal the same level of information, so I know this may not be possible. However, during the conference and the developer summit, I have heard questions answered with that kind of detail ("We hope to have that out in this year's Q3 release"), so if you are comfortable enough to say it, please write/post it somewhere for those who are not able to attend every conference session.
@Jianxia Thank you for this.
Are there plans to include Select 3D Features (from SLPKs) in Web Scenes (not 2D Features in a Web Scene).
At the moment, I dont believe that this very useful functionality is possible with SLPKs.
@Jianxia I'm super stoked to see that you guys have created the moveable search bar!!
I really need this search bar to be able to return arcade scripted fields. The majority of the time we use search on our property layer, however we heavily use arcade for the popups to show how that property relates to other layers. This means that we can keep our layers clean and not duplicate information between layers - less updates and maintenance required! For example I'm trying to build a page for our rubbish and recycling collection. We have this currently as an app where the person can search their property and it will return the results in a sentence including the intersecting collection day feature.
@NaomiBegg, Glad you like the movable search bar. Currently Experience Builder does not support arcade except for the pop up from the map. Could you help submit an enhancement or add it to the idea site? Thanks
@Jianxia Do you have an update on the Print widget? Also, is there anyway to constrict ESRI Search to Map? Or should I add a layer of addresses and use that? Thanks. Mike
@mhargreaves The Print widget is planned for the Q2 next year around UC. As for the Search widget, the workaround I can think of is to add the same map twice in the data source tab. Rename one map to map1 and another one to map2, for instance. Add the map 1 to the Map widget, then connect the layer on the map1 to the Search widget and the same layer on the map2 to the List widget. In this way, the widgets think they work with different datasources, therefore would not interfere with each other even though two map datasources are identical. The List still can interact with the Map widget connecting to map1 datasource as long as the Map widget is set as target for the action triggered by the List widget.
Could you share the use case so we fully understand the question?
cc @ShengdiZhang for comments.
The functionality matrix for WAB and ExB is now available under the ExB Documentation tab.
I got an update on relationship class support. Will not be until the July update. Big bummer there and it puts us way behind.
Anyone hear a date when the now Classic Map Viewer will go away? At this point I would need until at least end of 2023, and if the current pace continues probably end of 2024.
My question regarding search - in the instant apps, you are able to restrict suggestions from the ESRI World Geocoding to just the extent of the map. I don't see this ability in EB, and when I type something in the search box, I'm getting suggestions from all over the world... Here is the site I'm working on
Also, I'm not seeing a way to reply to a post in this blog, only to add a new one...
@mhargreaves - Currently there is no option of "Only search current map extent" in the Search widget in Experience Builder. This option is available in Web AppBuilder though. Would you mind submitting an enhancement request to Esri Support?
@Jianxia we are currently missing the following functionality in EXB:
Are there any plans to add this functionality in the near future?
@mhargreaves - For now, you can work around the map extent issue with Search widget by using the locator view, which is a hosted custom world geocoder. To do so, in ArcGIS Online, click Content->New item->Locator, and define the extent for the locator. Once it is done, share this item publicly, then copy the url to the locator source in ExB. (note: currently ExB only takes the public locator view). Understand this is not strait-forward.
@Jianxia I tried that, and also deleted the World Service in ExB, but still giving suggestions outside my area...
@Jianxia any updates on EB print or PDF export widget timelines?
Are you aware of any AGOL PDF map/report generation workarounds (besides Survey123 which has awesome report templating)?
PDF reports/maps still rule in government because they can be treated as "immutable" documents.
Thank you for your time!
@Wolfgang_Grunberg_AZ_DFFM , the Print widget is planned for Q2, 2002 currently. See ExB 2022 roadmap. As far as the report templates are concerned, Pro team is working on it and hopefully we will have such capability in the printing/reporting service in the future.
@Jianxia thx - excellent news!
BTW: Survey123 report templating is surprisingly powerful and flexible (even supports MS Word's dynamic elements) - kudos to that team.
I'm having another attempt at using the search widget.
I can't see in the settings where to change the search settings for ArcGIS World Geocoding Service to be set just to my country/region. This is quite important as using the world geocoding without the filter is quite overwhelming for customers who only work within specific areas.
@NaomiBegg - you may create a locator view with chosen country/region, then use it in the Search widget. To do so, in ArcGIS Online, click Content->New item->Locator, and select the country/region.
@mhargreaves - if you still run into the issue after creating a locator view with the extent, pls submit a Support ticket. BTW, you can use non-public locator view in the Search widget now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.