Community

URL Parameters similar to WAB

788
2
05-11-2021 11:45 AM
Status: Open
Labels (2)
ZorbaConlen1
by
Occasional Contributor III

Hi. It would be great if ExB supported url parameters similar to WAB. In that app, one can pass parameters to the app which control default layer visibility, extent, selection of features and similar. 

Additionally, the share widget provides an interface to easily generate short URLs using these parameters. This allows non-technical people to create their own custom launch links. 

And there are other behaviors that would be useful to enable via url params, including default active widget, basemap, title or sub-title or other text values in the app, query expression, etc.

I feel like this is one of the best features of WAB and disappointed that it's not implemented for ExB.

There are many use cases. As an example: a single app can replace multiple single purpose apps. Suppose a city has a separate map for Zoning and another for Capital Projects and another for Parks ans so on. All of the layers could be combined into a single ExB app, and separate launch links could be generated to launch the app to mimic each single purpose app. The one for zoning would load with zoning layers visible by default and the title could be changed to "Zoning". 

Thanks

2 Comments
AllisonMuise2
by
‎05-25-2021 09:03 AM

I need the ability to open an Experience Builder app with a specific feature selected. It would be ideal if I could do this with a URL parameter.

BrianFausel
by
‎02-15-2022 03:15 PM

Just started using the Share widget in Web AppBuilder (WAB) to obtain direct links to specific map areas and layer visibilities. Also, we have been using URL parameters to link external apps to our map via a common ID for awhile now. Both work great in WAB!

This functionality should definitely be added to Experience Builder, as we would really like to utilize the new web map layer grouping functionality that is offered there. Unfortunately the layer grouping does not work in WAB, so we are trapped between two apps each containing separate pieces of the critical functionality puzzle.

Use case: What ZorbaConlen1 suggests as "a single app can replace multiple single purpose apps" -- a link to open the same app but different layers turned on (zoning, capital projects, etc).