Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If I understand you correctly, you use a WCF Service to send a task to SharePoint (you may be able to use the BizTalk SharePoint Adapter to do this directly - I have ner used it, but I think this is the kind of thing it can do). The event handler in SharePoint fires when the task is marked complete and then sends a message back to BizTalk.</p> <p>To get the message back to BizTalk, you will need to create a WCF Receive Location. This receive location can be either one way or two way. These are really both two way receive ports. The Port receives the message from SharePoint via WCF and then sends a repsonse back to SharePoint to ack the receipt. BizTalk considers it a one way receive port if it only sends back an ACK. It considers it a two way receive port if it sends back the ACK along with a message.</p> <p>So in a nutshell, you need to set up this second receive port in the orchestration. Publish it as a WCF web service. You also need to set up correlation so that the message can find its way back to the correct orchestration instance. Here is a good blog post on correlation: <a href="http://mstecharchitect.blogspot.com/2009/03/message-correlation-in-biztalk-2006.html" rel="nofollow noreferrer">http://mstecharchitect.blogspot.com/2009/03/message-correlation-in-biztalk-2006.html</a>.</p> <p>The key to successful correlation is having a promoted property in each message that can be used to tie them back togeather. So the task you send to SharePoint should have a unique TaskID (or whatever). And the response from SharePoint should have that same promoted property in the repsonse.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload