Bug 1232975
| Summary: | Process elements divided in different swimlanes changes its connectors positions everytime we move one of the swimlanes | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | William Antônio <wsiqueir> | ||||||
| Component: | jBPM Designer | Assignee: | Tihomir Surdilovic <tsurdilo> | ||||||
| Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1.0 | CC: | alazarot, kverlaen, wsiqueir | ||||||
| Target Milestone: | DR1 | ||||||||
| Target Release: | 6.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1233980 (view as bug list) | Environment: | |||||||
| Last Closed: | 2020-03-27 20:09:07 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1233980 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1040194 [details]
Position changed after we move the swimlane
Designer has a default enabled connector layouting routine. This helps with exactly the types of scenarios when you have a lot of connections going from one container object to another. I guess the customer here does not like this function so I have disabled it. We could add an optional on/off button in the navbar but I am not sure what the default should be as maybe some other users might actually like the connection layouting to be enabled for them. Let me know what you think. For now what I have done is simply disable connection layouting which will keep any/all connections (and their bendpoints) exactly as the user defined them at all times. Tiho, the default should be it "on" for backward compatibility. If anyone dislike it, so it can be disabled manually. It is fine to turn it off for now completely. We will add an option for this via system props and navigation bar at a later time. master commit https://github.com/droolsjbpm/jbpm-designer/commit/1ae506da52afd38f38cf550efc0ed6466db57d80 Verified on 6.2.0.ER3. Connectors are not rerouted automatically now. But please see the new linked bugzilla, where I filed problem with docker on edges. |
Created attachment 1040193 [details] Connectors pos before moving swimlane Description of problem: If we have a gateway in Swimlane1 and it is connected to tasks on Swimlane2, all the time we chance Swimlane1 position or swimlane 2 position, the connectors position changes, making hard to check where its connection ends. (which node) Version-Release number of selected component (if applicable): n/a How reproducible: Always Steps to Reproduce: 1. Create a process in a new project in BPM Suite 6.1 2. add a start node that is connected to a task which is connect to a gateway 3. Connect the gateway to tasks in another gateways and adjust the connector position (direction) Actual results: Every time we move the swimlane, it changes the connector position back to a default position Expected results: Do no change the position. Additional info: See attachments that demonstrate this issue.