Use
To define the flow of the approval process in the system, you first create a multistep task workflow template.
For further information, refer to
Definition of Multistep Tasks in the SAP Business Workflow documentation.Procedure: Creating a workflow template
This takes you to the Task: Maintain screen.
The Workflow Template: Add screen is then displayed.
Entering the basic data for the workflow template
Abbreviation:
< ini _ws>Name
: <Workflow: notification of absence ( ini )>The system has now allocated an 8-digit number for your workflow template. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. This number together with the letters WS forms the workflow ID. Make a note of the ID so that you can later call the workflow more quickly.
Entering a workflow description
The SAPscript text editor is then launched.
<You can use this workflow to create a notification of absence. This will then be sent to your superior for review. You will be notified of the result of this review.
If your request is rejected, you can revise it and resubmit it for review or withdraw it completely.>
Determining agents
To enable the workflow template to be started in dialog, the workflow template must be assigned to its possible agents.
The workflow template: agent assignment screen is displayed.
The dialog box Task: <Workflow: Notification of absence (ini)> is displayed.

Designating your workflow template as a general task means that every user in the system is authorized to start this workflow template in dialog.
Result
You have now created a workflow template as a "framework" for a workflow definition.
To create a workflow definition, you need tasks that are used as steps in the workflow definition.
Additional information: Tasks
A task can either be a
single-step task or a multistep task. In our example of the notification of absence, making the application and checking the application are single-step tasks. The entire procedure involved in processing a leave request consists of these (and other) single steps, and is therefore a multistep task.
In this tutorial, a single step task is generally described as a task. The difference between the task types is only explicitly explained if there is a risk of confusion over multistep tasks. The term workflow is used as the umbrella term for the workflow template (and thus the multistep task) and the workflow definition. More precise differentiation only takes place if there is a risk of confusion.
On a technical level, the main difference between single-step tasks and multistep tasks is that:
A workflow definition is made up of a sequence of different steps (for example, all steps required to process a leave request).
Standard tasks and workflow templates are client-independent. Customer and workflow tasks are client-dependent. Customer and workflow tasks are no longer supported and are therefore no longer used in this tutorial.
An Activity is a possible step type in a workflow definition. An activity refers to a task. It references a task, which can be a single-step or multistep task (subworkflow).
For further information, refer to
Tasks and Task Groups in the SAP Business Workflow documentation.