Expose variable incarnations per origin

[barinali]

Problem you would like to solve

We are currently merging the variable values/info and types with all the possible incarnations. It is more obscure than it helps the user when it comes to the variables written by many places.

Proposed solution

Instead of merging value/info and types from all the incarnations, we would like to make the variable resolution more contextual. Taking the screenshot from the problem statement into account;

Instead of showing a variable's merged value/info and types, we should show its current incarnation at the point of selection.

For the variable expressionsOverExpressions3, we currently have 4 merged value/info. Instead of showing all four at once, we should show what's "current" value/info in the current selection/context. Some produced screenshots;

The same goes for the variable expressionsOverExpressions4.

Exposing incarnations of variables instead of their merged states would enable users to have a better understanding of their variables at a point, navigate via elements writing to the same variable and observe different incarnations at that point of selection.

Alternatives considered

Leaving the variables resolution as-is.

Additional context

The diagram used in the screenshot is added here; many_elements_writing_to_same_variables.bpmn.txt. It's added as a plain text file as .bpmn extension is not supported by GitHub.

[barmac]

How would it work in a non-linear flow?

[barinali]

@barmac multiple incarnations at a time can be valid due to the essence of BPMN and we can visualize them accordingly if it's the case. Right now, we cannot distinguish and thus, cannot contextually visualize the incarnations.

[barmac]

In general, I agree that showing plenty of expressions is not very helpful.

[nikku]

Moving to ready to discuss whether this shall be a post-release investment.