WebService Component

[Former Community Member]

I've created a (LiveCycle 7.2) workflow that is webservice enabled that I had originally intended to be called from a form. Basically, it takes an input param, runs a SQL Stored Procedure, then outputs two parameters.



When called from the form, everything works fine, the output params pass data back to the form. Now, I'd like to move the webservice call into the main workflow, rather than be called from the form. Using the WebService Component, the main workflow does call the webservice, pass in the input parameter and I know the Stored Procedure runs correctly. However, none of the output parameters being XPath mapped to workflow variables contain any data.



Any ideas?

[HowardTreisman]

Hi

If you're calling one workflow from another, it is much simpler (and more efficient) to invoke the service using the Chain QPAC rather than the web service QPAC.

Howard

http://www.avoka.com

[Former Community Member]

Thanks Howard, using the Chain QPAC worked. I'm still curious about the WebService QPAC though - does it just not work for me or is it a bug?

Fortunately my Web Service is on the same server as my main workflow so the Chain QPAC is sufficient - I'm not sure what my solution would be if it was on another server though.



Thanks all the same.

Michael

[HowardTreisman]

Hi Michael

I'm not an expert on the Adobe Web Services QPAC.

One of the issues may be the data-types that you are producing/consuming - you're better off sticking to simple data types, and no repeating elements.



We have built our own Web Services QPAC, which is a little harder to use (no graphical mapping User interface), but deals a bit better with more complex WSDL files. It depends on the service you're calling as to which one is better.

You can download it and give it a try if you're interested:

http://www.avoka.com/Avoka/qpac_library.shtml



Sorry I can't offer you any better solution.



Howard

http://www.avoka.com