Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
for /task/claim /task/complete, /message and process-definition/start, variables are submitted in a key-value map like
{ "aKey" : "aValue", "anotherKey" : "anotherValue"}This should be changed to dedicated variable objects:
{ "aKey" :
, "anotherKey" : {"value" : "anotherValue"}}
Existing webapps (tasklist) and docs have to be updated accordingly.
When this gets released, it has to be explicitly stated as a breaking change!
Methods that use variables and thus have to be checked/changed:
Process Definition -> Start Process Instance
Process Instance -> Get Single Process Variable
Process Instance -> Put Single Process Variable
Process Instance -> Get Process Variables
Process Instance -> Update/Delete Process Variables
Execution -> Get Local Execution Variable
Execution -> Put Local Execution Variable
Execution -> Get Local Execution Variables
Execution -> Update/Delete Local Execution Variables
Execution -> Trigger Execution
Execution -> Trigger Message Subscription
Task -> Complete Task
Task -> Resolve Task
Message -> Deliver a Message
The following methods take variables as arguments for comparison like
{"name": "aKey", "operator": "eq", "value": "aValue"} but these are not variables but rather comparison terms, so the following methods are not touched by this refactoring:
Process Instance -> Get Instances (POST) (+ Count)
Execution -> Get Executions (POST) (+ Count)
Task -> Get Tasks (POST) (+ Count)