Hi,
We have a business need to make filter component easier to use for analysts. Current the UI in Clover filter component provides a way to drag and drop fields and use symbols (>, > =, NOT, etc) in filter criteria but it does not do formatting. I was wondering if its possible for us to take this component and extend it to make the filter expression UI easier to use.
I have attached a screen shot indicating what we need to change.
Clover Filter Component.png
Please let us know if this is feasible or not?
Thanks!
We have a business need to make filter component easier to use for analysts. Current the UI in Clover filter component provides a way to drag and drop fields and use symbols (>, > =, NOT, etc) in filter criteria but it does not do formatting. I was wondering if its possible for us to take this component and extend it to make the filter expression UI easier to use.
I have attached a screen shot indicating what we need to change.
Clover Filter Component.png
Please let us know if this is feasible or not?
Thanks!
-
Hi
It is not possible for a user to customize the components. Could you please describe in detail how would you like to extend the component (editor) and what do you mean by that formatting? I could create improvement proposal, if the change will be beneficial for other users too.
Best regards -
Hi,
Thank you for your response. There are few improvements we would like to provide to our end users who are not programmers or technical:
1. When you want to put an operator next to a field name, currently it does not add space between field name and operator. This makes it hard to read and makes query invalid. It will be nice to when you put an operator in the expression editor it adds leading and trailing space. Same should be true if you drag a field into expression editor.
2. It will be great to have a way to get values from look up tables to be used in query editor so the end users can use it in where clause rather than typing or copy paste which can be error prone.
Thanks -
Hi - 1. This behavior is already reported. I modified the ticket so it covers all the aspects that can be improved. You can see it here.
2. Could you, please, describe how exactly should it work? What type of lookup table should it work with? Should it look like some kind of context help? Etc.
Best regards
Please sign in to leave a comment.
Comments 3