The semantically different task types from BPMN are either determined via the object symbol in ARIS or via the objects that the task is connected to. The following rules apply:
An object with the symbol User task is always transformed in line with its symbol. Associated objects that do not match this symbol are ignored.
If an object of the Task type is connected with a service the object is handled like an object of the Service task type during the transformation. Organizational elements or a different symbol are ignored.
If a task is connected to an organizational element and the first two cases do not apply, the object is transformed like an object of the Manual task type.
If the Error handler, Cancelation handler, or Timeout handler attribute has been activated for a task in the webMethods area, the task must not have any incoming or outgoing connections. In the <Package> element, a WorkflowProcesses ext:errorHandler, WorkflowProcesses ext:timeoutHandler, or WorkflowProcesses ext:cancelHandler element is generated, which references the GUID of the object.
If an object does not have any connections to another object, the transformation is performed in line with the object symbol. This applies to the following task types: Abstract task, Send task, Receive task, Business rule task, and Script task.
Graphical information from ARIS, such as size, position, or color, is transformed into an element of the NodeGraphicsInfo type of the activity in XPDL.