-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DMN - Annotation flow disappears after renaming decision in table editor #2052
Comments
Related to #1874. |
The issue is that when replacing the decision the association's parent from the model's perspective is changed to the text annotation. In the case of information requirements and such the parent is indeed the target element. Not in this case since the association is an artifact. This issue was fixed before (bpmn-io/dmn-js@90a7952#diff-a42b136569b62592b63126d0bfe523df9cfd77884dfd10741252ceead428e185R265) but then broken again (bpmn-io/dmn-js@853eea1). So we're fixing it again. ♻️ |
Fixed upstream (again) via bpmn-io/dmn-js#620. |
Describe the Bug
annotation-2021-01-06_14.48.59.mp4
Here are the logs after saving and reopening the diagram:
Steps to Reproduce
-Create Decision
-Name it
-Add Annotation
-Morph into Decision Table
-Rename inside of Decision Table mode
-Go back to DRD
-See that the Annotation is unlinked
Expected Behavior
The annotation stays linked to the decision element
Environment
Related to #1874
The text was updated successfully, but these errors were encountered: