What’s New in Web AppBuilder for ArcGIS (March 2017)

This update to Web AppBuilder for ArcGIS embedded in ArcGIS Online has many usability enhancements which include the following:

Widget Enhancements:

  • A new Legend widget is available for viewing legend information in 3D apps:

    New Legend widget for 3D apps

  • Analysis Widget – 2 new tools are available: Find Outliers and Join Features. For the Plan Routes, Connect Origins to Destinations, and Find Nearest tools, you have the option to include the Route layer as a resulting layer.

    Analysis widget - 2 new tools

  • Basemap Gallery widget excludes basemaps with different tiling schemes from the current basemaps in the widget.
  • Edit widget – You can now configure the display name of the related records in the pop-up when editing a related table. See general enhancements section for more details.
  • Group Filter widget has 2 additional filter clauses: “Is on or before” and “Is on or after” for filtering on date fields.
  • Info Summary widget has improved support of CSV layers.
  • LayerList widget has a new context menu option to show/hide feature labels, when a feature layer has labels applied.
  • LayerList (3D) widget supports displaying layer hierarchy and terrain layers.
  • Near Me widget enables you to specify the maximum number of results to be returned.
  • Query widget includes options to configure the labels for both Task and Results tabs.QueryWidget
  • Situation Awareness widget – The snapshot button is now disabled when there is no potential impact of an incident in the defined location, and the Find Closest Address has been modified to better support localized projections (non-Web Mercator).

General Enhancements

  • Within a pop-up, related records now use the pop-up title defined in the ArcGIS Online map viewer, instead of the “display name” defined in the service, as the default display name. End users can also manually change it to other field names in the pop up at run time. For example, when you click a parcel and view its pop-up, it reveals 2 related tables: Relationship2 – Buildings_GlobalID and Relationship2 – OwnersR. When you click on the Relationship2 – Buildings_GlobalID, the related records are returned but they are not very clear – both related records are called Buildings_GlobalID:RC.RelatedRecordNameYou can change the appearance of the related records returned in the pop-up, by modifying the pop up of the related records layer. Under the Map tab, click Edit This Map, select the related records layer and configure its pop-up. In this case, you could select RepRowID to provide a more informative name. So you can configure the pop-up title to be used as the default display name for related records. Save the changes to the web map.Edit RelatedRecordNameNow when you click a parcel, view its pop-up, then view its Relationship2 – Buildings_GlobalID, the related records are labeled based on the RepRowID values 19 and 20.RelatedRecordName2
  • Label configurations on a layer are honored in the app.
  • A new feature action Save to My Content is available to a feature set. For example, a query result, a GP result, or a selection set.
  • Support for Hindi language

Builder Enhancements

The builder environment supports ArcGIS Online’s new account switcher capability. This is useful if you have multiple accounts for various ArcGIS Online organizations. You can link the accounts to efficiently switch between them when creating new web apps.


The Web AppBuilder for ArcGIS Dev team

This entry was posted in Apps, ArcGIS Online, Mapping, Web and tagged , , , , , . Bookmark the permalink.

Leave a Reply


  1. athomas says:

    Is there any chance the print widget was modified with this iteration? Suddenly today, the WAB print widget will not accept URLs to my custom print services. I receive this message: “the URL is not a print task.” Thanks!

    • Law says:

      Hi athomas,

      No changes were made to the Print widget. Can you please open an Esri Tech Support incident so we can get some repro steps and sample data to investigate further? Thanks.

  2. vanporman says:


    with the new LayerList widget update, all feature layer labels are by default turned off even if they are applied in the web map. It is very tiresome to turn them on manually every time user open WAB app. Is there a way to show labels by default if they are applied in the web map? And how does this new update affect server map service? If i have enabled labels to my feature class and have uploaded it as a map service, then added this to the web map and have created a WAB app?

    • Law says:

      Hi vanporman,

      We did have a minor regression with the recent ArcGIS Online update regarding labels. Basically labels for features from a feature collection are not visible by default and we are working to address this item in a patch. This should NOT affect map services with labeled features. If this is the case, can you please open an Esri Tech Support incident so we can get some repro steps and sample data to investigate further? Thanks.

  3. liamrobinmurray says:

    “Basemap Gallery widget excludes basemaps with different tiling schemes from the current basemaps in the widget”.

    Call me cynical, but turning useful functionality off doesn’t feel like an enhancement.

    • dcoley says:

      I must say I have to agree with Liam:

      “Basemap Gallery widget excludes basemaps with different tiling schemes from the current basemaps in the widget” is not good.

      I have all of my custom basemaps defined with the same web mercator projection and using the googlmaps/bing tiling scheme. The only difference is I do not create the same levels of detail – i.e. most users do not create cache scales for local basemaps at continent-size levels. If coarser scales are removed and finer scales are added, 1:564, 1:282, then does that by this definition change the tiling scheme? Because if it does then some esri basemaps would be excluded – e.g the light gray base map does not go down to the same level of detail as the topo. We need more info please

      • dcoley says:

        Actually I was a bit hasty on my comment here. There are no issues with differing LODs as long as the services are the same spatial reference and the services are cached tiles. It is however unfortunate that we can no longer layer both dynamic and tiled services in the same basemap. Not a huge but it was a work saver.