Yes you need to Reader Enable the form to do client side Web Services. Those Web Services will not work in the Guide. You can do a server side Web Service call and that technique will not require Reader Extensions, but you will do a round trip to the server each time the service is run.
The Form Guide cannot do the web service on its own (without modifying the Flex code underneath). The PDF that is created behind the Guide can have a server side WS call that can be used to populate the PDF dropdowns which in turn will populate the Guide. The Web Service is coded in the XDP template and is setup to run server side. The activation of the WEb Srevice must be done on an event that is shared between the guide and the PDF (i.e. a button click).
We have made a data connection to a wsdl. We have binded this to a drop down via the Dynamic Properties. We have tried activating it via various events (initialize, click) using xfa.connectionSet.DataConnectionName.execute(0);
I have even tried to drag the data connection onto the form to test that way.
Everywhere we select run at server.
But nothing happens - neither in form nor form guides.
I can't see anything in any logs.
If we set it to run on client we get the error message from reader (no reader extensions).
What would be next step to find out what is happening? Are we missing a configuration somewhere?
Sorry to butt in here, but we are currently facing pretty much the same problem, but with an additional wrinkle. The webservice we are trying to invoke is a LiveCycle service which will take the current contents of the form and print it.
First, as a proof of concept we built a stripped down form/form guide, (i.e three fields and a button) where we can invoke the service from the form guide, with the run at server option set. This works great.
Then we tried to migrate this to our main form/form guide (we added the three fields and the button). Both forms use the same render services, both have been set up to run the web service at the server. But the main form/form guide will not invoke the webservice.
I'm at a loss to figure out what is different between the proof of concept form guide and the main form guide, other then size of course. (the example XML file for the main form would be approximately 25Kb)
Any assistance on this would be greatly appreciated.
Actually, we managed to isolate the problems down to the form/form guide level. We started deleting fields and objects from the form/form guide until it started working. We eventually got the webservice to work.
After doing this clean up the form/form guide we managed to get everything working. Everything we need is now in a fresh version form and form guide, and the web service is functional.
Now, for some reason every time we try to delete the old form from the server, LiveCycle crashes.