MohammadMu99 opened a new issue, #4016:
URL: https://github.com/apache/incubator-kie-tools/issues/4016

   ## Description
   
   In the new BPMN Editor, the position of a **Sequence Flow label** is 
calculated automatically, and currently the user cannot drag and move the label 
manually.
   
   This becomes a problem when a gateway has multiple outgoing paths.
   
   For example, an **Exclusive Gateway** may have several outgoing Sequence 
Flows such as:
   
   * `Approved`
   * `Rejected`
   * `Manual Review`
   * `Need More Information`
   
   When multiple Sequence Flows leave the same gateway, their labels can appear 
very close to each other or even appear around/inside the gateway area.
   
   This makes it difficult to understand which label belongs to which Sequence 
Flow.
   
   The user should be able to drag each Sequence Flow label and move it closer 
to its corresponding connection.
   
   ## Steps to Reproduce
   
   1. Open the BPMN Editor.
   2. Add an Exclusive Gateway.
   3. Create three or more outgoing Sequence Flows.
   4. Connect each flow to a different BPMN node.
   5. Give each Sequence Flow a name.
   6. Observe the labels around the gateway.
   7. Try to drag one of the labels to another position.
   
   ## Current Behavior
   
   Sequence Flow labels are positioned automatically and cannot be manually 
moved.
   
   When multiple paths leave the same gateway, labels may overlap or appear too 
close together, making it difficult to determine which label belongs to which 
path.
   
   ## Expected Behavior
   
   The user should be able to drag and reposition a Sequence Flow label.
   
   This would allow the user to place each label near its corresponding 
connection and make diagrams with multiple gateway paths easier to understand.
   
   Ideally, the manually selected label position should also be preserved in 
the BPMN DI information so that the label remains in the same position after 
saving and reopening the BPMN file.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to