Variable instructions of multiple activations sometimes ignored in process instance modification #10317
Labels
area/reliability
Marks an issue as related to improving the reliability of our software (i.e. it behaves as expected)
kind/bug
Categorizes an issue or PR as a bug
severity/high
Marks a bug as having a noticeable impact on the user with no known workaround
version:8.1.0
Marks an issue as being completely or in parts released in 8.1.0
Describe the bug
I've discovered a bug related to
A modification with variable instructions for multiple activations can lead to buffer errors, or some of the variable instructions are ignored.
For example, when writing
foo: 1
in the first activation andbar: 2
in the second one, then onlybar
gets created as a process variable.However, when
bar
's value is changed to a different type (e.g."now it's a string"
), then it leads to buffer errors, and the modification command is completely rejected altogether.To Reproduce
Expected behavior
Variables are created for each of the provided variable instructions.
Log/Stacktrace
Full Stacktrace
Environment:
main
)The text was updated successfully, but these errors were encountered: