Entering content frameBackground documentation Step Types and Their Symbols Locate the document in its SAP Library structure

Symbol

Step type

Runtime function

This graphic is explained in the accompanying text

Process control

The functions Cancel work item or Set work item to obsolete are applied to other work items of the current workflow.

This graphic is explained in the accompanying text

Ad hoc anchor

In the definition, you save workflows that can replace this step. At runtime, an authorized user can select one of the saved workflows. The ad-hoc anchor is then replaced by the steps of this workflow.

This graphic is explained in the accompanying text

Activity

Execution of a task or subworkflow

This graphic is explained in the accompanying text

Condition

One of two branches defined in the workflow definition is processed. The system makes the decision based on defined conditions. When doing this, this system takes account of information from the context of the workflow or the application objects processed.

This graphic is explained in the accompanying text

User decision

The process flow of the current workflow is controlled on the basis of a decision made by the current agent.

This graphic is explained in the accompanying text

Document from template

A document is created from a document template.

This graphic is explained in the accompanying text

Container operation

Elementary arithmetic operations or value assignments are applied to individual elements of the workflow container.

This graphic is explained in the accompanying text

Event creator

An event is created.

This graphic is explained in the accompanying text

Form

The data in a container element that refers to a structure can be displayed, processed, or approved as a form.

This graphic is explained in the accompanying text

Send mail

The text entered in this step type is sent as an e-mail.

This graphic is explained in the accompanying text

Multiple condition

One of several branches defined in the workflow definition is processed. To do this, the system checks the value of a container element in the workflow container.

This graphic is explained in the accompanying text, This graphic is explained in the accompanying text

Fork

The processing that follows takes place in a fork. You can define how many branches have to be executed for the fork to be successfully completed, or you define an end condition in the condition editor.

This graphic is explained in the accompanying text

Undefined step

No function at runtime. Undefined steps always have an outcome.

This graphic is explained in the accompanying text

Loop (UNTIL)

A sequence of steps is processed repeatedly until the defined termination condition occurs.

This graphic is explained in the accompanying text

Loop (WHILE)

A sequence of steps is processed repeatedly as long as the defined comparisons apply. The system leaves the loop when the basis of comparison does not agree with any of the comparison values.

This graphic is explained in the accompanying text

Wait for event

The system waits for a specific event. The work item is only completed if the expected event occurs. The event can also be triggered by the occurrence of an XML document.

This graphic is explained in the accompanying text

Web activity

The content of container elements is sent to a URL unchanged or in the form of a generated XML document. The step can wait for a reply. Communication with a process started by a Web activity is possible. A process started by an XML message can communicate with its caller.

 

 

Leaving content frame