BPMN task types generated based on the EPC

One single transformation pattern is applied to a function. The transformation tries to apply the pattern that matches the following precedence rules (top to bottom):

First, the value of the implement as attribute is evaluated.

Second, the evaluation checks whether or not there is a screen modeled as a satellite.

Third, the evaluation checks, whether or not the satellite is a Service type object. The transformation generates a Service.

Fourth, the evaluation checks, whether or not the satellite is an organizational element.

If multiple service type objects or multiple organizational elements are connected to a function, the transformation throws an error and no BPMN diagram is created.

First, the semantic check checks whether or not the connections are unique on definition level. If the connections are ambiguous on definition level, the semantic check examines the connections on occurrence level. If the connection is unique on occurrence level, the transformation is executed according to the connected satellite.

The following table shows the matching rules in detail:

Function object in EPC

Transformation result

Value of 'implement as' attribute

Satellite objects

Generated task type

Placed in lane

User task

any

User task

system lane

Service task

any

Service task

system lane

Manual task

any

Manual task

system lane

not specified

one single organizational element

Manual task

Lane of the organizational element

Screen(s)

User task

system lane

one single service type

Service task

system lane

Service type and an organizational element

Service task

system lane

Organizational element and screen(s)

User task

Lane of the organizational element

Service type and screen(s)

User task

system lane

multiple service types

Transformation error

multiples organizational elements

Transformation error

none

Abstract task

system lane