Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
3
-
Not defined
Description
Brief summary of the bug. What is it ? Where is it ?
When an external variable batch contains two variables with the same ID for the same instance, we store the first one on the json array as the variable value. While the desired behaviour might not be obvious, I would possibly say that we should take the later value as the "correct" value in this scenario. Whatever the decision, we should probablu document this usage as the behaviour is non-obvious to users
Steps to reproduce:
- Ingest external variable batch containing two of the same variable IDs/instance IDs but with different values
- Observe that the first variable in the batch list is that persisted to the process instance in Optimize
Actual result :
The first variable in the batch is the saved result
Expected result:
Probably that the last variable in the batch list is that persisted to the process instance in Optimize