-
Notifications
You must be signed in to change notification settings - Fork 2
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
Disallow Condition If Sequence Flow Is Not Exclusive or Inclusive Gateway #82
Comments
The rule makes sense, thanks for suggesting it |
This would be "modeling guidance" then. With this plug-in we strictly validated compatibility for execution. |
Related issue that we do not capture yet (in terms of run-time compatibility): Conditions must not be empty:
|
Closed via #97. |
How did you end up with an empty expression? The |
Change a flow into a conditional flow. |
Ah! Yeah, that part is a bit confusing. So any sequence flow can have a condition, but only when the source is an activity it must also be rendered as a conditional sequence flow. I guess we need the empty expression to be able to determine that the sequence flow is conditional and to render it as such. |
The rule should detect the following modeling patterns
Incorrect: Camunda 8.1 will reject this:
converted-c8-conditional-flow.bpmn.txt
Correct: Camunda 8.1 will accept this:
converted-c8-inclusive-gateway.bpmn.txt
In addition, we consider modeling implicit gateways a bad practice, so even if zeebe will support conditional flows, this rule would still apply as warning or info.
How does the rule improve the BPMN diagram?
This rule will prevent users from creating undeployable diagrams.
Rule Details
error
What alternatives did you consider?
The text was updated successfully, but these errors were encountered: