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):
DISCLAIMER: this issue describes path computation for a single instance/case only. So the implementation will go to the
CasePathResolverclass as it differs fromPathResolverwhich 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):