Description
Currently, the Jmix BPM Runtime Modeler does not support copying BPMN elements from one .bpmn file and pasting them into a different .bpmn file. This is a significant limitation in projects that follow a modular process architecture.
Use Case
In enterprise Jmix applications, business processes are often split across multiple .bpmn files, and many structural patterns (e.g., approval chains, error-handling subprocesses, notification tasks) are reused across them. Without cross-file paste support, developers must:
Manually recreate identical process fragments in each file, or
Switch to the raw XML editor and hand-copy BPMN element definitions — a fragile and error-prone approach.
Requested Action
Add support for cross-file copy/paste within the Jmix BPM Runtime Modeler:
- Allow copying one or more elements (tasks, subprocesses, gateways, sequence flows, etc.) from a .bpmn diagram.
- Allow pasting those elements into a different .bpmn diagram open in the same IDE session.
- Preserve element properties, types, and — where unambiguous — their internal connections.
This is consistent with how the modeler already handles single-file copy/paste at the bpmn.io level, and the implementation may be achievable by persisting clipboard state to a shared in-memory or session-scoped buffer accessible across editor tabs.
Description
Currently, the Jmix BPM Runtime Modeler does not support copying BPMN elements from one .bpmn file and pasting them into a different .bpmn file. This is a significant limitation in projects that follow a modular process architecture.
Use Case
In enterprise Jmix applications, business processes are often split across multiple .bpmn files, and many structural patterns (e.g., approval chains, error-handling subprocesses, notification tasks) are reused across them. Without cross-file paste support, developers must:
Manually recreate identical process fragments in each file, or
Switch to the raw XML editor and hand-copy BPMN element definitions — a fragile and error-prone approach.
Requested Action
Add support for cross-file copy/paste within the Jmix BPM Runtime Modeler:
This is consistent with how the modeler already handles single-file copy/paste at the bpmn.io level, and the implementation may be achievable by persisting clipboard state to a shared in-memory or session-scoped buffer accessible across editor tabs.