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.

Currently, the existing method of PathResolver considers only flowNodes/shapes in the input parameters and returns only the visited flows/edges.

Describe the solution you'd like

Provide a new method dedicated to the management of a single case instance (create a new CasePathResolver class) that returns the "full path" including:

• pass ids of elements that are considered as "completed". For more information, see [FEAT] CasePathResolver: distinguish completed and pending elements passed as input parameters to infer more flows/edges in the path #16
• the model elements objects (as BpmnSemantic) corresponding to the ids passed as inputs that exist in the model
• considering both flowNodes/shapes and flows/edges as input to compute the path
• computed list of flows/edges and flowNodes/shapes inferred from the inputs

This will require to explicitly split the data returned by the method to identify the input (objects retrieved from the provided ids) from the computed elements. See also #24.

Additional context

We could use it in the "predictions" demo. We are not using PathResolver in the demo for now as it is not considering edge in the input (process-analytics/bpmn-visualization-examples#520). See process-analytics/bpmn-visualization-examples#573.
See also process-analytics/bonita-day-demo-2023#122