Basic Data of a Workflow Definition 

Use

You can process the basic data of the workflow definition by selecting in the Workflow Builder. General information about the workflow definition is also displayed here, and you can create and process triggering events, start conditions and start transactions.

Features

Tab page Start

In the area Workflow start by triggering events..., you can define and remove triggering events for the workflow, as well as create and process start conditions for the triggering events. To define a triggering event, enter the relevant object type and the event into the appropriate fields in a line. You can use the F4 input help. You can activate a defined triggering event and process the binding from the event container to the workflow container.

You can process the properties of a triggering event by selecting it and choosing .

You can create start conditions for each triggering event defined. The workflow then only starts if the triggering event has occurred and one of the start conditions defined for it is fulfilled. Use the condition editor to define the start condition. For further information, refer to Binding Definitions from the Event Container and Start Conditions for a Workflow.

In the area ...and/or start transaction(s), you can create a start transaction for the workflow. This start transaction is executed if you start the workflow manually. There are input fields in the start transaction, in which you can assign data to the import parameters of the interface. You can process the layout of the start transaction generated in the Screen Painter.

Tab page Control

You can make settings for the workflow definition here. If you set the indicator Advance with dialog, you can set the indicator individually for each step definition.

If you do not specify anything for maximum node number or maximum subworkflow level, the Customizing settings apply. In the field Performance optimization, you specify what data is to be logged by the system. The more data you have logged, the worse the system performance is.

If you choose Only log errors, the workflow log does not contain any attachments, objects, forwarding information or information in the area Details.

Tab page Responsibilities

Here you define the system administrator for this workflow. If no entry is made, the entry for the party responsible in the definition of the relevant multistep task is evaluated first, then the relevant SAP Business Workflow Customizing entry if necessary.

You can also define a standard recipient for all missed deadlines. This party is notified if the following apply:

For further information, refer to Defining Responsibilities.

Tab page Notification

Here you define the message recipient for completion of the workflow. This party is notified if the workflow is used as a subworkflow and there is no recipient specified in the task definition. Upon completion of the workflow, the text displayed here is sent as an e-mail.

For further information, refer to Defining Responsibilities.

Tab page Change data

All entry, change and activation data of the workflow definition is displayed here.

Tab page Technical information

Here you will find general data about the workflow and a version overview for the workflow definition. The version number of the version being processed in the original development system is displayed in the field Original version. If a workflow is transported into another system, in which workflows are already running for this definition, the version numbers are reconciled.

The indicator Locked against instantiation is maintained in the classification of the multistep task.