Simplified Workflow Definition 

Use

In many cases, workflow definitions must be created in which only a single object is processed in some form in several sequential or parallel steps. The possible operations on this object are available in the form of methods and the single-step tasks derived from them.

Prerequisites

To use an object type in a simplified workflow definition without encountering problems, you should make sure during definition of the object types that the methods only require the object reference and not additional method parameters, since these cannot always be created using automatic binding.

Features

The Workflow Wizard first requests the object type on whose object the operations of the workflow definition are to be performed. The system automatically creates a container element with an object reference to the requested type in the workflow container.

Then you choose the tasks that are to be executed in workflow. Agent selection can be performed. The system caters for all appropriate object references of the tasks in the binding. All other input and output parameters required and container elements in the workflow container are created by the system.

You must check the generated workflow definition in the Workflow Builder.

The tasks are arranged in sequential steps as standard. It is possible to group individual steps in a fork. The forks cannot be nested in each other. Other modeling elements, such as loops, are not supported.

Activities

All tasks of the selected object type are displayed in the left-hand part of the screen. Using the pushbuttons Add and Add all, the selected tasks can be transferred to the field on the right-hand side.

Cut and Paste can be used to define the sequence in which the single-step tasks are to be executed.

Several tasks can be grouped together in a fork with Select block. Identical numbers then indicate this association.

The pushbuttons Agent assignment and Task details take you to task processing.