[jira] [Commented] (OFBIZ-13184) Add alternative to performFind group option

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on OFBIZ-13184:
---------------------------------------------------------

Commit 531f2bda92095f2693e6f70cb1711326b588600e in ofbiz-framework's branch refs/heads/trunk from Gil Portenseigne
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=531f2bda92 ]

Improved:  Add alternative to performFind group option (OFBIZ-13184) (#860)

* Test creation before refactor createConditionList method

* Refactor createConditionList to avoid redundancy

* Implementation and test of OR_AND alternative

> Add alternative to performFind group option
> -------------------------------------------
>
>                 Key: OFBIZ-13184
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13184
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Gil Portenseigne
>            Priority: Minor
>
> With OFBIZ-10195 was contributed a way to manage more complex conditions in performFind service for find screens.
> The origin contribution was to offer union within a group condition, this contribution has change through collaboration before going into the code base to intersection.
> Today the grouping option allow : 
> <field name="field1"><text-find/></field>
> <field name="field1_grp"><hidden value="1"/></field>
> <field name="field2"><text-find/></field>
> <field name="field2_grp"><hidden value="1"/></field>
> <field name="field3"><text-find/></field>
> <field name="field3_grp"><hidden value="2"/></field>
> <field name="field4"><text-find/></field>
> <field name="field4_grp"><hidden value="2"/></field>
> The grouped search fields criteria will be added during the search by the AND operator. Both group are union-ed resulting to (field1 AND field2) OR (field3 AND field4) AND notGroupedFieldCond
> In one of our customer project we needed a case : 
> (field1 OR field2) AND (field3 OR field4)
> That cannot be solved with current implementation.
> This improvement offer a way to change operator that are used inside and between groups, with a new alternative using :
> <field name="groupConditionOperator"><hidden value="OR_AND"/></field>
> This is a new parameter of the type of noConditionFind, that will control the way the final group condition is built.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)