Bug 801311

Summary: Designer removes sequence flow together with connected nodes
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tomas Schlosser <tschloss>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: VERIFIED --- QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GA   
Target Milestone: ---   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Schlosser 2012-03-08 09:29:09 UTC 
Description of problem:
When sequence flow between two nodes is deleted the nodes connected to it are deleted as well.

Version-Release number of selected component (if applicable):
BRMS-5.3.0-ER4

How reproducible:
every time

Steps to Reproduce:
1. create a simple process with sequence flow between two nodes
2. remove the sequence flow
  
Actual results:
sequence flow is deleted together with the nodes connected to it

Expected results:
sequence flow is deleted and nodes connected to it are kept

Additional info:
Comment 1 Tihomir Surdilovic 2012-03-12 16:38:12 UTC 
I am unable to reproduce this issue locally. Could you provide a specific BPMN2 file and tell me what sequence flow to delete to be able to reproduce? Could you also re-test with latest wars on people.redhat.com/designer/master?

Thanks.
Comment 2 Tihomir Surdilovic 2012-03-12 16:39:38 UTC 
What we added is smart deletion of nodes - if you delete a node, designer is going to also delete its incoming and outgoing sequence flows (those that do not specify a script expression). Deleting a sequence flow however should not delete any connecting nodes.
Comment 3 Ryan Zhang 2012-03-21 10:07:11 UTC 
Please verify this issue on ER5.

Thanks!
Comment 4 Tomas Schlosser 2012-03-28 06:26:33 UTC 
The designer included in BRMS-5.3.0-ER5 fixes this issue.