Inside Automation Engine > Executing Objects > Executing Objects

Executing Objects

Executable objects such as jobs can be processed manually or subject to superordinate objects. They run through four stages which together form the execution of an object.

In detail, the individual executions depend on activation type, object type and object content.

Executed objects are also referred to as tasks. Hence the processing of objects is described whenever the Automation Engine Documentation refers to tasks.

The terms "Parent" and "Child" are commonly used with objects. An object is referred to as a child if it is activated through a superordinate task (parent). An example is a Schedule object (parent) which processes a FileTransfer object (child).

Two points in time are important during object execution: activation and the start time. During the activation time, the task is displayed in the Activity Window. Mostly, tasks do not start immediately because usually they are subject to superordinate objects such as Schedule objects.

When you execute a workflow, it's children will not be affected by the workflow's TimeZone setting. Any workflow task-specific changes you want to make need to be made on one of the tabs of the Properties window for each task.

Refer to the chapter "Inside AE" to obtain more detailed information about how the settings made in Workflow and Schedule objects affect processing.

A group must only run once at a time. The number of parallel executions of other executable objects depends on the settings made in the Attributes tab.

For Job objects the status "ENDED_OK" will be set as soon as the execution has ended. Post Processing options will not result in a change of the object's status to "ACTIVE".