Bug 1230950 - [GSS] (6.1.z) Unable to drag a workflow pattern from the menu and drop it inside a swimlane in BPM Suite 6.1
Summary: [GSS] (6.1.z) Unable to drag a workflow pattern from the menu and drop it ins...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: CR1
: 6.1.0
Assignee: Tihomir Surdilovic
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On: 1230181
Blocks: 1230825
TreeView+ depends on / blocked
 
Reported: 2015-06-11 21:05 UTC by Alessandro Lazarotti
Modified: 2020-03-27 20:04 UTC (History)
7 users (show)

Fixed In Version:
Clone Of: 1230181
Environment:
Last Closed: 2020-03-27 20:04:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alessandro Lazarotti 2015-06-11 21:05:30 UTC
+++ This bug was initially created as a clone of Bug #1230181 +++

Description of problem:
It is not possible to drag a "Workflow Pattern" from the menu and drop it inside a swimlane (wp_insideSwimlane.png). First, you will have to drop it outside the swimlane (wp_outsideSwimlane.png), select all again and then drag and drop it inside the swimlane.

Version-Release number of selected component (if applicable):
BPM Suite 6.1.0

How reproducible:
Always


Steps to Reproduce:
1. Create a simple process with a swimlane;
2. Try to drag and drop a "Simple Merge" Workflow Pattern from menu inside the swimlane.


Actual results:
It will not allow to drop the Simple Merge inside the swimlane (see wp_insideSwimlane.png). 

Expected results:
It should allow to drop the workflow inside the swimlane as it is possible for any other component (i.e. tasks, gateways, etc).

Additional info:
Workaround is drop it outside and then drag it inside the swimlane.

--- Additional comment from Amana on 2015-06-10 08:12:55 EDT ---



--- Additional comment from Amana on 2015-06-10 08:13:09 EDT ---



--- Additional comment from JBoss Product and Program Management on 2015-06-10 08:20:07 EDT ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Amana on 2015-06-10 10:10:22 EDT ---

Comment 4 Kris Verlaenen 2015-06-24 13:47:58 UTC
Alessandro,

The reason I set is as medium is because it was also defined as priority2, with the comment "duplicated as priority 2, so if we can deliver it in Update 2 fine, or it can go to Update 3".  So for that reason it seemed less critical than some others.

Also, we've made further categorization (priority urgent vs high) for priority 1 issues, for those we believe are really blocking a customer (urgent priority) vs can be worked around (high).

If there's a fix available, I obviously don't mind this being backported (regardless priority).

So putting this back to medium priority, but @Tiho: feel free to cherry-pick to 6.2.x if this was fixed.

Comment 5 Tihomir Surdilovic 2015-06-24 14:24:02 UTC
6.2.x fix commit 

https://github.com/droolsjbpm/jbpm-designer/commit/8cc988652

Comment 6 Tihomir Surdilovic 2015-06-24 14:24:43 UTC
please see comment on 1230181 with some details on implementation

Comment 7 Jozef Marko 2015-07-08 13:36:40 UTC
Not fixed properly yet. If user add 'Lane' to canvas, he is not able to drag 'Simple Merge' pattern inside or outside previously added lane. Lane has to loose focus at first. User is then able to drag 'Simple Merge' anywhere. I find this not intuitive.

Expected result:
User can add 'Lane' and 'Simple Merge' in two immediate steps. Without need to click "somewhere" to lane loose focus.

Comment 8 Tihomir Surdilovic 2015-07-08 15:40:44 UTC
I am sorry but this was clearly described in the blocker bz commen (Depends On:	1230181 (edit))

****************

fixed in designer master branch

when you now drag a pattern into an area of a lane or a subprocess the pattern will become part of that container. in addition the container will resize itself if needed to include the added pattern

please not that as before the container should not be selected when dragging a pattern into it. having a node selected when adding a pattern tells the pattern that you wish to substitute the start node of the pattern with the selected node. for this to work properly the container node should not be selected on the canvas when dragging a pattern into it.


*************************

This is just how workflow patterns work. They are intuitive and if there is a node/nodes selected they will try to attach themselves to the selected nodes rather than not looking at them at all. The Lane has to not be selected.....

Comment 9 Jozef Marko 2015-07-09 06:44:02 UTC
Tihomir, thanks for explanation. I apologize for my bad. If it is desired behaviour, everything is all right. You can consider this fix as complete. I will mark BZ as verified when the test will be finalized.

Comment 10 Ivo Bek 2015-07-10 09:10:17 UTC
Verified in BPMS 6.1.2.CR1


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