If a timer is added as boundary event to a task which is in a subprocess, its bpmn2 tag is not changed from "bpmn2:intermediateCatchEvent" to "bpmn2:boundaryEvent", resulting in: "Timer node 'timer' has no outgoing connection." Steps to Reproduce: 1. Drag and drop a timer to a user task in a embedded subprocess 2. Save the process Actual results: The Problems tab show: ""Timer node 'timer' has no outgoing connection." " - in source code is generated an intermediateCatchEvent Expected results: No errors. The code generated should be "bpmn2:boundaryEvent"
I found out that this is a problem for all types of boundary events (Message, Error, Compensation, etc.).
What is the target release? It seems like a problem of 6.0.3. I cannot reproduce this issue in 6.1.0 ER4. I will create a test which covers it.
I can confirm that the catch intermediate event is changed to the boundary event, when it is attached to an activity. Validation results were affected by this change. In case that the event represents an intermediate event. Validation shows: Timer node 'a' [7] has no incoming connection. Timer node 'a' [7] has no outgoing connection. In case that the event represents an boundary event. Validation shows: Timer node 'a' [7] has no outgoing connection. I think that the current behaviour is the expected one. I cannot find any sentence in BPMN2 specification which says that the outgoing connection is not required for a boundary event.
Created attachment 1003312 [details] 6.1.0 ER6: Invalid boundary event (missing outgoing connection)
Created attachment 1003313 [details] 6.1.0 ER6: Valid boundary event