It seems that my MessageCorelator bean was not even triggered by this. Could you please advise what mistake have i made and how can i start the subprocess by message?
My use case requires me to trigger this sub process from many points of main process (and only from main process), therefore i wanted to embed this sub process in main process model as it still represents a single instance business wise. You are correct about conditional events, in normal case i would do so, however due to my use case (many entry points to sub-process) this would require me to have process variables and some logic between them and i would prefer not to introduce any additional logic. Should i still use variables and logic between them or is there a better solution?
This is more or less what im trying or archive, my initial idea was to use signals, however since signals are global, therefore they can not be used in my case (i need to notify sub-process just within my process instance). Is there a way use signals within process instance only?
Is that the prefered way? it seems that in case of, let’s say, 1mil+ process instancess we will have 1mil+ different signals and tbh this does not feel right when it’s just a signal to process instance relation. I believe you (and your hawk) are right, and at the end i will probably use this solution. Just one final question: is there some mechanic dedicated for within process instance communication (like a signal but taken into consideration just within process-instance)?
Well just to be clear - i don’t actually think i would pick the solution with signals (although it would work) I think it would be better to use escalation events, because then you wouldn’t need the UUID or worry about bad correlation.