Developing Business Logic


When you define a workflow, you can proceed in different ways:

·        Bottom-Up: You start by checking whether all required object types, tasks and events exist, and define them, if required. You then define the flow logic for the business process, by defining a workflow with the relevant steps.

·        Top-Down: You start by defining the flow logic for the business process, by defining a workflow with the relevant steps. You then check whether all required objects, tasks and events exist, and define them, if required.

Special Workflows

The procedure described below generally applies to defining workflows. For more information about special workflows, see:

·        WebFlow Function: enables you to execute workflows across the Internet

·        Ad Hoc Workflow: enables ad hoc agent assignments and ad hoc enhancements

·        Review Workflow: enables a reviewer to start a review workflow from the graphical workflow display of a running workflow. The review workflow displays the data of the running workflow.

Process Flow


       1.      Objects and object types: You check whether all required objects and object types exist. If required, you extend the definition of existing object types or define your own.

See also: Maintenance of Object Types

       2.      Tasks: You identify the tasks involved in your business process. If required, you define your own tasks.

See also: Tasks and Task Groups

       3.      Events: You identify the events required to initiate and control the workflow and check whether these events are defined for the relevant object types. You insert the event in the corresponding object type definition, if required. You must also ensure that the event is created.

See also: Using Events

       4.      Workflow: You define the business process as a workflow.

To define the flow logic, insert the required steps into the workflow definition.

See also: Step Types

To specify which data the workflow processes, you define the corresponding container elements and the binding between the containers.

See also: Definition of a Container and Definition of Binding

A workflow often processes objects that are related to each other, such as a quotation and its corresponding sales orders. To identify such related objects, you can define correlations.

See also: Correlating Objects

       5.      Start options: You specify how the workflow is started.

See also: Definition of Options for Starting a Workflow



       1.      Workflow: You define the workflow with the relevant steps.

See also: Top-Down Modeling

       2.      Object types, tasks, and events: You check whether the required object types, tasks, and events exist, or if required, define them as described under Bottom-Up Modeling.