Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Outbound Messaging
Collapse the table of content
Expand the table of content

Outbound Messaging

Updated: July 16, 2012

Workflow Manager 1.0 provides activities for both HTTP-based and SOAP-based messaging, including two-way (request-response) and one-way patterns.

Outbound Messaging

HTTP messaging can be done using the HttpGet, HttpPut, HttpPost, HttpDelete, and HttpMerge activities. These activities provide access to the request and response content, as well as the Uri, headers, and the status code. The body contents of the request and response messages can be controlled using a DynamicValue, which has a natural serialization to JSON, although XML formatting is also possible. For more information on these activities, please see Working with complex data in a workflow, DynamicValue Activities, and Http Activities.

The .NET 4 Framework Send & ReceiveReply activities can be used for SOAP-based messaging, although custom code is required. (For more information on supporting custom code in Workflow Manager 1.0, see Using Custom Code in Workflow Manager 1.0).

In this release of Workflow Manager 1.0, Add Service Reference functionality is not supported.

Workflow Manager 1.0 MSDN Community Forum

Build Date:


Community Additions

© 2015 Microsoft