Empty Filter vs. Default Value in Window Filtering

[metas-mk]

Is this a bug or feature request?

Feature Request.

What is the current behavior?

When using Window Filters, then the initial behavior is that Flags are considered as null/ not set. As soon as you click a Flag filter then results are Filtered by FlagValue = 'Y'. When clicking off, everything is filtered by FlagValue = 'N' and the user has no single possibility to reset to null to not consider anymore.

Which are the steps to reproduce?

Try Filtering in Product Price Window.

What is the expected or desired behavior?

Similar to ID Fields one should be able to switch off/ nullify the filter with some kind of 'X' (x in a circle) to empty the filtering criteria without resetting the whole window filter.

[teosarca]

what about changing the checkbox filter to Yes/No/empty dropdown, like we do in swing?

[metas-mk]

A. Don't like that with a dropdown. A flag is clicked with 50% less effort and more visible. But would be the info for backend what's needed, From user Interface, I would prefer something like this when a flag in not null. WDYT?

[metas-mk]

B. other Alternative: have a flag input which can take and show 3 different status.
a. Green + ticked = 'Y'
b. Gray + X = 'N'
c. Empty = null

edit: discussed w/ teo. not convinced about this alternative B. because its a different feel and usage as in "normal" window (not filter)

[metas-mk]

Lets move on w/ Proposal A. (initialization possibility w/ circled X. @cadavre WDYT?

[metas-mk]

Moved further discussion to webui-frontend. closing here.

[cadavre]

Whao, never 've seen this. 😲 Please link to webui-frontend.

[metas-mk]

I believe that. But what other possibilities do you see to show the user which filters are set and which not? If we cannot show the user cannot see that she/ he is explicitly using a flag filter = 'N' because it could also just be [null] --> not set

[cadavre]

I definitely understand this – we need some additional state here for sure!

[teosarca]

Fontend task: metasfresh/metasfresh-webui-frontend-legacy#762