Details
-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
Description
When we import historic running/completed activity instances, we discard the value of the canceled field. For us to be able to filter and match cancellation states, we need to instead store this property on the nested flow node events that are part of the process instance, as well as part of the camunda activities, which then get correlated to stored event process instances.
ATs:
- Store the cancellation state of running and completed historic activity instance flow nodes as part of process instance
- Store the cancellation state of running/completed activities in the camunda activity event indices
- Use the value of this field when correlating these events into an event process instance DTO