Open korthout opened 1 year ago
Thanks for opening this issue.
Documentation describing this limitation
I'm not sure this is an actual limitation, or just a "stay sane" fact, cf. sequence flow handling.
Moving to 8.2, so we have this as a radar as a potential follow-up improvement.
I'm not sure this is an actual limitation, or just a "stay sane" fact, cf. sequence flow handling.
It is part of the spec under Link Event Definition
in 10.5.5 Event Definitions
The use of Link Events is limited to a single Process level (i.e., they cannot link a parent Process with a Sub-Process).
@korthout Exactly. I'd just not phrase it as a limitation, but as "this is how it is defined in the BPMN spec" :slightly_smiling_face:.
Re-visiting for 8.4 release.
We're going to add a bpmnlint
rule to validate this (links are only allowed within the same scope).
A link-event
validating the basics of BPMN soonish via https://github.com/bpmn-io/bpmnlint/pull/128.
@philippfromme Removed from current milestone. Let's decide if this shall be eligible for the next one.
What should we do?
Add a linting rule in
bpmnlint
that disallows linking events between two different scopes.link-event
rule frombpmnlint-plugin-camunda-compat
link-event
tobpmnlint
link-event
rule to disallow linking across scopesExamples
## Allowed examples ### Within the root scope ### Within the same subprocess scope ## Not allowed examples ### From root scope to subprocess scope ### Between two different subprocess scopes ### From subprocess scope to root scopeWhy should we do it?
Link events are about to be released with 8.2.
Documentation describing this limitation: https://github.com/camunda/camunda-platform-docs/pull/1813/files#diff-34469b07893c827e8a343835e1da741cf6fdf9f80dc51b24332b7c94330b2717R30-R37
Related bug https://github.com/camunda/zeebe/issues/10854
Related to https://github.com/camunda/bpmnlint-plugin-camunda-compat/issues/136, https://github.com/camunda/bpmnlint-plugin-camunda-compat/issues/129