-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.7.0.GA
-
Red Hat Process Automation Manager 7.7.0 (RHPAM)
Openshift (OCP) 3.11
Customer worked with a sample project from Karina Varela related "persisting-custom-process-variables-in-different-db-on-jbpm". They tried to use the request to complete a task without Id field and the map_var_id column doesn't set to null, but it created a second record in the Person table instead of updating the existing one.
In another way, it happens if they use the complete request with Id field but map_var_id field from the mappedvariable table is set to null without creating a second record from the table person
- is related to
-
JBPM-9460 Persisting in mappedvariable table comes null entry in its map_var_id
-
- Closed
-