Move elements to another package by going through the diagram?

[miksko]

Let's say I've created an activity diagram in a use case and then realize that an alternate flow should be moved to another use case. I can of course cut and paste the affected elements in the activity diagram, but the the elements will remain under the first use case; it's only the links that I cut and paste. Is there some way to perform a "deep move" in the same way you may do a "deep copy"?

[Sparx Systems Malaysia]

The distinction here is between moving an element’s appearance in a diagram and changing its owner in the model. Cutting and pasting between diagrams does the former.

For the ownership change, relocate the underlying elements in the Browser to the intended destination. Official documentation indicate that Browser moves to preserve existing relationships and diagram usage.

For your example, first check whether the flow’s nodes belong directly to the Use Case or to an Activity beneath it; that determines what should be moved. You can then arrange their appearances on the destination diagram.

Could you share the relevant Browser hierarchy? That would help identify the correct scope of the move without unintentionally moving shared nodes.