![](https://csdnimg.cn/release/download_crawler_static/1810784/bg13.jpg)
Tutorial: Workflow Modeling April 2006
Unit 4: Defining and Inserting Task "Create Notification of Absence"
Business Workflow - Tutorials 14
If your request is rejected, you can revise it and resubmit it
for review or withdraw it completely.>
4. Choose Back and save the task definition.
8. Exit the task definition with
.
Interim result
You have now defined your first task. This task is used in the activity that you created in the
Workflow Builder.
Completing Activity
When you exit the task definition, the Define Container Elements and Binding dialog box is
displayed in which the system proposes a change to the workflow container and a binding
definition:
● The upper part of the dialog box contains proposals for new container elements in the
workflow container.
The system proposes that you create a local container element in the workflow
container, which can store the reference to the
notification of absence created in this
step. The element has the technical name
AbsenceForm.
● The lower part of the dialog box contains proposals for a binding definition from and to
the task container.
The system proposes that you define a binding from the task container to the workflow
container. This binding transports the reference to the generated object (i.e. the created
notification of absence)
from the task (from the _WI_Object_ID element in the task
container)
to the workflow (to the AbsenceForm element in the workflow container).
For more information on automatic binding definition proposals, see Binding Definitions from
the Workflow Container [Extern] and Binding Definitions from the Task Container [Extern] in
the documentation on
SAP Business Workflow.
...
1. Confirm the proposal with .
The new
AbsenceForm container element is displayed in the workflow container. Local
container elements are marked
. The remaining elements in the workflow container
are workflow system elements. For more information, see Workflow System Elements
in the Workflow Container [Extern].
2. Enter a text to describe the step.
You can, of course, leave the name of the task that is proposed by the system. The
name entered here is used to identify the step in your workflow definition.
3. Go to the
Outcomes tab.
All of the possible outcomes for this step are displayed here. Only the outcome
Step
executed
is active.
4. Enter a text for the name of the active outcome.
Enter the name (proposal: <
Application filled out>) in the Step executed line.
Each step has at least one subsequent outcome (in this case:
Step executed). The
name is the text with which the outcome is labeled in the workflow definition.
The
Form does not exist and Form could not be generated outcomes are the possible
exceptions that could occur in the method execution. You “run the risk” of not
intercepting these exceptions and not modeling any exception handling in your