Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
Description
Context:
The fetchAndLock helper takes a processInstanceId which suggests that we only lock those tasks associated with that specific instance, when in fact we lock everything but only return the tasks of that instance. This unexpected side effect makes it hard to eg create incidents for multiple different process instances and is generally a bit confusing.
We can refactor this helper as well as the related incident helpers to take a businessKey instead and then only lock those tasks related to the given business key - the methods for this already exist, we just need to refactor the usages.
See also: https://github.com/camunda/camunda-optimize/pull/3639
AT:
- Refactor fetchAndLock and incident helpers to always take a businesskey