Details
-
Bug
-
Resolution: Done
-
Minor
-
7.58.0.Final
-
None
-
False
-
False
-
NEW
-
NEW
-
undefined
-
In attachment a test process data-assignment-mvel.zip
, to reproduce the problem:1. Start process test
2. Fill out all the fields with value "A"
3. Check the process variables value through the Business Central
4. You will notice that the variable another has the value "A" where as the variable request.priority is not updated. In fact, the table VARIABLEINSTANCELOG does not contains the update.On the other hand, checking the actual value of the variable via REST API shows the expected result:
curl -X GET "http://localhost:8080/kie-server/services/rest/server/containers/variable-out_1.0.0-SNAPSHOT/processes/instances/2/variable/request" -H "accept: application/json"
In attachment a test process data-assignment-mvel.zip , to reproduce the problem: 1. Start process test 2. Fill out all the fields with value "A" 3. Check the process variables value through the Business Central 4. You will notice that the variable another has the value "A" where as the variable request.priority is not updated. In fact, the table VARIABLEINSTANCELOG does not contains the update. On the other hand, checking the actual value of the variable via REST API shows the expected result: curl -X GET "http://localhost:8080/kie-server/services/rest/server/containers/variable-out_1.0.0-SNAPSHOT/processes/instances/2/variable/request" -H "accept: application/json"
Description
When a variable is updated by a data association in a User Task using a MVEL expression, the variable log is not aligned with the current variable value.
Example:
Considering a process: start -> Task 1 -> Task 2 -> end
- request = { "priority" : "", "value" : false }
- Task 1 is performed the assignment: "aaa" -> #{request.priority}
- Inspecting the variable variables from process instance details the request variable remains unchanged.
- Nevertheless, the actual variable value is correctly updated
