Working with Web Services in SharePoint 2013 Workflows using SharePoint Designer 2013
Demonstrates how to use web services in SharePoint Designer 2013 workflows.
Last modified: December 12, 2013
Applies to: SharePoint Foundation 2013 | SharePoint Online | SharePoint Server 2013
In this article
Why are web services important for SharePoint 2013 workflows
Leveraging web services in SharePoint workflows
Creating web services for SharePoint 2013 workflows
Create a workflow with SharePoint Designer 2013
Microsoft has taken a fresh approach to workflows in SharePoint Server 2013. The workflow team worked with the Microsoft Azure team to create a new product called Workflow Manager. Workflow Manager serves as the host for the latest version of the Windows Workflow Foundation runtime and provides all of the necessary services as well as leveraging the Microsoft Azure Service Bus to enhance performance and scalability. Once deployed, it runs the same whether in an on-premises deployment or deployed to the cloud. Importantly, SharePoint 2013 hands off all workflow execution and related tasks to the Workflow Manager farm, which is external to SharePoint 2013.
One of the more significant changes to the workflow architecture is that now all workflows are authored in a declaratively, on a designer surface, including those built using Visual Studio 2012. In previous versions of SharePoint, workflows developed with Visual Studio 2012 were not exclusively declarative. Instead, they were a mix of declarative XAML and a compiled assembly that contained the workflow business logic.
For those customers who have created workflows using SharePoint Designer in the past, this is nothing new. Workflows authored using SharePoint Designer have always been fully declarative. This change does benefit customers who create workflows using SharePoint Designer 2013, however, because SharePoint Designer 2013 workflows now support calling and consuming web services.
Let’s start by understanding scenarios in which using web services makes sense. In the days of SharePoint 2007 or SharePoint 2010, writing custom code was common when using Visual Studio to author workflows because that was the best way to perform calculations or implement custom business logic. Any time you encountered a situation in which the out-of-box actions and activities didn’t meet your needs, you could fall back on custom code in a managed assembly.
For the non-developer users of SharePoint Designer 2013, on the other hand, this was not so easy. When you ran into a use cases that you couldn’t handle with existing workflow actions, you had to call in a developer to write a custom action. Often, this was difficult because they could only create code for the sandbox (when in a hosted environment), or could only use fully-trusted solutions if in an on-premises deployment. In other cases, the workflow had to be completely handed over to a developer to build as a fully-trusted solution because what was needed could not be achieved in SharePoint Designer.
Now comes the good news: In the world of SharePoint 2013, when SharePoint Designer 2013 lacks an action that you need, all you need is to create a custom web service. And creating a custom web service is much easier than creating a custom action. Not only that, but whereas a custom action could only be used by the workflow in which it’s installed (or, at best, by only a SharePoint workflow), a custom web service is portable and can be used by any number of consumers.
Perhaps best of all, in cases where there is an existing web service that you need to access – either a public one, or perhaps a private web service that is hosted by your company – SharePoint Designer 2013 now provides an action that you can use to call the web service. There is no longer any need to rely on a developer when you need to call an existing web service.
This recommendation is based on their being support for these OData formats in SharePoint 2013 workflow authoring tools (both SharePoint Designer 2013 and Visual Studio 2012). Both tools support building payloads to submit to the service and for handling the responses returned by the web services. Additionally, the OData formats support communication with anonymous web services as well as with those protected by various types of authentication. In short, you have full control over the request and response for each service call. This allows you to use a series of activities within a workflow to first authenticate using one service and obtain an OAuth token, and then include that token in future requests to services secured using the OAuth 2.0 protocol.
Invoking web services from workflows using SharePoint 2013 takes place in two stages: first is calling the web service, then is exchanging data with the web service.
In SharePoint 2013 workflows, you call a web service using a new action introduced in SharePoint 2013 named Call HTTP Web Service. This action is flexible and allow you to make simple calls to a web service easily, or, if needed, you can create more complex calls using HTTP verbs as well as allowing you to add HTTP headers. Figure 1 shows you the Call HTTP Web Service action on the SharePoint Designer 2013 surface.
The Call HTTP Web Service action lets you specify any of several request methods, including GET, PUT, POST, and DELETE. This lets you tell the web services, specifically RESTful services, what to do on the service that you’ve specified with the URI property on the activity.
For instance, to get all the properties of a specific item, the service URL would contain the unique address of the item, and you would set the method to GET. To delete the item, the process is the same, except you set the method to DELETE. The same is true for updating an item, except for setting the method to POST. When you create an item, set the URL to the unique address of the collection where the item is to be created, and then set the method to POST. When creating or updating items, services generally require the data to use, which you pass along as content in the request, then indicate using the request property on the Call HTTP Web Service action.
The second stage of working with web services involves submitting data to, and receiving data from, a web service, which you do by using either the request or response properties on the Call HTTP Web Service action. Note, however, that rather than as a stream, data is passed as a complex structure using the Dynamic Value object. (For more information about dynamic values, see Understanding Dynamic Value.)
There is a series of activities associated with the DynamicValue type that can be used to count the number of items in the response, extract values from the response, or build up a new structure for updating or creating items. Note that SharePoint Designer 2013 does not support working directly with the DynamicValue type and instead, workflow authors will use the Dictionary type.
So we’ve learned that SharePoint Designer 2013 supports calling web services, but that it doesn’t support invoking custom code from workflows. Consequently, you will need to know how to create a web service if you wish to extend the functionality of your workflows beyond the default actions.
Fortunately, there are plenty of options for creating custom web services for use in SharePoint 2013 workflows. Specifically, the HttpSend activity, along with the DynamicValue data type, are ideally suited for creating RESTful web services that conform to the OData protocol.
OData is a protocol for creating and consuming data based on the principles of REST services. It was developed to standardize exchanging data using mature, reliable, and robust HTTP protocols. Once the OData specification was complete, different organizations implemented the protocol on their own technology stacks. Microsoft implemented its own version of OData, which it branded WCF Data Services.
Following are discussions of two common scenarios in which RESTful web services are useful to workflow developers:
Implementing OData service CRUD-Q operations
Implementing OData service operations
Implementing OData service CRUD-Q operations
A common use for web services is performing simple create, read, update, delete, and query (CRUD-Q) operations on data in a database. It is relatively easy to create an OData web service for a SharePoint 2013 workflow WCF data service an OData service to be used by a workflow by using WCF Data services. You can review the walkthroughs and samples on creating web services at sites like WCF Data Services, www.OData.org, and others.
Assuming that you already have database that you can operate against, there are four short steps:
Create a model of the database using the Microsoft Entity Framework. There is no code required as this is a wizard-based creation in Visual Studio. For additional information, see Entity Framework 4.0 and WCF Data Services 4.0 in Visual Studio 2010 and Entity Framework Designer Gets Some Love in Visual Studio 2012.
Create a new WCF Data Service. Again, no code is required in this Visual Studio wizard. For more information, see Walkthrough: Creating and Accessing a WCF Data Service in Visual Studio.
In the service code file, set the name of the entity model that you created in step one to the source of the service; then, set the accessibility and permission for the entities in the model (both steps implemented in as little as two lines of code).
Publish the service to a location that Workflow Manager can access.
Implementing OData service operations
There’s a pretty good chance that your workflow wants to run some business logic that doesn’t fit into limited the CRUD-Q model. For example, there may be an OData service that supports CRUD-Q operations when it creates a new bank loan. This service might also ask for consumers to call the service and provide a credit score so it can then retrieve the current interest rate. Such a task exceeds the capability of simple CRUD-Q operations, since it calls a method, passes in an integer, and receives a response.
However, you can support this scenario by using OData and WCF Data Services, through which you can implement Service Operations. Service operations are common, and are even used in the SharePoint 2013 services. For example, when SharePoint retrieves a specific list using the address format http://[..]/_api/web/lists/GetByTitle(‘ListTitle’), the GetByTitle() function in the address is actually a service operator that was created by the SharePoint 2013 team. Typically, developers create their custom service operations in web services they create using WCF Data Services.
The following walkthrough demonstrates how to create a custom workflow that calls the OData web service of the Northwind database, which you can find publically hosted at the www.odata.org site. In this sample, the user enters a customer ID and then starts the workflow, which takes the customer ID and uses it to query the web service to collect additional information about the customer – specifically, the user’s full name and employer. The workflow then takes this information and updates the list item by adding the user’s customer name and employer.
Create a customer list
In SharePoint Designer 2013, create a custom list and name it "Customers".
Rename the Title field to Customer Id.
Add two new fields of type String and name them Full Name and Employer, as shown in Figure 2.
Create the workflow
In the SharePoint Designer 2013 navigation pane, select the Workflows option.
On the ribbon, click the List Workflows button and select Customers from the resulting drop-down list.
Name the workflow "Get Customer Details".
Set the Platform Type to SharePoint 2013 Workflow, as shown in Figure 3.
Query the web service for the customer details
Now that we’ve created the workflow, we want to enable it to call a web service, which we do by adding a Call HTTP Web Service action to the workflow’s default stage.
Click on the link labled this.
To the right of the Enter the HTTP web service URL text box, click the builder button (…) to open the String Builder dialog box.
In the String Builder, enter this URL: http://services.odata.org/Northwind/Northwind.svc/Customers(‘CUSTOMERID’)?$format=json&$select=ContactName,CompanyName. Notice the "$select" portion of the URL is retrieving only the fields that are relevant to this list.
In the URL, locate the URL segment CUSTOMERID and remove it. Leave the parentheses and single quotes in place.
To then dynamically create the full URL, click the Add or Change Lookup button in the String Builder.
In the resulting Lookup for String dialog box, set the Data Source to Current Item and set the Field from Source to CustomerId, as shown in Figure 4.
Click OK, then OK again to accept the new URL.
Now that we’ve set this up to receive results from the web service, next we need to store the results in another variable.
In the Call HTTP Web Service action, click the response link in the action and create a new variable of type Dictionary and name it nwServiceResponse.
The entire Call HTTP Web Service action is not likely visible, since it is a long sentence in the designer. Scroll to the right and notice that the response status code is stored in a variable called responseCode. This is convenient, and something that can be written to the workflow instance’s statistics page using the workflow history list.
Add a Log to History List action after the Call HTTP Web Service action and set its message to write the status code for the response to the log, as shown in Figure 5.
Extract values from response
Now that we have the web service response stored in the nwServiceResponse variable, the next step is to extract these values and place them in local variables.
To do this, we’re going to add two Get item from dictionary actions to the workflow. Note that the path to the item from which we’re going to extract a value has to match the structure of the response and be in a specific format. A good way to figure this out is to enter the URL into the browser to see the response that comes back. Notice that the results are nested within the object called d. Therefore the path to the field CompanyName in the web service response is d/CompanyName.
Add two Get item from dictionary actions to the workflow.
On the first of these new actions, set item by name or path to d/ComopanyName.
Set the dictionary link to nwServiceResponse.
Set the item link to a new String variable named CompanyName.
Repeat steps 2, 3, and 4 on the second Get item from dictionary action, except to use ContactName instead of "CompanyName", as shown in Figure 6.
Update the list item
The final step is to update the list item using two of the Set field in current item actions. These set the fields in the list item to the values stored in the variables we created, as shown in Figure 7.
And finally, we complete the Transition to stage section of the workflow stage.
Add a Go To Stage action.
Select End of workflow.
Save and publish the workflow.
Test the workflow
Open a browser and navigate to the Customers list.
Add the two customer IDs that are in the Northwind service on two new list items, ALFKI and ANATR.
Manually start the workflows by selecting each item, then clicking the Workflows button on the ribbon.
Select the Get Customer Details workflow.
At this point the workflow will start and will query the web service.
Navigate back to the Customers list and refresh the page. It might take a few refreshes for the workflows to complete, but eventually it should look like the image in Figure 8. You should see both list items updated with the customer’s full name and their employer, which came from the Northwind web service.
SharePoint 2013introduced a new workflow architecture facilitated by a new product, Workflow Manager 1.0. To ensure that all custom workflows worked regardless of the SharePoint 2013 deployment choice, either on-premises or hosted in Office 365, all workflows are now 100 percent declarative. The added support for calling web services from SharePoint Designer 2013-authored workflows provides a more flexible and powerful workflow authoring process than in previous versions.
Microsoft introduced support for calling web services in Workflow Manager using the new Call HTTP Web Service action in SharePoint Designer 2013. Workflow Manager also introduced support for creating structures to submit to web services as well as consuming their responses using the Dictionary variable type. When creating workflows, use the Dictionary type and associated actions in SharePoint workflows that use external web services.