My application implements a Worker of job type io.camunda.zeebe:userTask
. In the handler I push the user task data to the browser, which is automatically re-rendered to show the form of this new user task. This has been discussed quite extensively.
Now, I read everywhere that Zeebe user tasks are replacing Job worker-based user tasks. Consequently, I cannot have a worker push the data to the browser.
What is the Camunda architects’ strategy for achieving this with Zeebe user tasks? What comes to mind is to implement a custom Exporter that listens to the create
event, which is emitted when the engine successfully creates a task instance.
I would like your thoughts before implementing it. Not least, since custom Exporters are unavailable in SaaS, this significantly impacts the solution.
Any other ways of solving this?