[
https://issues.apache.org/jira/browse/OFBIZ-13184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne reassigned OFBIZ-13184:
----------------------------------------
Assignee: Gil Portenseigne
> 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
> Assignee: 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)
