Currently, it is intended that actions and processes executed via the API return taskId's visible in the /tasks/ endpoint. These same tasks when executed via the web UI are not intended to return a taskId, resulting in different levels of detail returned by the API depending on the method of execution.
We propose that all Processes and Actions, regardless of the method used to execute them, should return a taskId that can be seen in the /tasks/ endpoint.
This would positively impact users, as it would provide consistency and they could expect the same level of detailed returned by the API across all situations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.