When we specify a fromFlowNodeId parameter, we read all instance keys for that flow node definition and do a modification for each
When we specify a fromFlowNodeInstanceKey parameter, we only modify that one flow node
If the request has values for both fromFlowNodeId and fromFlowNodeInstanceKey, then fromFlowNodeId behaviour takes precedence. It feels to me like it should be the opposite: if you specify fromFlowNodeInstanceKey you will only modify that one even if you also specify fromFlowNodeId
Current behavior
If the request has values for both fromFlowNodeId and fromFlowNodeInstanceKey, then fromFlowNodeId behaviour takes precedence.
Expected behavior
if you specify fromFlowNodeInstanceKey you will only modify that one even if you also specify fromFlowNodeId
Additional context
Acceptance Criteria
Definition of Ready - Checklist
[ ] The bug has been reproduced by the assignee in the environment compatible with the provided one; otherwise, the issue is closed with a comment
[ ] The issue has a meaningful title, description, and testable acceptance criteria
[ ] The issue has been labeled with an appropriate Bug-area label
[ ] Necessary screenshots, screen recordings, or files are attached to the bug report
For UI changes required to solve the bug:
[ ] Design input has been collected by the assignee
Implementation
:mag: Root Cause Analysis
:thought_balloon: Proposed Solution
:point_right: Handover Dev to QA
Changed components:
Side effects on other components:
Handy resources:
BPMN/DMN models, plugins, scripts, REST API endpoints + example payload, etc :
Example projects:
Commands/Steps needed to test; Versions to validate:
Docker file / HELM chart : in case that it needed to be tested via docker share the version contain the fixed along with version of other services .
Release version ( in which version this fixed/feature will be released):
Describe the bug
fromFlowNodeId
parameter, we read all instance keys for that flow node definition and do a modification for eachfromFlowNodeInstanceKey
parameter, we only modify that one flow nodefromFlowNodeId
andfromFlowNodeInstanceKey
, thenfromFlowNodeId
behaviour takes precedence. It feels to me like it should be the opposite: if you specifyfromFlowNodeInstanceKey
you will only modify that one even if you also specifyfromFlowNodeId
Current behavior
fromFlowNodeId
andfromFlowNodeInstanceKey
, thenfromFlowNodeId
behaviour takes precedence.Expected behavior
fromFlowNodeInstanceKey
you will only modify that one even if you also specifyfromFlowNodeId
Additional context
Acceptance Criteria
Definition of Ready - Checklist
Bug-area
labelFor UI changes required to solve the bug:
Implementation
:mag: Root Cause Analysis
:thought_balloon: Proposed Solution
:point_right: Handover Dev to QA
:green_book: Link to the test case