[
https://issues.apache.org/jira/browse/OFBIZ-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666070#comment-16666070 ]
Lalit Dashora commented on OFBIZ-6892:
--------------------------------------
Hi,
I faced an issue of status valid change if no transactions are found. The system was throwing an error. The patch provided in this ticket shows commented line for putting lookedUpValue in localcontext.
{code:java}
localContext.put("lookedUpValue", lookedUpValue);{code}
I have fixed this issue in the ticket TicketID: OFBIZ-10377. I have also provided the patch for the same. If this looks good to you then we can proceed.
Thanks!
> new action expire for service engine entity-auto
> ------------------------------------------------
>
> Key: OFBIZ-6892
> URL:
https://issues.apache.org/jira/browse/OFBIZ-6892> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Minor
> Fix For: 16.11.01
>
> Attachments: OFBIZ-6892.patch
>
>
> Relate to the thread
http://ofbiz.135035.n4.nabble.com/entity-auto-and-cancel-operation-td4676929.html on the dev mailing list, I load the patch to manage the action expire.
> When you call *expire* on a entity :
> * if a date field is present on service attribute, OFBiz try to expire it with the given value or with now date
> * else try to expire thruDate field
> * else try to expire *ThruDate or thru*Date field
> The patch contains the new action, a code refactoring to separate each action on dedicate function and unit test associate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
