Handling timezone - Community - Arcana Development

The solution presented in the recent hotfix raises other issues, particularly for larger organizations.

"""
When importing jobs from adTempus 3.x, trigger times may be shifted to the wrong time zone CR00007122 Defect

When you import an adTempus 3.x export file into adTempus 4, jobs that use Schedule Triggers to trigger at a specified time may end up scheduled at the wrong time due to a time zone shift. This occurs because adTempus 3 erroneously includes time zone information with the scheduled execution times, and adTempus 4 erroneously adjusts the trigger times using this information. specified execution times should always be absolute times regardless of time zone. This problem was corrected to ignore the time zone.
"""

What does "absolute time" mean in this context? Absolute local time or absolute UTC time?

A job is scheduled to run at 05:00 in New York so that it will be complete by 07:00 and ready for the business day.

If the job is moved to a system in Los Angeles and run at 05:00 to complete by 07:00, it would not be ready for business users until 10:00 in New York.

Also, how does Daylight Saving Time work in this context?

You are referring to fix CR00007122, which is not generally available but will be included in the next release.

The Schedule Trigger has a time zone setting that determines what time zone the trigger uses. This has not changed from version 3 to version 4. In your example it would depend on the setting for that option. The default setting uses the time zone of the server, which means that if you move the job to a server in a different time zone it will run at 05:00 in the new time zone. If you need it to run at 05:00 Eastern time regardless of what server it runs on, you need to specify the time zone in the trigger settings.

Daylight Saving is handled based on the rules for the selected time zone.

This fix only relates to the time value, considered independently of the time zone setting. Due to the problem, if you export the job from adTempus 3 in one time zone and import it into adTempus 4 in another time zone, the scheduled time may shift, regardless of the time zone setting. For example, your job was configured to run at 05:00 in the time zone of the server. You export the job and import it in version 4, and now it shows that it will run at 02:00 in the time zone of the server. This is incorrect, as it should still be scheduled for 05:00.