Morphing a call activity
to an expanded sub-process
should add a start event
#1631
Labels
call activity
to an expanded sub-process
should add a start event
#1631
Describe the Bug
When morphing a call activity to a subprocess, it creates a tiny subprocess which looks just like a task, this is confusing UX wise and a first step to fix this would be for the morphing behavior to match that of tasks and include a start event.
Steps to Reproduce
Expected Behavior
Expanded sub process should be created with an event like it is done when morphing from a task:
The text was updated successfully, but these errors were encountered: