You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It is difficult to determine the cycle in a DMN from the current message in the Camunda modeler. My only way to figure this out is to run the parser locally and set a breakpoint.
Left(Failure(
"Invalid DMN model: Cyclic dependencies between decisions detected."))
Describe the solution you'd like
I'd like to see the ids of the impacting decisions added to the failure message.
This sounds like a reasonable improvement. But maybe not the most important one. I assume that the cyclic dependency is obvious when looking at the DRD. But feel free to share an example to demonstrate the issue.
Is your feature request related to a problem? Please describe.
It is difficult to determine the cycle in a DMN from the current message in the Camunda modeler. My only way to figure this out is to run the parser locally and set a breakpoint.
Describe the solution you'd like
I'd like to see the ids of the impacting decisions added to the failure message.
Related issues
#207
The text was updated successfully, but these errors were encountered: