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

[FEAT] CasePathResolver: detect boundary events #180

Open
tbouffard opened this issue Dec 3, 2023 · 0 comments
Open

[FEAT] CasePathResolver: detect boundary events #180

tbouffard opened this issue Dec 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@tbouffard
Copy link
Member

tbouffard commented Dec 3, 2023

DISCLAIMER: this issue describes path computation for a single instance/case only. So the implementation will go to the CasePathResolver class as it differs from PathResolver which is a generic implementation that both deals with single instance or all instances of a process.

Is your feature request related to a problem? Please describe.

Some systems execute boundary events but don't provide information about their actual execution.
In this case, they could be deduced.

Describe the solution you'd like

Be able to infer the boundary events in the path in "simple" cases i.e. when the list of provided reference elements contains an element right after the event. This is something which is similar to #12.
Such detection should be enabled by passing an option and should be disabled by default. Possible names of for the new option (non exhaustive list, feel free to add new proposals. To be discussed and the final decision should be explicitly mentioned here along with all proposals considered, in particular the usage of singular or plural as part of #23):

  • inferBoundaryEvents
@tbouffard tbouffard added the enhancement New feature or request label Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant