Bug 1186022 - Designer does not allow add a Timer as boundary event to a task if they are within an embedded subprocess
Summary: Designer does not allow add a Timer as boundary event to a task if they are w...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ER5
: ---
Assignee: Tihomir Surdilovic
QA Contact: Sona Mala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-26 20:32 UTC by Alessandro Lazarotti
Modified: 2020-03-27 20:00 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:00:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
6.1.0 ER6: Invalid boundary event (missing outgoing connection) (139.94 KB, image/png)
2015-03-18 15:53 UTC, Sona Mala
no flags Details
6.1.0 ER6: Valid boundary event (141.07 KB, image/png)
2015-03-18 15:53 UTC, Sona Mala
no flags Details

Description Alessandro Lazarotti 2015-01-26 20:32:51 UTC
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"

Comment 2 Sona Mala 2015-01-27 08:02:04 UTC
I found out that this is a problem for all types of boundary events (Message, Error, Compensation, etc.).

Comment 3 Sona Mala 2015-01-27 08:11:40 UTC
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.

Comment 4 Sona Mala 2015-03-18 15:52:00 UTC
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.

Comment 5 Sona Mala 2015-03-18 15:53:09 UTC
Created attachment 1003312 [details]
6.1.0 ER6: Invalid boundary event (missing outgoing connection)

Comment 6 Sona Mala 2015-03-18 15:53:41 UTC
Created attachment 1003313 [details]
6.1.0 ER6: Valid boundary event


Note You need to log in before you can comment on or make changes to this bug.