Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.0.0, 7.2.0, 7.1.0
-
None
Description
WARNING: this issue is BAAAAAD
Event subprocesses are currently not written to History.
Reason: it is currently impossible to remember the activity instance ID for the event subprocess activitiy itself. Since the event subprocess is not a scope, we do not have a dedicated execution created for executing the event subprocess which makes it impossible to store the activity instance id.
As a result we are able to fore an historic activity instance START event but not an historic activity instance END event.
We disabled history for event subprocesses in the parser for now.
See commented testcaes in
org.camunda.bpm.engine.test.bpmn.event.message.MessageEventSubprocessTest