A function is transformed into an abstract task in a BPMN diagram if none of the special transformation rules applies to it.
This abstract task is inserted in a system lane that has the same name as the process.
Service task - optional
The model transformation generates an object in the system lane with the Service task symbol type if the function is connected to a business service or an Application system type object, that is, the function must be connected to an object of the Application system type or Service type type by the supports connection. In turn, this service type (business service) must be connected with a service in a function allocation diagram.
In the BPMN diagram, the task is assigned a function allocation diagram, in which the software service type assigned to the business service from the business process model has an occurrence. If the software service type only comprises one operation this has an occurrence there, as well.
If an organizational element is connected to the function, it is ignored during transformation.
User task
The model transformation generates an object of the User task symbol type (Function object type) if at least one dialog (Screen object type) is connected to the function in the business process model, or if the corresponding attribute for the function has been specified.
If both an organizational element and a screen are connected to a function, the User task object will be placed in the corresponding organizational lane. If no organizational element is attached, the User task object is placed in the system lane.
Manual task
An object of the Manual task symbol type is embedded in a lane that is named after the corresponding organizational element. If an object of the User task type is created using the implement as attribute, the object of symbol type Manual task is embedded in the system lane.
The model transformation generates an object of symbol type Manual task if the function is linked to exactly one organizational element that is unique. First, the transformation checks whether or not it is unique at definition level via a connection of type Carries out. If not, then the transformation checks whether or not it is unique at occurrence level. If this is not the case, an object of type Task is generated by which the Task type attribute is specified with the value Abstract.
If more than one software service type is connected to a business service, it is not inserted into the BPMN diagram during the transformation. If a software service type has more than one or no software service operation type, a software service operation type must be added to the BPMN diagram manually.
The following organizational elements are possible:
Position
Role
Organizational unit
Group
Organizational unit type