You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Nicolas Malin (JIRA)" <ji...@apache.org> on 2017/07/31 19:47:00 UTC
[jira] [Commented] (OFBIZ-9546) Entity Auto should use nowTimestamp
while expire either thruDate is set or not on entity
[ https://issues.apache.org/jira/browse/OFBIZ-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107852#comment-16107852 ]
Nicolas Malin commented on OFBIZ-9546:
--------------------------------------
Hi Deepak,
At the beginning I imagined the expire system to oriented the update to expire an object, on the past, now or in the future.
* was expired at (correct an historic error)
* expire it (mostly used)
* expire it at (planned)
The better example when we use it is ProductPrice.
What the gain you obtains to limit this like you proposed ?
> Entity Auto should use nowTimestamp while expire either thruDate is set or not on entity
> ----------------------------------------------------------------------------------------
>
> Key: OFBIZ-9546
> URL: https://issues.apache.org/jira/browse/OFBIZ-9546
> Project: OFBiz
> Issue Type: Improvement
> Reporter: Deepak Dixit
> Attachments: OFBIZ-9546.patch
>
>
> Currently Entity Auto expire action set thruDate only to nowTimestamp if entity.thruDate is not set.
> Ideally it should set nowTimestamp each time or at least it should check if entity.thruDate is greater then nowTimestamp then should set nowTimestamp.
> If thruDate is not passed in expire service it means record should be expire immediately. so it should override the future thruDate with nowTimestamp
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)