L3 - Default When a user tries to modify a process instance by drag-and-dropping a token to the next task, the following request payload is created:
{
"id": "55f0003f-3911-11e9-a278-aa340f2b1d5b",
"skipCustomListeners": true,
"skipIoMappings": true,
"instructions": [
{
"type": "startBeforeActivity",
"activityId": "Task_0bcexgz",
"variables": {}
},
{
"type": "cancel",
"activityInstanceId": "Task_1rvjnra:55f00042-3911-11e9-a278-aa340f2b1d5b"
}
]
}
According to the Cancellation Propagation principle, this may result in a called process instance (f.ex. subprocess or call activity) cancellation. In consequence, the call activity of the calling process instance gets cancelled as well.
While the user can see the future state of his current process definition diagram in cockpit (orange +1 and -1 tokens), the potential change in the parent processes is not visually indicated anywhere.
This might confuse some users (see linked support cases for examples), as when a user drags a token to a new place in the diagram, the intention is mostly to continue the process (and parent process) (otherwise they would simply cancel the process).
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2295. Please use this link for any future references and continue any discussion there.