Usability Enhancement - By Default, Expand All Filters on Data Grids

What does this group think about this enhancement request?

Enhancement request: Usability Enhancement - By Default, Expand All Filters on Data Grids

The requestor added this description: "Throughout Landmark, users find it very aggravating that the filter option is always not on, by default. I have to dig for it in the actions and then click filter on every screen. I think all of these screens should have the filter icon expanded, by default. There should be a global setting to do this on all lists. This [expanding the filter row] is just one more click when most of the time you want to filter for data on the screens."

Here are some screenshots to illustrate the enhancement request:

Find more posts tagged with

Comments

Stace Webley

A global setting would be great. I agree that in nearly all circumstances you want the filter on. We have created many configurations on lists to display filters by default, so users don't have to toggle it on each time. I know many have been updated by Infor to do this, but I'm not sure it has happened everywhere.

karen-mackenzie

I 100% support this idea! It is very rare that I do not want the filters visible, and I spend a lot of time with end-users navigating them to the filter button. If it's not an option to default it, another couple of ideas would be to let the default be something that could be turned on by an administrator for a particular organization or to store something in memory to keep track of what was last displayed (menu or no menu) and use that

0911060553270289.pdf

unknown

I echo what Stace and Karen have already stated. The time savings of that extra click will add up over time. Please make this the default. Thanks!

Dr. Awesome

Just sharing - the more ya know:

The reason for the current default relates to what we believe are the needs for simplicity for the more casual users like a candidates or employees or executives. They typically do not need, nor do we want them to need to have to filter anything or see the density/complexity of that filter bar.

So, the thinking behind the current design is that the application is designed intentionally and takes a POV on where filtering is interesting, useful, required or necessary, screen by screen. And in those places we add that filtering is shown initially by default.

Part of the issue we face here is a. we've not gotten this totally right and found all of the places (yet) and/or b. we have made the changes to show filtering initially but customer Personalizations or Configurations are blocking the changes.

Overall, I don't see any reason we couldn't discuss or look at adding a User Setting (or maybe even a Role based Configurable Feature maybe) that says - "just always initially display the filter bar on all lists".

Question: do you find that initially display filter is missing in many many spots overall? Or just a few frustrating places? When you run across these do you check if you have a Config/Personalizaiton or that we deliver now that filter should initially display?

Stace Webley

I appreciate the conversation and background to why certain design decisions were made. I think for us it was that initially displaying the filter was not the strategy by Infor (correct me if I'm wrong). We ended up doing configurations to turn it on by default. We just chipped away at lists for awhile doing that. Then displaying the filter by default started happening through the CU's here and there. I'm not sure if it is on in all places where we want it to be, but for simplicities sake a toggle switch per user or configuration parameter would clear it up. I think taking the POV of the every day user/analyst/processors is more beneficial to an organization than designing for the casual user because they don't use it every day and having it on shouldn't hurt their experience. The executives and casual users may not be on a lot of list view pages anyways vs viewing reports or forms. In our organization we are like 95% every day user and 5% casual user. That's my strong bias .

Dr. Awesome

Thanks Stace, all fair points.

The "fun" dichotomy we walk is from a time spent in app perspective "95% every day user and 5% casual user" is probably spot on.

From a number of users perspective though 10% of users are every day and 90% are casual. E.g. the overall Employee and Candidate population is massive when compared to more back-office Recruiter, Generalist , Buyer, etc populations.

Not making an argument or point really. Laying out competing forces that go into all this stuff.

Appreciate your feedback and we'll consider the user setting stuff for sure.

VID023_Extending Resources for Translatable Strings.zip

Stace Webley

karen-mackenzie

For Benchmark, we have done zero configurations around this - we tried to do as much "out of the box" as we possibly could to avoid future maintenance issues. Additionally, for our end users (managers, employee roles) we have the "personalization" option disabled. I would say that the filters do NOT show in more places compared to what we would prefer, especially on many of the admin type menus.

I am all for simplicity, but sometimes there's too much of a good thing (like the Tesla Model 3, for example), where they've simplified so much by getting rid of buttons and various displays that some find it too spartan.

I love the approach of creating a user setting &/or configurable role-based feature (perhaps both?) so that we can set a default for a particular population, then they can override if they prefer things the other way.

Appreciate the perspective and the discussion very much!

unknown

Got to agree that our core users suffer the pain of setting the filters on more than the casual users. Toggles and settings are certainly a desirable feature for us. What about having it "remember" the last setting a user selection? If I turn it on, it stays on for me.

rkhickam

Ditto for Children's Mercy Core users

curtis-evans

What a great, and needed, conversation!

This is a need, and has historically been brought up in a lot of internal meetings/discussions. We have likewise configured it on a few list views. I've also brought this forward on optimization calls with Infor as a need.

For organizations that prefer a streamlined view, perhaps a company level toggle can be added instead to accommodate the need of multiple industry types, and/or similar toggle based on role security where the Controller may want it off, but Inventory Manager benefits from it being on by default.

If implemented, would InforGo reflect the same revision? Presuming yes?

unknown

I'm in alignment with a global setting to have the filter option always 'on' ...it really doesn't add that much additional space for even the casual users. That being said, I'm hoping we'll have the opportunity to talk about the Filter functionality overall at some point and where there are some unique quirks. For example, always needing to hit 'Enter' (it is my understanding that is the only option to apply a filter), the ability to 'clear all filters' (just like Excel), some columns have the magnifying glass and others don't, etc.

Dr. Awesome

Yes! Great area of discussion. We've been rolling out better "Clear" menu options and Clear tags (where you see search tags).

Also, have you see the User Settings to control how search works? We have given users the choice to use Active or Passive searching. Active essentially means Enter isn't needed, the UI fires search requests based on user input of values or operators. Passive means that the UI waits for you to tell it when to search, typically with Enter. Many financial power users prefer Passive as they usually are entering multiple search terms, using operators and the "chatty" searching slows them down.

unknown

I am not aware of the Active or Passive (but that doesn't mean someone else on our team is not!). Is there anything you can send to me on this? TY!

phillip-patton

Just one piece of clarification: the active mode is essentially how it works today. Meaning dropdowns, time fields search automatically when a change is made. But standard enterable fields still require one to type enter.

There is a plan for an "uber active" mode that will search as you type into one of those fields.

@andrew-lipetzky what are we calling that mode again?

Dr. Awesome

The Feb 2022.02 NCR for Landmark web should have looked something like this:

>> What changes were made to the product, and why?
Introduced "Search Mode" to help users control when and how frequently the UI executes searches for them as they type search values, select operators like Contains or Equals or use drop-downs.

Search Modes are available in User Settings and the modes are "Active" or "Passive".

The default mode has been and continues to be "Active".

The "Passive" search mode option is new and means that any change to any search option requires the user to use Enter to perform the search. The UI will never automatically search for you.

>> What impact does this have on me?
None. The default Search Mode has been and continues to be "Active".

>> Do I need to do anything differently?
No. But you can take advantage of the "Passive" Search Mode in User Settings if needed.

Copyright © 2025 Infor. All rights reserved.