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.
• this issue only deals when the following element of the exclusive gateway linked with a lonely edge is an merge exclusive gateway

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

Sometimes, there is an exclusive gateway with a branch without element (ege only).
When detecting path of

• a single instance, only detect the "lonely edge" as "activated" when not passing through the other branches.
• several instance, the "lonely edge" can be activated if never passing through the other branches. Otherwise, we can only assume that this edge is a candidate ([FEAT] CasePathResolver: categorize the elements returned in the inferred path #24). We would need a frequency information to be able to decide.

Note: this use case doesn't apply to parallel gateways (we don't want to support non conformant model)

flowchart LR
    task --> gatewaySplit{X}
    gatewaySplit --> task1 --> gatewayMerge{X}
    gatewaySplit --> task2 --> gatewayMerge
    gatewaySplit --> gatewayMerge 
    gatewayMerge --> anotherTask

Describe the solution you'd like

Handle the case when it is obvious.

Questions

• Do we introduce an option as part of [FEAT] CasePathResolver: let provide options to tune the path computation #23 to enable the processing of such an use case?