XFA Specification
Chapter 11, Forms That Initiate Interactions with Servers
Submitting Data and Other Form Content to a Server
328
5. Execute the scripts in any events activated as part of submit processing, provided those scripts contain
a
runAt
attribute set to
server
or
both
and provided they do not contain
submit
elements.
Example of an event that does not expect data to be returned from the server
<field name="Button1" …>
<event activity="click">
<submit target="mailto:me@example.org"
textEncoding="UTF-8" xdpContent="datasets template"/>
</event>
</field>
<field name="NumericField1" …>
<value>
<float>100</float>
</value>
</caption>
<event activity="preSubmit" ref="$form">
<script runAt="server">valueA * valueB</script>
</event>
</field>
<field name="valueA" …>
<value>
<float/>
</value>
</field>
<field name="valueB" …>
<value>
<float/>
</value>
</field>
Client Submit Event That Processes Data at the Server
This section describes the processing steps that are initiated when a submitting event is activated. The
steps depend on whether the XFA processing application declares itself as a client or as a server.
Client-side actions
The client XFA processing application performs the following steps when a
submit
event is activated. The
submitting event requests data be processed and returned. (See the table
“Factors That Influence
Submission Behavior” on page 326).
1. Package the data and any other content, as specified in the
submit
properties
format
,
embedPDF
and
xdpContent
. (“Content
2. Include in the package an indication of the event initiating the submission.
3. Send the data to the server using the HTTP POST operation.
4. When the HTTP POST operation returns (Step
2.
For more information on the HTTP POST interchange, see [HTTP].
The response to an HTTP POST failure is implementation-defined.