To see scripts in a form, you need to select the object(s) who scripts you want to see and then use the Script Editor palette.

As for executing a web service on a FormReady event, I would recommend you simply invoke it programmatically by calling its execute() method:

xfa.connectionSet.{WebServiceDataConnectionName}.execute(1);

The difference between the Initialize and the FormReady events is that Initialize occurs immediately after data merge however prior to calculations and validations whereas FormReady occurs immediately after validations (so Initialize, Calculate and Validate events occur prior to FormReady). Both events occur prior to master page layout (which includes Initialize, Calculate and Validate for master pages). Finally, the LayoutReady event occurs, followed by DocReady.

It’s difficult to tell if it’s SP3 or your form without knowing more about the internals of your form.

Could you please explain what is the difference between the “form:ready” and “intialize” events. I used to have the code to execute the web service in the “form:ready” event which worked fine and then it stopped working which does not execute the web service when there is no change in the web service. This happens after the LC ES service pack 3 was applied. So I moved the code from the “form:ready” event to the “intialize” and it works fine then. I couldn’t tell whether it the sp3 or the form, could you please advise.

Thanks,
Han Dao

There are 3 types of data connections: schema, database and web service. None of them would be hitting your LC server per se unless you exposed a web service from one of your LC services (built in Workbench). For schemas, it must be a local file or a resource in the LC Repository and for database, it’s via a DSN defined on the local system.

The DSN holds credentials for authentication and for web services, Designer 8.2 has basic support for authenticated web service calls (which you setup in the Data Connection Wizard).

Thanks,
Mohan

While I’m no expert in that area, I would think that you could do it in many ways using LiveCycle. For example, you could define the web service data connection in the form but have it execute on the server rather than the client.

Depending on how your LiveCycle process was setup, another option could be to execute the web service call first, gather the returned data and merge it into the form when serving it out to the client (this way, the form doesn’t know anything about the web service).

How is this type of architecture implemented ? I couldn’t get any architectural guidelines dealing with Adobe e-forms and how it aligns with the established web application designs.

Thanks,
Mohan