Inside Automation Engine > Date and Time > Using TimeZones in the AE

Using Time Zones in the Automation Engine

Time plays a key role in AE when programs communicate with each other, tasks are activated, conditions evaluated, data is saved etc. Time becomes even more important when AE is used on a global basis across several TimeZones and when interconnected tasks are to run properly.

The components (server processes, agents, databaseA database is an organized collection of data including relevant data structures., etc.) internally use the internationally agreed and precise UTC time scale. Nevertheless, TimeZone objects can be created to indicate local times which can also be used in tasks and script elements. TimeZones contain specifications such as the point in time when the clocks are changed to winter time or daylight savings time, or the time difference to UTC. The name of a TimeZone object must not be comprised of more than 8 characters.Note that TimeZones consisting of more than 8 characters cannot be selected in other objects!

The folder "TEMPLATE" in the system client 0000 contains the following TimeZone templates:

CET - Central European Standard Time
CST - Central Standard Time
EST - Eastern Standard Time
GMT - Greenwich Mean Time
PST - Pacific Standard Time
SYD - Sydney Standard Time

Usage

The created time zones can be used for various purposes such as:

Usage	Tab
Client	"Attributes"
User	"User"
Setting in the UserInterface	"TimeZone/Calendar"
Executable objects	"Attributes" "Runtime"
Properties in executable objects (workflow and schedule)	"Checkpoint" "Earliest" "Dependencies" "Runtime"

Already when creating a new client you can specify a time zone. This time zone is then used within this client when tasks are processed and for indicating date and time. If a different time zone is required for a particular object, it can be specified in this object's Attributes tab. Time zones can also be specified for task properties in workflows and Schedules. These time zones will then be given priority.

Hence the appropriate time zone is searched for in the following order:

Object settings -> Client

The client's time zone is used if no time zone has been selected in the object. UTC is used if no time zone has been specified at all. Automic recommends indicating a time zone at least in the Client object.

For the properties of workflows and schedules (such as the latest start time), either the time zone selected there or the time zone of the workflow or Schedule object is used. If there is also no time zone available, the client's time zone or UTC is used.

For starting tasks in schedules, the particular schedule's time zone is valid!

Display

Time zones specified for a user serve mere information purposes (such as in the Message Window). The same holds true for UserInterface settings which can be specified by each user. Both do not influence the processing of tasks. Therefore, it is not important to know the user who has started the object.

Script

Time zones are additionally used in many script elements. The following list shows the ones in which time zones are assigned as parameters.

Script Function	Description
CONV_TIMESTAMP	Converts date and time for use in another time zone.
SYS_DATE	Returns the current date at the beginning of the script processing.
SYS_DATE_PHYSICAL	Returns the current date.
SYS_TIME	Returns the current time of day at the beginning of the script processing.
SYS_TIME_PHYSICAL	Determines the current time of day.
SYS_TIMESTAMP_PHYSICAL	Provides current date and time.

Additional script elements referring to date and time are found in the document Script Elements - Ordered by Functions

Logical Date

When executing tasks with options and creating forecasts, you can indicate a so-called "logical date". In this case the date specified in the calendar conditions of workflows and Schedules is used instead of the current date.