As of today it is not straight forward to replace a typed event, i.e. a configured message start event, with the respective intermediate catch event partner. This can be needed as I refactor a process, i.e. the "trigger" is moved from in the flow ("intermediate catch") to an event sub-process ("start").
For example, given a message start in the above capture I'd like to see all of the following variants present:
What I have to do is to do the replace operation in the XML, or (1) create a new event, (2) re-wire all relevant connections, (3) copy manually over all implementation details. This violates our do the hard work and make it simple principle.
Proposed solution
[ ] For any typed event ("timer", "message", ...) the replace menu offers the ability to change to the respective alternative form ("start", "intermediate throw", "intermediate catch", "end")
[ ] Relevant implementation details are preserved (i.e. wired message), where applicable
Problem you would like to solve
As of today it is not straight forward to replace a typed event, i.e. a configured message start event, with the respective intermediate catch event partner. This can be needed as I refactor a process, i.e. the "trigger" is moved from in the flow ("intermediate catch") to an event sub-process ("start").
For example, given a message start in the above capture I'd like to see all of the following variants present:
What I have to do is to do the replace operation in the XML, or (1) create a new event, (2) re-wire all relevant connections, (3) copy manually over all implementation details. This violates our do the hard work and make it simple principle.
Proposed solution
Alternatives considered
None.
Additional context
Reported by @falko here.