Control which saved searches to show in the list
From what I've read so far through the apps we are not able to create new searches or modify existing searches that have been saved through the desktop version of WA. Could there possibly be a way to add a checkbox on the full version of WA searches to show only those searches in the app? We have a lot of internal searches that don't necessarily need to be included on the app, but it would be nice to be able to reduce the number of searches in the app list to only those that are deemed necessary for our membership administrators.
Larry Killer commented
Yes Evgeny, it would be nice to exclude some of the searches that aren't necessary for the majority of our uses.
As an example, our GM has saved searches to look up members that are about to be archived, but that search wouldn't be anything any other board member would need.
The other reason I would like to see this - from the standpoint of our organization - is that because the app searches cannot be modified we will need to create more defined searches which means more searches to scroll through. Example: We have a search by region (we have 7 regions). On the desktop we can search different regions by simply changing the search fields. On the app it only shows the results by the region that is the default on the desktop search...if that makes any sense?! Therefore we need to create 7 distinct searches on the desktop of each region and name them specific to the region. That adds to the list of searches, so being able to prevent non-essential searches from showing in the app would make it much easier scroll through and find what you really need.
Now, we could modify our searches from the app, that would be even better! But without knowing how to code, in my feeble little mind it seems it would be easier (at least for the next release) to just add checkboxes next to each search to indicate whether they should appear on the app or not.
In other words, you want to hide some searches on the mobile app, correct? Funny, we had this in very initial app design but excluded in first release.