Select to view content in your preferred language

Allow actions to select the floor filter

449
2
06-17-2024 05:53 AM
Status: Open
Labels (2)
KatieSelfEd
Occasional Contributor

Message actions from other widgets should also act on the floor widget if it is connected to the same data framework.

For example I currently have an Experience with three widgets:  a (floor-enabled) map, a list and a floor filter. When I select a building from the list, I'm able to pan to the corresponding on the map via the message action. The problem is that the floor filter widget does not react and stays on whichever building it was last on.

This removes the ease of being able to jump around buildings first, then internally within floors. The list is made redundant as the user still has to select the correct building on the floor filter 'browse', but this browse menu is less customisable and not as intuative to navigate, so doesn't make a good replacement for the list widget.

2 Comments
AndrewBowne

It'd be nice to be able to pass URL Parameters to filter floors through the widget also.

JDenham

We could really use this functionality as well.  We are still running Enterprise 11.3, and in this version at least, even the select widget doesn't play nice with the floor filter.  Selections using the widget do not respect the floor chosen on the floor filter.  Instead, it will select all features within the pick box across all floors.  This makes the 'statistics' action options available through the widget useless because the statistics are produced from the whole (unwanted) selection.  This, among some other functionality gaps, is keeping us from being able to migrate to ExB.  I suspect there are still proportionally few users working with floor aware maps, because your list example and our need for quick stats on selected rooms is foundational to anyone actually building indoor tools.  Perhaps they have this particular bug fixed in 11.4, and we'll hopefully be able to upgrade soon to test.  We are coming down to the wire on migrating to ExB because I understand that 11.5 is the only version we'll get to actually transition before WAB goes away, and we're still waiting on critical functionality. 😬