-
Bug Report
-
Resolution: Done
-
L3 - Default
-
3.0.0
-
None
Context:
More than one processInstanceStart & End event don't work as the activityInstanceId is not unique across instances:
The same applies for flow nodes that get split into multiple events in Optimize. At the moment, they are given activity Ids comprised of the instanceId + the predefined suffix. They should instead be using the flow node Id rather than that of the instance. This will be a problem for any model that has more than one splittable node, because the start events of all split nodes within an instance will have the same activity instance IDs, as will all the end events of the split nodes.
Given:
I map processInstanceStart/End events into an event based process and publish it
When:
there are more than one processInstanceStart/End event in one event batch
Then:
only the last of these events wins and is assigned to the correct process instance, other process instances lack the mapped activity instances
Expected:
every of these events per process instance should get published as an activityInstance
Given:
I map multiple split Camunda events into an event based process and publish it
When:
there are more than one mapped Camunda events that get split imported
Then:
only the last of these events wins and is assigned to the correct process instance, other process instances lack the mapped activity instances
Expected:
every of these events per process instance should get published as an activityInstance
Hint:
We should consider documenting these as known issues
