nmalin opened a new pull request, #948:
URL: https://github.com/apache/ofbiz-framework/pull/948

   On screen or form actions, I propose to add a condition-date element on 
<entity-condition> to directly add historic filter.
   
   Currently, element entity-condition can have a boolean attribute 
filter-by-date that filter your entity list with fromDate/thruDate on now date 
only.
   
   If you need to navigate on history or use some other date fields, you can't 
use it and need to add a complex condition by hand
   
   With condition-date you can select the date value to use and date fields for 
the filter.
   
   Example :
   
   Complex :
     <entity-condition entity-name="PartyContactDetailByPurpose">
         <condition-list>
             <condition-expr field-name="partyId" operator="equals" 
from-field="parameters.partyId"/>
             <condition-date from-field="order.orderDate" 
ignore-if-empty="true">
                 <date-field field-name="fromDate">
                 <date-field field-name="thruDate">
                 <date-field field-name="purposeFromDate">
                 <date-field field-name="purposeThruDate">
             </condition-date>
         </condition-list>
     </entity-condition>
   
    Simple :
     <entity-condition entity-name="PartyContactDetailByPurpose">
         <condition-list>
             <condition-expr field-name="partyId" operator="equals" 
from-field="parameters.partyId"/>
             <condition-date from-field="order.orderDate"/>
         </condition-list>
     </entity-condition>
   
    Default :
     <entity-condition entity-name="PartyContactDetailByPurpose">
         <condition-list>
             <condition-expr field-name="partyId" operator="equals" 
from-field="parameters.partyId"/>
             <condition-date/>
         </condition-list>
     </entity-condition>
   
   Improved:
   Implemented:
   Documented:
   Completed:
   Reverted:
   Fixed:
   (OFBIZ-)
   
   Explanation
   
   Thanks:
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to