Camunda 8 Receive task does not seem to support inputs till date like in C7.
Q1. How to pass input variables to Receive Task other than using Zeebe clients.
Q2. Even in pre migration guide does not mention it is not supported.
Will it be supported in future?
an input mapping for a receive task will create local variables. Then the task has to wait until the message arrives and continue with the outgoing sequence flows afterwards.
What purpose should a local variable serve for a receive task? Do you have a concrete example?
Hey @Ingo_Richtsmeier ,
Thanks for response.
In Camunda 7 we had a use case where the input mapping was being used in a timer event attached to the message task. The input passed was being used as a key to fetch value from a cache/service. And timer had an execution listener attached which did some business relevant task once the timer expires.
MessageTask_Sample.bpmn (3.1 KB)
as listeners are not supported in Camunda 8, your example from Camunda 7 needs some modification.
I would model the business logic explicitly with an outgoing sequence from the attached boundary timer event. Here you can fetch the value from the cache/service and then invoke the business relevant task.
If you name the tasks in a readable way, nobody should complain about the tasks.
Hope this helps, Ingo