-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
Not defined
Context:
With OPT-5197 the report base query took multiple definitions into account when filtering process instance data.
FlowNode & UserTask reports however don't consider the unity of all model elements from all definitions in case of group/distributeBy flowNode,userTask or identity but stick to the model elements of the first definition, these views are to be adjusted to properly support multi definitions.
AT:
- FlowNode & UserTask (ModelElement) Views support the unity of all flow nodes/userTasks across all included definitions