Issue seems related to
ACTIVITI-355 where the historic process instance query now supports “includeProcessVariables”, but the normal process instance query API (/api/enterprise/process-instances/query) does not, whereas it does support the parameter in the corresponding engine API call (/api/query/process-instances). The customer has no way to display a list of process variables when running Enterprise REST call /api/enterprise/process-instances/query
Steps to reproduce
- Login to activiti-admin, select the Instances tab and locate a running process instance, which contains at least 1 process instance variable. Copy the process instance id. e.g. 2506. NOTE: If you can´t locate a running instance with a process variable, you would have to start any process and could add a process variable via activiti-admin
- Open POSTMAN (or any RESTful client) and fire below calls:
- Enterprise API call get list of process-instances -> /api/enterprise/process-instances/query
(a) Without specifying the “includeProcessVariables” parameter in request body, empty variables bracket will be returned.
(b) If attempting to specify “includeProcessVariables” parameter in the request body, it results in an error "JSON parse error: Unrecognized field \"includeProcessVariables\""
c) however, running the equivalent Engine API call allows querying for process-instances with the "includeProcessVariables" parameter in the request body and returns instances including their variables.
Variables are listed in the response similar to a historic query 'api/enterprise/historic-process-instances/query' using the "includeProcessVariables" parameter set to "true" in the query request body.
Process Variables are never listed in the 'api/enterprise/process-instances/query' call response and the "includeProcessVariables" parameter is an unrecognized field.