Flow message tasks overhaul
Correctly configuring message tasks in your process diagrams has been a complicated and error-prone task for a long time.
In Flow-Process v11.6 however, we are introducing a new way of implementing and interacting with message-tasks without the complexities of correctly mapping up process variables and correlation keys in your task handlers.
Now, message-tasks can be triggered similarly to how user-tasks are completed today by using the new POST /tasks/{taskId}/trigger-endpoint. If you switch to using this new endpoint, you will also no longer have to set up
correlation keys, or map up local process variables to trigger specific instances of your message listeners as this will be automagically mapped up
for you.
From v11.6 and onwards, we strongly recommend using this new endpoint for completing message-tasks as it can help you avoid introducing a lot of unnecessary complexity to your projects.
Additionally, the old functionality for triggering messages on flows via message name has been deprecated, and will likely be removed in a future major version.
For additional details, see the following links: