[ 
https://issues.apache.org/jira/browse/OFBIZ-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563205#comment-14563205
 ] 

Christian Carlow commented on OFBIZ-6419:
-----------------------------------------

OFBIZ-6428 will add the sort enhancements to this issue.  The plan is to 
implement some way to identify that a form is intended to be used for finding 
records and then allow the extra reporting options to appear next to fields 
like ignoreCase does.

This would allow for the same form and query to be used rather than creating a 
separate form for every little difference which I often feel is too redundant 
and becomes more difficult to manage.

My next train of thought is to find a way to define defaults for the new find 
options so they can be automatically selected.  This could lead the way for end 
users to create and save their own custom reports as well but that part would 
likely need to be driven by the database.

> Improve form widget find functionality as a generic reporting tool to offer 
> more power to the end user
> ------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-6419
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6419
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Christian Carlow
>         Attachments: OFBIZ-6419.patch
>
>
> This is a container issue for future issues that work toward enhancing the 
> form widget find functionality as a more generic reporting tool.
> Controls similar to ignore case should be added to find fields to allow end 
> users to for example: hide result fields, sort by multiple fields, 
> group/summarize by fields and choose grouping color
> Most of this functionality is meant to allow a single form and entity query 
> to handle multiple reports that use the same data but hide, sort, and 
> group/summarize fields differently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to