-
Sub-task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Context:
Currently, identity and flownode duration view level filters cannot be properly applied to incident reports and incident filterse cannot be applied to flownode/usertask reports due to the nature of our data structure where flownode and incident data are sibling nested documents within the process instance index. One way to resolve this limitation is to move incident data into the flownode data.
However, we first need to evaluate if incidents can always be reliably associated with a specific flownode.
This is the controller panel for Smart Panels app
[OPT-5131] Spike: Investigate moving incident data to flownode data
| Description |
Original:
*Context:*
Currently, identity and flownode duration view level filters cannot be properly applid to incident reports due to the nature of our data structure where flownode and incident data are sibling nested documents within the process instance index. One way to resolve this limitation is to move incident data into the flownode data. However, we first need to evaluate if incidents can always be reliably associated with a specific flownode. |
New:
*Context:*
Currently, identity and flownode duration view level filters cannot be properly applied to incident reports and incident filterse cannot be applied to flownode/usertask reports due to the nature of our data structure where flownode and incident data are sibling nested documents within the process instance index. One way to resolve this limitation is to move incident data into the flownode data. However, we first need to evaluate if incidents can always be reliably associated with a specific flownode. |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: blog current_release potential_for_3.5 potential_for_next_quarter | New: blog next_release potential_for_3.5 potential_for_next_quarter |
| Labels | Original: blog next_release potential_for_3.5 potential_for_next_quarter | New: blog current_release next_release potential_for_3.5 potential_for_next_quarter |
| Labels | Original: blog current_release next_release potential_for_3.5 potential_for_next_quarter | New: blog current_release potential_for_3.5 potential_for_next_quarter |