tag:blogger.com,1999:blog-1804865242850018128.post3783536170353610532..comments2023-09-27T14:29:55.934+07:00Comments on Sohel's Blog: SharePoint 2013 Workflow: Use HttpSend Activity to call Custom SharePoint WCF ServiceAnonymoushttp://www.blogger.com/profile/15485221969375347012noreply@blogger.comBlogger20125tag:blogger.com,1999:blog-1804865242850018128.post-82155667957288597632015-08-13T22:21:30.077+07:002015-08-13T22:21:30.077+07:00Hi Sohel,
Can we call a Windows Service using htt...Hi Sohel,<br /><br />Can we call a Windows Service using httpSend activity in SharePoint 2013?Sakethttps://www.blogger.com/profile/07789159365456811467noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-82521384437319391692015-03-01T09:20:30.548+07:002015-03-01T09:20:30.548+07:00I was also getting the bad request. To fix it make...I was also getting the bad request. To fix it make sure you not only use MultipleBaseAddressWebServiceHostFactory but use the 15.0.0.0 version. I was getting error because I was using 14.0.0.0 version.Naumanhttps://www.blogger.com/profile/11197458970640022927noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-19580799974547577312014-03-02T04:06:39.458+07:002014-03-02T04:06:39.458+07:00I have tested HTTPSend activity's authorizatio...I have tested HTTPSend activity's authorization attribute as "" with HTTPs site (Site and workflow service app both are running on HTTPs) and it's working fine.Sourabh Khatrihttps://www.blogger.com/profile/10414914862438060839noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-56073957382825581972014-02-25T14:55:02.922+07:002014-02-25T14:55:02.922+07:00thanks to replay.
I add the Microsoft.sharepoint.d...thanks to replay.<br />I add the Microsoft.sharepoint.desgin.activity and i can get it.Anonymoushttps://www.blogger.com/profile/11973993788217007281noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-9273187251140904912014-02-20T09:24:11.539+07:002014-02-20T09:24:11.539+07:00@abdelmohsen, I think it's not shown by defaul...@abdelmohsen, I think it's not shown by default. Try to browse and add the SharePoint Designer activities dll from workflow installation directory (mabye in program files directory)Anonymoushttps://www.blogger.com/profile/15485221969375347012noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-50468689159625439972014-02-17T21:21:45.396+07:002014-02-17T21:21:45.396+07:00Frist thank you for this great effort it help me i...Frist thank you for this great effort it help me in WCF creating and call , but i need to ask you about set workflow status activity in SharePoint 2013 , because i couldn't find it in tool box, and also couldn't do it as custom activity.<br /><br />thanks in advanceAnonymoushttps://www.blogger.com/profile/11973993788217007281noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-90194744517943759572014-01-28T18:26:05.210+07:002014-01-28T18:26:05.210+07:00Yes Impersonating the user by passing the credenti...Yes Impersonating the user by passing the credentials is a workaround I am already considering.<br /><br />Just was curious as to why the service call was not made from the current user's context by the workflow manager.Vardhaman Deshpandehttps://www.blogger.com/profile/17919845281919756108noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-17160836333544917822014-01-28T18:21:41.731+07:002014-01-28T18:21:41.731+07:00Vardhaman, I'm not sure but I reckon this is e...Vardhaman, I'm not sure but I reckon this is expected. Workflow Service is running under the workflow service account and I expect workflow manager doesn't impersonate the service call. You can dig dipper into the problem or you can go for a simple solution - pass the current username/id in the service call and impersonate the code with the passed user.Anonymoushttps://www.blogger.com/profile/15485221969375347012noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-35954548747990666752014-01-28T15:35:58.548+07:002014-01-28T15:35:58.548+07:00Great Post Sohel, all is working well.
My only i...Great Post Sohel, all is working well. <br /><br />My only issue is that when I invoke the WCF service from the HttpSend activity, the WCF service always runs in the context of the account which is the service account of the Workflow Manager. It never runs with the context of the current logged in user. <br /><br />When I do SPContext.Current.Web.CurrentUser inside the service, I always get the service account of the Workflow Manager. However, If I call the service from the browser, the correct user is returned so the issue is not with the WCF service.<br /><br />My guess is that it has to do something with the Authorization header being set as "". Do you have any idea?Vardhaman Deshpandehttps://www.blogger.com/profile/17919845281919756108noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-14406463567286996132013-12-06T08:31:17.626+07:002013-12-06T08:31:17.626+07:00@Sourabh, the idea of using Authorization header t...@Sourabh, the idea of using Authorization header to empty string can be found at http://social.msdn.microsoft.com/Forums/windowsazure/en-US/d3b8dd8f-a1ab-4a52-be58-dfb3e1f2b2eb/httpsend-to-call-custom-wcf-service?forum=wflmgrAnonymoushttps://www.blogger.com/profile/15485221969375347012noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-17145383046900724752013-12-06T03:35:30.714+07:002013-12-06T03:35:30.714+07:00Hi Sohel, I was getting 401 error while calling cu...Hi Sohel, I was getting 401 error while calling custom WCF service (Hosted in SP) from workflow. Based on code you shared I changed the request header autherization with "" and it's working fine. I just want to know this is the only solution did you find or any other solution also available for same problem. Please also help me to know your opinion to set request header autherization ="" for production environment.Sourabh Khatrihttps://www.blogger.com/profile/10414914862438060839noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-17107271976497492122013-10-28T22:45:06.884+07:002013-10-28T22:45:06.884+07:00@Russell, As I can remember I couldn't find an...@Russell, As I can remember I couldn't find any property to get Site Collection Url. Maybe it's by design as workflow will be executed under current site context?Anonymoushttps://www.blogger.com/profile/15485221969375347012noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-80778923184927786452013-10-28T10:40:07.282+07:002013-10-28T10:40:07.282+07:00I used LookupWorkflowContextProperty -> Current...I used LookupWorkflowContextProperty -> Current Site to get the site URL which I expected to be http://xzy.local/ but instead it returned http://xyz.local/pm my Project Management sub-web. Do you know any other way in 2013 Workflow to return the site collection url? Thanks SohelLownlazyhttps://www.blogger.com/profile/05392233266906950235noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-29257733105110349612013-08-30T03:46:53.063+07:002013-08-30T03:46:53.063+07:00Where can I get Microsoft.SharePoint.Client.Server...Where can I get Microsoft.SharePoint.Client.ServerRuntime.dll? I have downloaded SharePoint Server 2013 Client Components but it's not there. ThanksGonzalohttps://www.blogger.com/profile/13246482430004895205noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-24452852985943811822013-07-16T03:44:59.843+07:002013-07-16T03:44:59.843+07:00Thank you, really, THANK YOU!Thank you, really, THANK YOU!emzerohttps://www.blogger.com/profile/17660002158531752758noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-52356524502466749922013-06-25T19:52:25.899+07:002013-06-25T19:52:25.899+07:00I've been getting Bad Request 400 response. Th...I've been getting Bad Request 400 response. The solution is to change the Factory in .svc file to use MultipleBaseAddressWebServiceHostFactory used for REST services instead of MultipleBaseAddressBasicHttpBindingServiceHostFactory that is used for SOAP services.Anonymoushttps://www.blogger.com/profile/12199462402642676941noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-87085001896370387452013-06-25T19:51:44.692+07:002013-06-25T19:51:44.692+07:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/12199462402642676941noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-50652767324195090252013-06-20T11:26:31.942+07:002013-06-20T11:26:31.942+07:00I can access right now. Thank you so much:)
Two t...I can access right now. Thank you so much:) <br />Two tight details:<br />1. Using SharePoint default factory 'Microsoft.SharePoint.Client.Services.MultipleBaseAddressWebServiceHostFactory, Microsoft.SharePoint.Client.ServerRuntime, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' in WCF .svc<br />2. Add Authorization="" to RequestHeaders property at HttpSend action Chad Liuhttps://www.blogger.com/profile/10409678754702113315noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-67089286601357600412013-05-25T21:34:57.059+07:002013-05-25T21:34:57.059+07:00Accessing WCF service is not related to anonymous ...Accessing WCF service is not related to anonymous access. If your WCF service deployed properly, you should be able to access the WCF service. You can download the code for this post from msdn code gallery and find out if the WCF service works.Anonymoushttps://www.blogger.com/profile/15485221969375347012noreply@blogger.comtag:blogger.com,1999:blog-1804865242850018128.post-82436778842290535872013-05-24T22:14:02.524+07:002013-05-24T22:14:02.524+07:00I cannot access my customized WCF Service deployed...I cannot access my customized WCF Service deployed on MOSS2013. HTTPCode is badrequest. Have you enabled your WCF service access anonymously? Chad Liuhttps://www.blogger.com/profile/10409678754702113315noreply@blogger.com