• State Not Answered
  • Replies 3 replies
  • Subscribers 5 subscribers
  • Views 1234 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

Web Service Node Failing

apatil

forum.appian.com/.../ #SmartServices : Call Web Service

We are facing a particular issue specific on the "Call Web Service" smart service node.

On a process model which was running smoothly until recently, the response was no longer obtained from any web service calls. BUT, if we delete the particular node and re-configure the it again with the same parameters, the web service gets executed with no issues.

Would this issue occur:
(a) should there be any change to the (input or output) parameters of a particular web service call?
(b) should there be any change to the (input or output) parameters of any OTHER web service method, from the same WSDL server?

Could anyone help us out on figuring out the cause for the issue? & if there is one, how to resolve it?

What would be the best practices to be followed if there are any changes to a web service?

I created a discussion forum post for the same issu...

OriginalPostID-57714

OriginalPostID-57714

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    This could happen if web service changes on the server side. It would typically only happen if the parameters/data types associated with the selected operation change, but could happen if some general changes are made to the web service's WSDL. I would expect that you would see some sort of errors on the web service's logs that make it clear what is going on. Also, you can capture the fault output and see if the web service returned a fault as a result of the call.

    Instead of re-creating a new node, you can also just click the "Refresh Services" button on the Call Web Service setup tab. That will retrieve the latest version of the WSDL and allow you to reconfigure the node for any changed inputs or outputs.
Reply
  • 0
    Appian Employee
    This could happen if web service changes on the server side. It would typically only happen if the parameters/data types associated with the selected operation change, but could happen if some general changes are made to the web service's WSDL. I would expect that you would see some sort of errors on the web service's logs that make it clear what is going on. Also, you can capture the fault output and see if the web service returned a fault as a result of the call.

    Instead of re-creating a new node, you can also just click the "Refresh Services" button on the Call Web Service setup tab. That will retrieve the latest version of the WSDL and allow you to reconfigure the node for any changed inputs or outputs.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.