Major Currently, once a workflow is designed with it's tasks, the layout for each task has to be built in Designer, but the transitions performed, the action buttons are handled by WebUI at runtime, so the user clicks a button, and the linked automation chain is ran and the transition applies, and the workflow moves to the next task (or stop it was the last task)
From WebUI, we need more control on what happened after the user clicked the button, so we can also adapt the UI accordingly, typically for example toi display a short message.
That being said, there are possibly 3 automaiton chains involved:
1. The task output chain
2. The transition chain
3. The task input chain of the next task
I believed we can ignore 3. in the context of the UI
But, form inside nuxeo-task1234.layout.html, it would be nice to be able to use a callback that receives information:
-> The chains that ran, if any (1 and/or 2)
-> The result of each: success or error