-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
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
This is the controller panel for Smart Panels app
[OPT-4313] Store historic activity instance cancellation state
| Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
| Labels | Original: potential_for_3.2 report_builder | New: current_release potential_for_3.2 report_builder |
| Status | Original: In Specification [ 10000 ] | New: In Development [ 10312 ] |
| Summary | Original: Store historic activity instance cancellation state as part of process instance flow node events | New: Store historic activity instance cancellation state |
| Description |
Original:
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.
*ATs:* * Store the cancellation state of running and completed historic activity instance flow nodes |
New:
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 |
| Mentioned Roles |
| Mentioned Groups |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Johannes [ johannes.heinemann ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Status | Original: In Review [ 10212 ] | New: In Specification [ 10000 ] |
| Assignee | Original: Johannes [ johannes.heinemann ] | New: Joshua Windels [ joshua.windels ] |