My team is working with getting the WS Smart Service to connect and work with th

robbier over 9 years ago

My team is working with getting the WS Smart Service to connect and work with the Docusign web service API. It seems we can get a SoapUI client to successfully make calls to the service and get the document information based on request.

With the smart service the problem seems to be, even though the WSDL url is demo.docusign.net/.../dsapi.wsdl, the namesspace associated with it is www.docusign.net/.../3.0 (so http not https). So notice the difference here--actual WSDL is https but the namespace is http.

We can update the SoapUI config to accomodate but it seems the that the WS Smart Service always uses the default namespace which results in an http 301 error. Is there anyway to override this in the smart service?

Discussion posts and replies are publicly visible

0 Tom Ryan
Appian Employee
over 9 years ago

I'm not sure if the OOTB smart service can handle this. Some other options could be to look at the Advanced Call Web Service plugin

forum.appian.com/.../Advanced_Web_Service_Configuration.html
forum.appian.com/.../summary

or the web service connector functions

forum.appian.com/.../Connector_Functions.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 robbier over 9 years ago

I was looking at the Advanced Web Service Plug-In. It didn't give details in the description as to whether it allowed overriding but I'll download and give it a try.

Thanks for your suggestions!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 robbier over 9 years ago

Turns out that the development documentation for Doculabs wasn't 100% clear and one of the developers (on our end) was referencing the wrong schema. Now that we cleared that up it turns out Appian's OOB WS SS is at least able to connect and run the Doculabs functions. That said, it is good to get refreshed on the other options available as well.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 gauravg568 over 9 years ago

Hi robbier, we're facing a similar issue in integrating with docuSign in that we too are seeing a 301 error. Would appreciate your insight on the WSDL URL and targetNameSpace to resolve this issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel