[ 
https://issues.apache.org/jira/browse/UNOMI-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396022#comment-17396022
 ] 

Kevan Jahanshahi commented on UNOMI-482:
----------------------------------------

This have been fixed by: [https://github.com/apache/unomi/pull/329]

To be able to set the current date using the SetPropertyAction:
 * SetPropertyAction with setPropertyValue: 'now' is now deprecated,
 * instead of using '*setPropertyValue*' you can directly use 
'*setPropertyValueCurrentEventTimestamp*' or '*setPropertyValueCurrentDate*'.

> SetPropertyAction eventArrivalTime
> ----------------------------------
>
>                 Key: UNOMI-482
>                 URL: https://issues.apache.org/jira/browse/UNOMI-482
>             Project: Apache Unomi
>          Issue Type: New Feature
>            Reporter: Amit Cohen
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> In setPropertyAction, "now" in propertyValue is being translated to 
> event.timeStamp.
> I would like to add support for "eventArrivalTime" which will be the current 
> time in which the event got into Unomi.
> an example to emphasize the need - 
> event1 arrived with timestamp - 8:00
> then, event2 arrived with timestamp - 7:00
> the profile will be updated with lastUpdatedTime - 7:00, which is not true
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to