The following examples show several TimeZone-specific combinations and how these affect a jobAn Automation Engine object type for a process that runs on a target system. which either runs alone or in a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."].
Several TimeZones are used so that differences in using them become clear. Nevertheless, Automic recommends using complex combinations only in exceptional cases. Keeping clear structures for your processes should always be given priority.
The job properties in the workflow refer to the earliest start time, for example.
Object |
TimeZone |
---|---|
Client |
VIENNA |
Job |
No TimeZone |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Job |
NEWYORK |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Workflow |
No TimeZone |
Job properties within the workflow |
No TimeZone |
Job (in the workflow) |
No TimeZone |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Workflow |
No TimeZone |
Job properties within the workflow |
No TimeZone |
Job (in the workflow) |
NEWYORK |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Workflow |
SYDNEY |
Job properties within the workflow |
No TimeZone |
Job (in the workflow) |
NEWYORK |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Workflow |
SYDNEY |
Job properties within the workflow |
No TimeZone |
Job (in the workflow) |
No TimeZone |
|
Object |
TimeZone |
---|---|
Client |
VIENNA |
Workflow |
No TimeZone |
Job properties within the workflow |
NEWYORK |
Job (in the workflow) |
No TimeZone |
|
See also:
TimeZone Object
Using TimeZones in AE
TimeZones - Overview
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |