Closed allisonmuise closed 4 years ago
Formerly part of #213 cc @jlindemann
@allisonmuise
Based on the above comments, we are assuming the following points for this functionality:
Let us know your thoughts on this (mockups attached)
Description | Proposed mockups |
---|---|
Adding a new button beside "Sign in" | |
Filters list on click of filter button (buttons to edit and enable filters) | |
Create/Edit filter popup screen |
@ashutoshverma-ct I'm going to distinguish between 2 users:
Due to limitations with the app config panel, I believe we would need to pre-determine how many filters could be set if the filter configuration were to take place in the app config panel. To get around this, I propose using the filter configurations from the map.
I'm imagining something that would have a Manager style UX for the App Configurer and a Near Me style UX for the App User.
1) App configurer defines a series of filters on one or many layers in the map. 2) App configurer enables the display of these filters in the app. This can be a single checkbox parameter in the configuration panel that allows the App User to see the list of configured filters. As you described above, this should be off by default for backwards compatibility. 3) App User can tap the Filter button and then toggle on/off each of the filters. I like your idea for an 'all off'/'all on' option when more than one filter is configured. User should be prompted for values when Ask For Values is enabled on a filter.
@allisonmuise
Based on the above points, in the widget, we will now have only one screen for all the defined filters and a button to view the filter screen. Following are the salient points:
@ashutoshverma-ct
It appears that configuring 'ask for values' filters on date fields is no longer possible. There was a bug in AGOL that allowed it for a time, but they have since fixed it.
We do need a way to configure date filters in this app:
Could you please look into using the time enabled settings on the layer? This will require two additional configuration parameters: 1) users can choose to expose the date filters (off by default) 2) users can choose to filter using start and/or end time for time enabled on two fields (start and end by default, only applied if previous option is enabled, not applicable when time is enabled on a single field)
@CTLocalGovTeam One other note re: the word Filter at the top of the app. We would like to make this the standard filter icon. let's re-arrange the header bar in the following order to make this look better. From left to right the icons (when relevant) should be filter, help, sign in. The burger menu options are fine as discussed.
@allisonmuise
We would like to discuss the date filter requirements in detail to make sure we are on same page. Could you please set up a call at your convenient time?
@ashishchoure Would after status tomorrow work for you?
@allisonmuise
We can discuss the requirements after status.
@allisonmuise
Considering all the inputs during the discussions, here are the updated points along with the mockup:
Configuration:
Widget:
Note: Filters defined in the map with no "Ask for values" will be not be shown in the widget
Mockup |
---|
Please confirm Mockup also includes the filter icon in the header section |
@jlindemann - please review and let CT know if this looks good to you
This looks good @ashutoshverma-ct @allisonmuise I assume the second drop down is 15 minute intervals like other apps?
@jlindemann @allisonmuise
I assume the second drop down is 15 minute intervals like other apps?
Yes, the second dropdown is the 15-minute interval. Here are the screenshots for both first and second dropdown.
looks good
As discussed, we need to provide a "back" button for the filter screen and match the style as shown in the below sample screenshots:
Filter de-activated | Filter activated |
---|---|
verified
Need ability to filter specific layers using specific queries, such as road blocks that fall within a specific date range.
each filter is applied to only one layer.
filter(s) must be editable in the UI.
filters do not need to be reflected in the URL.
Perhaps configure using the 'Ask for values' filters defined in the map, with a configuration toggle (off by default) that users can enable to have these filters exposed in the app (backwards compatibility)?