|
When a user requests a form from the Forms service (for
example, by clicking a button located on an HTML page), the request
initiates a Forms service operation. This table summarizes the interaction
among a client device (for example, a web browser), a client application,
and the Forms service when a user requests a form.
User actions
|
Client application actions
|
Forms service actions
|
|---|
A user requests a form from a web page.
|
No action
|
No action
|
No action
|
Invokes an operation such as renderPDFForm.
|
No action
|
No action
|
No action
|
Retrieves the form design that is specified.
|
No action
|
No action
|
If data is passed to the Forms service,
it prepopulates the form with the data.
|
No action
|
No action
|
Executes all form-wide field initialize
events.
|
No action
|
No action
|
Executes all form-wide page initialize events.
|
No action
|
No action
|
Executes all form-wide field calculate events.
|
No action
|
No action
|
Executes all form-wide page calculate events.
|
No action
|
No action
|
Executes a page enter event.
|
No action
|
No action
|
Executes a form ready event.
|
No action
|
No action
|
Executes a page enter or exit event.
|
No action
|
No action
|
Transforms the form design into the format specified.
|
No action
|
No action
|
Returns the form to the client application.
|
No action
|
Verifies that an error was not returned.
|
No action
|
No action
|
Creates a binary stream and sends it to the
client web browser.
|
No action
|
Internet Explorer, Mozilla, Netscape Navigator,
and Opera browsers perform these actions:
Runs
each field initialization marked Run script on client
Runs the page initialization marked Run script on client
Runs each field calculation marked Run script on client
Runs the page calculations marked Run script on client
Note: These
actions occur only if the form is rendered as HTML.
|
No action
|
No action
|
Views the form as either PDF or HTML.
|
No action
|
No action
|
|
|
|
