[I] BPMN Editor : Task Deletion Doesn't Remove Attached Boundary Events [incubator-kie-tools]

["rajalakshmys-27 (via GitHub)" <gi...@apache.org>]

rajalakshmys-27 opened a new issue, #3853:
URL: https://github.com/apache/incubator-kie-tools/issues/3853

   ### Summary
   When a task or sub-process is deleted in the BPMN Editor, its attached boundary events are left behind as orphaned elements on the canvas and in the underlying XML.
   
   ### Description
   According to the BPMN 2.0 specification, boundary events are structurally dependent on their host activity via the `attachedToRef` attribute. Deleting the host activity should cascade and remove all associated boundary events. Currently, this cascade deletion does not occur, resulting in invalid BPMN XML with dangling `attachedToRef` references.
   
   ### Steps to Reproduce
   1. Open the BPMN Editor
   2. Create a Task or Sub-Process
   3. Attach one or more Boundary Events to the task
   4. Delete the Task or Sub-Process
   5. Observe the canvas and inspect the underlying XML
   
   ### Expected Behavior
   - All boundary events attached to the deleted task are automatically removed from the canvas
   - The underlying XML contains no orphaned boundary event elements referencing the deleted task
   
   ### Actual Behavior
   - Boundary events remain on the canvas as orphaned elements
   - The XML retains boundary event entries with an unresolvable `attachedToRef` pointing to 
     the deleted task, producing invalid BPMN
   


-- 
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: commits-unsubscribe@kie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org