Sequence flow condition removed after morphing source or target (Task / Gateway)
See original GitHub issueDescribe the Problem
When changing the source or target of a sequence flow that has a condition configured it seems like re-connecting the sequence flow does not retain the condition.
Steps to Reproduce
- open test diagram
- Change target to intermediate message throw event or change source to inclusive gateway
- See that condition on sequence flow
A
is lost
Environment
Camunda Modeler Version: <= v3.3.0-alpha.1
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Morphing into default flow should remove condition - Modeler ...
What should happen if I add a condition to a default flow… the default attribute should be removed in the ExclusiveGateway?. Right?
Read more >Eclipse BPMN2 Modeler User Guide (Version 1.0.1)
Sequence Flow. Morph Activity/Gateway – changes the element's type, depending on whether the selected element is an Activity or Gateway.
Read more >Flow Control | Unreal Engine 4.27 Documentation
Nodes that allow for controlling the flow of execution based on conditions.
Read more >Getting Started - jBPM Documentation
Execution - execute processes, tasks, rules and events on the core runtime engine. Runtime Management - work on assigned task, manage process instances,...
Read more >Getting Started - jBPM Documentation - JBoss.org
Execution - execute processes, tasks, rules and events on the core runtime engine. Runtime Management - work on assigned task, manage process instances,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pinussilvestrus I checked this also, this is fixed with the commit you mentioned.
Seems like this will be fixed by the next release, cf. https://github.com/bpmn-io/bpmn-js/commit/b290078600ae4e45e7c72bd37919732e3f8fcbea