-
Notifications
You must be signed in to change notification settings - Fork 497
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
Escalation boundary event is reported as unsupported for ad-hoc subprocess #4859
Comments
Likely a result of camunda/bpmnlint-plugin-camunda-compat#110. |
Which make it an easy thing to fix, thanks for the hint @philippfromme 🧁 |
The current implementation is using exclusion (ie, for @barmac what do you mean with |
@Buckwich There is a second layer to linting which adjusts the error messages based on the assumption that they're going to be shown in the Problems tab.
For 1. you've already created the pull request so once that's integrated into |
@philippfromme @barmac I have released the new version of bpmnlint-plugin-camunda-compat and included it in camunda/linting#137. But I am still unsure what to do about the message as I didn't change the rule itself just reduced its occurence. |
In camunda/linting project, there's a utility which adjusts the generated error messages to be human-friendly (example: camunda/linting@23cc45a). The error message from the top comment is overly verbose, and hard to understand at the same time. This could be adjusted to a short, user-friendly alternative, e.g. "An attached to a is not supported in Camunda 8.7". |
Describe the bug
We report incorrectly escalation boundary event as unsupported for ad-hoc subprocess. This is not true as the element can be attached to an ad-hoc subprocess. Only tasks cannot have escalation boundary events.
Steps to reproduce
Expected behavior
Report for tasks only. Also adjust the message.
Environment
Additional context
Reported via slack: https://camunda.slack.com/archives/C0693F1NFK5/p1740574966727099
The text was updated successfully, but these errors were encountered: