Support different transactions using the same physical transaction having different behaviours

[Gaudeval]

Two user transactions may have the same path (physical transaction) but different behaviours, e.g. with regards to services they interfere with. We can specify the interference, but it does not seem to be taken into account. Either as user transactions are mapped to the same physical one.

[kevin-delmas]

Strange, it seems to me that PML Analyzer should consider them even if the underlying transaction is the same.
@Gaudeval could you provide me a minimal example of the problem? If I can reproduce the problem we will classify the issue as a bug.

[kevin-delmas]

This problem seems to be linked to the ability to model capacity.
See Issue #5