Thanks for replying.
I did almost same thing. I use a property called \”Stage\” instead of \”process\” thought.
I apologize I did make myself very clear in my design intention:
In order to take the advantage of parallel processing ability BizTalk provided, I use a correlation set on message’s WorkID (a GUID). Therefore, each message instance (with a unique WorkID) will instantiate a new correlation – as well as an instance of the the Orchestration hosting that correlation set.
This design create a constrain for me that the signal message has to carry a matching GUID for each instance of the the Orchestration/correlation. That makes the signal message unique from each other as well. That’s why I can’t broadcast it.
I probabily should ask you a question \”Do you think there is another way to realize this kind of parallel processing\” instead of my original question.