Skip to content
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

Detect conflicting interrupting event subscriptions per scope #98

Open
nikku opened this issue Feb 28, 2023 · 0 comments
Open

Detect conflicting interrupting event subscriptions per scope #98

nikku opened this issue Feb 28, 2023 · 0 comments
Labels
backlog Queued in backlog rules Concerning existing or missing rules

Comments

@nikku
Copy link
Member

nikku commented Feb 28, 2023

The rule should detect the following modeling patterns

event-scopes

How does the rule improve the BPMN diagram?

Interrupting events fire immediately, hence there can only be one interrupting event per scope that does something meaningful. If you model two conflicting interrupting events, then you are very likely to run into undefined behavior (execution wise) or make an error.

Rule Details

  • Name: event-scopes
  • Default notification level: warn

What alternatives did you consider?

None.

@nikku nikku added the rules Concerning existing or missing rules label Feb 28, 2023
@marstamm marstamm added the backlog Queued in backlog label Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog rules Concerning existing or missing rules
Projects
None yet
Development

No branches or pull requests

2 participants