Escalation boundary event is reported as unsupported for ad-hoc subprocess

[barmac]

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

1. Create an ad-hoc subprocess
2. Attach an escalation boundary event to it
3. now this happens

Expected behavior

Report for tasks only. Also adjust the message.

Environment

• OS: [e.g. MacOS 10.2, Windows 10]
• Camunda Modeler Version: [e.g. 2.0.0]
• Execution Platform: [e.g. Camunda 7, Camunda 8]
• Installed plug-ins: [...]

Additional context

Reported via slack: https://camunda.slack.com/archives/C0693F1NFK5/p1740574966727099

[philippfromme]

Likely a result of camunda/bpmnlint-plugin-camunda-compat#110.

[nikku]

Likely a result of camunda/bpmnlint-plugin-camunda-compat#110.

Which make it an easy thing to fix, thanks for the hint @philippfromme 🧁

[Buckwich]

The current implementation is using exclusion (ie, for CallActivity, SubProcess, and now AdHocSubProcess the rule is not triggered). I don't think there are others we need to exclude now, just something to be aware of if we add more activities.

@barmac what do you mean with Also adjust the message.? In the case of a task it would already show this error message: Element of type <bpmn:BoundaryEvent> with event definition of type <bpmn:EscalationEventDefinition> is not allowed to be attached to element of type <bpmn:Task>

[philippfromme]

@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. bpmnlint-plugin-camunda-compat can be used in a CLI which would lack the context of the modeler's UI. Therefore the default error messages are very technical and don't refer to entries in the properties panel and such. The usual workflow is

1. Create the rule in bpmnlint-plugin-camunda-compat
2. Adjust the error message and point to the right entry in the properties panel in @camunda/linting

For 1. you've already created the pull request so once that's integrated into @camunda/linting we can follow up with a pull request there.

[Buckwich]

@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.

[barmac]

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".

[Buckwich]

Done in camunda/linting#137. I used An <Escalation Boundary Event> is not allowed on a <User Task> as a message