You are viewing limited content. For full access, please sign in.

Question

Question

Creating SOA requests from Workflow

asked on January 24, 2014

 I am trying to use the HTTP Form Post activity to access a web service.  The web service is using SOAP, which, if I understand correctly is not directly supported by Workflow.  However, is there a video or some type of demo or walk-through that can describe the process of accessing a web service from Workflow?

1 0

Answer

SELECTED ANSWER
replied on January 24, 2014

We currently don't have a video or demo to walk through the process. The best method I can suggest right now is to make a custom activity that has a service reference to your SOAP service. You'll find the experience to be much more reliable with this method.

 

The reason workflow doesn't support SOAP is that its a lot more complicated to make the request from the activity because you have to build the more complicated SOAP message and there isn't documentation on what it should look like.

 

REST API services generally just need a URL to do something interesting or very simple post bodies, without the need for complicated headers.

 

Also, the REST API documentation tells you what you need to put into the activity in most cases.

 

If you have sample program that already uses the service you could try using a tool like Fiddler that will show you what the request should look like.

 

 

2 0
replied on January 24, 2014

Thanks Ed - my organization is currently using SOAP for all web services.  I'm relatively new to this topic, but will have to analyze if we will want to build custom activities for each web service we consume, or make a push to change to REST.  

0 0
replied on January 24, 2014

This is essentially what I've done with a particular integration that required accessing a SOAP service. In this case I built a custom .NET assembly that handled the integration and then integrated it into a Workflow activity.

 

The only way that I could see Workflow directly supporting SOAP services is if it first required a WSDL file. Still very complicated to do in an automated way, but you could probably map the parameters. Of course, not all SOAP services are the same. Some are very clear and others are far too vague to usefully sniff automatically.

 

As you've said, it's complicated.

2 0
replied on July 21, 2014

Hi Devin, Have a SOAP-based Web Service integration project with accompanying WSDL files. Can you expand on the way workflows could support the SOAP services directly as stated in you reply above?

0 0
replied on August 8, 2014

Hello, I just noticed this reply. As I recall, I'd intended my reply to be directed at Ed in the context of how Laserfiche could implement SOAP support into Workflow.

 

As a user, I still think the best option to interact with SOAP services from Workflow is to write your own assembly and then reference it from a Workflow script.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.