Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 864833

Summary: Lose Boundary Event when I move it along boundary of task
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Sona Mala <smala>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.1CC: kverlaen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:55 UTC 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:
Attachments:
Description Flags
Video of reproduction the problem none

Description Sona Mala 2012-10-10 08:37:43 UTC
Description of problem:
If I want move the boundary event along the boundary of the task then sometimes happened that the boundary event is changed to the intermediate catch event. 

Version-Release number of selected component (if applicable):
BRMS 5.3.1 ER1, designer 2.3.1-DEV

How reproducible:
Depends on position of mouse (if mouse is outside of the task then boundary event is changed to intermediate catch event).
The green boundary of task appears when the mouse is over the task: 
 - If I catch event at the top then the green boundary show up, the mouse is over the task and the boundary event stays. 
 - If I catch event at the bottom then the green boundary does not show up, the mouse is out of the task and the boundary events is changed. 


Steps to Reproduce:
1. create new BPMN2 asset
2. create the process (Start->Task->End)
3. attached boundary event
4. catch event at the bottom (mouse is out of the task) and move along a boundary of the task.
  
Actual results:
The boundary event is changed to intermediate catch event. It depends on position of mouse.

Expected results:
The boundary event stays. It depends on position of node (corners or midpoint). Please if you choose midpoint then add some position tolerance.

Additional info:
You can find this problem only if you look inside BPMN2 source code or you use validator (Mark by alert "Node has no incoming connections.". But validator is broken for this issue, now. See bz 864794). There is no difference between property bars (same title of property bar).

Comment 1 Tihomir Surdilovic 2012-10-11 21:47:11 UTC
Not sure what to do about this one. The only way the editor is going to recognize the event as a boundary even if the tasks borders are "lit" green. So as you move your event along the task, make sure that its borders are green before you release the mouse button.

Comment 2 Sona Mala 2012-10-12 12:29:24 UTC
Created attachment 625959 [details]
Video of reproduction the problem

Is there any possibilities that green lines will sensitive to position of node?

You can see five types of work with boundary event:
  - case 1: catch node at the top ... green line appears automatically (mouse is in)
  - case 2: catch node at the bottom ... green line does not appears automatically (mouse is out and boundary event is lost)
  - case 3: workaround of case 2: 
         - be sure that green line appears 
         - that means lift mouse and node into task
  #user just catch node and immediately push it (node has same position, mouse neither) 
  - case 4: specific part of case 2. ... green line does not appear (boundary event is lost)
  - case 5: specific part of case 1. ... green line appears 

There is no quick visual control, just check a BPMN2 process.

For user can be a problem check the green line every time when release a mouse.

Comment 3 Tihomir Surdilovic 2012-10-12 15:18:42 UTC
I will look into making boundary area more sensitive. If successful will report here.

Comment 11 Red Hat Bugzilla 2025-02-10 03:20:55 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.