-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
With adding the possibility to filter by the cancellation status of flow nodes, we also need to make it clear to users that this filter won't be applied correctly to previously imported flow node instances. The documentation should also suggest that to correct this, their only option would be to force a reimport of historic data with the usual caveats of potential data loss in the case of history cleanups
ATs:
- The documentation explains why previously imported data will not have cancellation filters applied correctly
- The documentation suggests a forced reimport as a solution to this
- The documentation also explains how process instance start/end events can never be cancelled even if their backing instance is
This is the controller panel for Smart Panels app
[OPT-4317] Documentation explains possible data inconsistency
| Description |
Original:
With adding the possibility to filter by the cancellation status of flow nodes, we also need to make it clear to users that this filter won't be applied correctly to previously imported flow node instances. The documentation should also suggest that to correct this, their only option would be to force a reimport of historic data with the usual caveats of potential data loss in the case of history cleanups
*ATs:* * The documentation explains why previously imported data will not have cancellation filters applied correctly * The documentation suggests a forced reimport as a solution to this |
New:
With adding the possibility to filter by the cancellation status of flow nodes, we also need to make it clear to users that this filter won't be applied correctly to previously imported flow node instances. The documentation should also suggest that to correct this, their only option would be to force a reimport of historic data with the usual caveats of potential data loss in the case of history cleanups
*ATs:* * The documentation explains why previously imported data will not have cancellation filters applied correctly * The documentation suggests a forced reimport as a solution to this * The documentation also explains how process instance start/end events can never be cancelled even if their backing instance is |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: potential_for_3.2 report_builder | New: current_release potential_for_3.2 report_builder |
| Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
| Status | Original: In Specification [ 10000 ] | New: In Development [ 10312 ] |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Sebastian Bathke [ sebastian.bathke ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | |
| Resolution | New: Done [ 10000 ] | |
| Status | Original: In Review [ 10212 ] | New: Done [ 10010 ] |
| Fix Version/s | New: 3.2.0 [ 16198 ] |