You use aTask to define an activity that can be executed within a workflow definition or independently (as a single step). This activity can be an SAP System transaction.
You have to create new tasks as
Task as a single step
It is not always necessary for a complex workflow containing 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.
If dialog with a user is required to execute the task, allpossible agents become recipients of the relevant dialog work item and receive it in their Workflow Inbox. You can limit the number of recipients by entering a rule for agent determination on the Default Rules Tab Page. When one of the recipients executes the work item, the relevant activity is executed and the work item can no longer be executed by the remaining recipients.
Task as part of a workflow definition
A 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 task, allrecipients receive a dialog work item in their Workflow Inbox. When one of the recipients executes the work item, the relevant activity is executed and the work item can no longer be executed by the remaining recipients.
Activity of task
You define the activity of the task using anobject type method of one of the object types defined in the Business Object Builder.
Possible agents of Tasks
Thepossible agents of a 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 used within a workflow, you can defineresponsible agents in the workflow definition. The recipients of the work item are all users who are both responsible agents and possible agents and were not explicitly excluded from processing.
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.
The definition of 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.
You should adhere to the following sequence when defining tasks (and analyzing existing tasks):
|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|
|Maintain triggering events|
Tab page Triggering events
|Maintain terminating events|
Tab page Terminating events
|Maintain default rules|
Tab page Default rules
|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
You only need triggering events of a task if you want to execute the task as a single-step. You can do without the entry of default rules if the task is only used within workflows.