Improved: Add condition-date on entity-condition element (OFBIZ-13349)#948
Open
nmalin wants to merge 1 commit intoapache:trunkfrom
Open
Improved: Add condition-date on entity-condition element (OFBIZ-13349)#948nmalin wants to merge 1 commit intoapache:trunkfrom
nmalin wants to merge 1 commit intoapache:trunkfrom
Conversation
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>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On screen or form actions, I propose to add a condition-date element on 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 :
Simple :
Default :
Improved:
Implemented:
Documented:
Completed:
Reverted:
Fixed:
(OFBIZ-)
Explanation
Thanks: