Skip to main content

We just upgraded our dev environment to 4.7.   In a workflow, I have an escalation set by reading an SQL DateTime field via a Smart Object.   The escalation is set for 1 hour later than the value in the field.

 

13779iE87034B7E4331FC0.png

 

For example, the value in the field was 4/28/2017 and 13:44:11, but the escalation was set for 4/28/2017 and 14:44:11 (per confirming the Server.ASync table).   Why is the To DateTime function adding an hour?

 

EDIT:  I had to write the time above in a non-datetime format.  K2 community's site redacted sections of it.

 

Is there a time difference between the K2 Server time and SQL?

Yes, our SQL server and our K2 server are the same time.  Thanks for the suggestion.

 

I think I solved it.  It isn't related to the DateTime conversion function at all.   Simple reason why the escalations fired an hour late....  The business days > Zone Details were an hour off from GMT because of daylight savings.  

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings