Definition of a Single-Step Task 

Use

You use a single-step task to define an activity that can be executed within a workflow definition or independently. This activity can be a transaction in the R/3 System.

You have to create new single-step tasks as standard tasks. Customer tasks can only be edited now. There will be no functional enhancements for customer tasks.

Single-step task as a single step

It is not always necessary for a complex workflow definition involving several steps to be executed to process a business task. Often a single step in the form of a standard task can perform the function required.

Single-step task as part of a workflow definition

A single-step task can be part of a workflow definition as a step of the type activity. In the workflow definition, additional information can also be specified regarding responsibilities and deadlines.

If dialog with a user is required to execute the single-step task, all possible agents receive a dialog work item in their Business Workplaces. If one of the recipients executes the work item, the relevant activity is executed.

Integration

Single-step task activity

You define the activity of the single-step task using an object type method of one of the object types defined in the Business Object Builder.

Possible agents of single-step tasks

The possible agents of a single-step task are specified in the relevant definition. These possible agents can be defined with reference to the organizational plan of the enterprise, with the consequence that the same task is offered for execution to several users, who have the same authorizations from an organizational perspective, in their Business Workplaces.

If the task is reserved by a recipient, it is removed from the Business Workplaces of the other recipients.

If the task is used within a workflow, you can define responsible agents in the workflow definition. The recipients of the work item are all users who are both responsible agents and possible agents.

Prerequisites

The object type method and the object type are defined, tested and generated.

You do not have to have defined the object type and its methods yourself. You can also use methods supplied as standard.

Features

The definition of single-step tasks is spread across several tab pages. You can make all the mandatory specifications on the tab page Basic data. The specifications on the other tab pages are optional.

Customer tasks are processed on a screen without tab pages. But the activities to be carried out are the same.

Activities

You should adhere to the following sequence when defining single-step tasks (and analyzing existing single-step tasks):

What?

Where?

Maintain names, work item text, object type and method

Tab page Basic data

Maintain agent assignment

Additional data ® Agent assignment ® Maintain

Maintain elements in task container

  Container

Maintain triggering events

Tab page Triggering events

Maintain terminating events

Tab page Terminating events

Maintain default roles

Tab page Default roles

Maintain description and notification texts

Tab page Description

Maintain additional data

Additional data ® Selection criteria...
Additional data
® Classification ® Change

Maintain SAPphone properties

Tab page SAPphone