This objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task records values for local time evaluation. By using these current values, UTC (Coordinated Universal Time), the AE time base, is converted into local time. The local time is then always displayed in the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."], for example. Vice versa, the local time that results from userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. activityAn activity (or task) is an entity that can be planned, assigned to a user or a team and tracked with respect to their plan and state (started, cancelled, suspended, completed). in the UserInterface or direct user entries, is converted to UTC by the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..
Object class: System object
Object
type (short name): TZ
Objects for most time zones are supplied with AE in clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. 0000. User-defined TimeZone objects can still be created in client 0000 or in local clients.
A TimeZone can be established as a default setting for each client . If no time zoneIt defines a local time. A particular Automation Engine object type. is defined, the Automation Engine automatically uses UTC.
Note that the name of a TimeZone object is limited 8 characters. If this number is exceeded, this TimeZone cannot be selected for other objects.
TimeZone objects that have been transferred with the Transport Case are not automatically refreshed. Calculations for objects that use them are based on UTC. This affects all time conditions such as calendarAn Automation Engine object type that defines a set of days based on calendar keywords. settings or start times and can be avoided by opening and storing any TimeZone object of your choice. All TimeZone objects are then refreshed.
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |