You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Be able to infer the start/end event in the path in "simple" cases i.e. when the list of provided reference elements contains an element right before/after the event.
Such detection should be enabled by passing an option and should be disabled by default.
More complex use cases will be handled through a dedicated issue.
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an exclusive merge gateway
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an parallel merge gateway
They should be both detected as part of the path
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an inclusive/event-based merge gateway
TODO choose the rule
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an exclusive split gateway
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an parallel split gateway
They should be both detected as part of the path
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an inclusive/event-based split gateway
TODO choose the rule
Several start/end events, only in "lonely edge" branches
This is not possible to detect the effective events. They can only be considered as candidates (#24).
tbouffard
changed the title
[FEAT] PathResolver: detect start/end event in "lonely edge" branch
[FEAT] CasePathResolver: detect start/end event in "lonely edge" branch
Oct 9, 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 fromPathResolver
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.
Improve #12 and handle special cases
Describe the solution you'd like
Be able to infer the start/end event in the path in "simple" cases i.e. when the list of provided reference elements contains an element right before/after the event.
Such detection should be enabled by passing an option and should be disabled by default.
More complex use cases will be handled through a dedicated issue.
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an exclusive merge gateway
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an parallel merge gateway
They should be both detected as part of the path
Several start events, some with BPMN elements in the same branch, other in "lonely edge" branch, going to an inclusive/event-based merge gateway
TODO choose the rule
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an exclusive split gateway
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an parallel split gateway
They should be both detected as part of the path
Several end events, some with BPMN elements in the same branch, other in "lonely edge" branch, coming from an inclusive/event-based split gateway
TODO choose the rule
Several start/end events, only in "lonely edge" branches
This is not possible to detect the effective events. They can only be considered as candidates (#24).
The text was updated successfully, but these errors were encountered: