Timestamp Conversion
Howdy,
I am populating the "scheduled start time" of a task based on a date field in the parent request. I'm seeing a weird behavior where the unix timestamp doesn't always produce a good date. For instance, one ticket had a timestamp of 10/02/2017 3:40pm. That translates to 1506958800. However, when I plug this into the scheduled start time for the task, it gave me a weird date of "1/18/1970 4:35am".
I did some playing around, and adding 000 to the end of the timestamp seemed to get it to the right date, making me think that the scheduled start date is in Milliseconds instead of seconds. However, that translation does not apply universally. When added to other dates, I get wild timestamps (year 2447, etc).
Can you help me decipher how to properly set "Scheduled Start Time" in tasks programatically?
I am populating the "scheduled start time" of a task based on a date field in the parent request. I'm seeing a weird behavior where the unix timestamp doesn't always produce a good date. For instance, one ticket had a timestamp of 10/02/2017 3:40pm. That translates to 1506958800. However, when I plug this into the scheduled start time for the task, it gave me a weird date of "1/18/1970 4:35am".
I did some playing around, and adding 000 to the end of the timestamp seemed to get it to the right date, making me think that the scheduled start date is in Milliseconds instead of seconds. However, that translation does not apply universally. When added to other dates, I get wild timestamps (year 2447, etc).
Can you help me decipher how to properly set "Scheduled Start Time" in tasks programatically?