Definition of Terminating Events for Tasks

Use

You use this function to define the terminating events of a task.

  • You must define at least one terminating event for tasks that refer to an asynchronous object method. At runtime, the relevant work item is only terminated when a terminating events occurs.

  • You can define a terminating event for tasks that refer to a synchronous object method. At runtime, the relevant work item is terminated when the synchronous method has been successfully executed or when one of the terminating events occurs.

Terminating Events

The terminating events of a task express the possible end statuses of the task.

A terminating event always refers to one object for which the event must be triggered. You define the object for which the event must be triggered in a container element in the task container.

The following example illustrates this for a classic business object (BOR):

Integration

If the task is used as a step in a workflow definition, you can go to a separate modeling branch when the event occurs. For more information, see Maintenance of Tab Page Outcomes.

If a task is terminated by an event, the execution of the workflow is continued. The method does not necessarily have to have been executed. If a task is aborted or non-defined processing statuses arise, the work item is not terminated since no event is created. The workflow is not continued.

Activities

You maintain the terminating events on the tab page Terminating Events.

  • You specify a container element of the task container, which at runtime contains a reference to the object for which the event has occurred. This is generally the task container element _WI_Object_ID. The fields Object type category and Object type are filled automatically.

  • You identify the event by specifying its instance ID. The event must be defined for this object type.

If you want to check the properties of the terminating event, select . The properties of the instance linkage are displayed and can be changed.