Closed elek closed 10 years ago
I see a problem with this pull request. As I would like to switch to runtimeService.correlateMessage instead of startProcessInstanceByMessage - see comments in the lines before. But then no priocessInstance is returned. So I would like to NOT add this to keep this flexibility. OK? What do you think?
Gave it a second thought: Yepp - I will close this pull request. If you need the process instance id I would suggest to use the StartProcessInstanceProducer (camunda-bpm://start). Feel free to object :-)
I think they are two different things. We would like to use a process with multiple starting point. In that case we can't use start (=startProcessInstanceByKey) which could be used only if there is one and only one start message.
If you don't like it what do you think about improving the camunda-bpm://start to use startProcessInstanceByMessage if the messageName parameter is used?
Hi Elek.
This actually sounds like a good idea and I do not yet foresee showstoppers here
"improve the camunda-bpm://start to use startProcessInstanceByMessage if the messageName parameter is used."
If you create a proper pull request (including a test case plase) I am happy to merge it!
Cheers Bernd
Sometimes it would be useful to get the instanceId if of the new process which has been started.