XFA Specification
Chapter 11, Forms That Initiate Interactions with Servers
Submitting Data and Other Form Content to a Server
325
processing. Before the content submission is allowed to progress, the form data must be successfully
validated and other scripts must successfully execute. Typically, if the validation or scripts fail, users are
asked to make corrections and resubmit the form. When the processing application successfully submits
the form content, the form is said to be
committed.
That is, the content is in a final form.
<field name="Button1" y="223.31mm" x="134.41mm" w="35.98mm" h="18.52mm">
<ui>
<button/>
</ui>
…
<event activity="click">
<submit
embedPDF="1"
format="xdp"
target="http://www.example.org"
textEncoding="UTF-16"
xdpContent="pdf datasets template"/>
</event>
</field>
Submitting a form and saving a form are similar in that they convert the Template/Form/Data DOM into an
XML or PDF representation, but they differ in the level of checking done. Saving a form does not involve
any validation or other checks because users may save forms at various stages of completion. Users do not
expect to see error reports and warnings during such saves.
Content Interchange
The
submit
syntax is intended to support most XML-based content interchanges. It does so by specifying
what types of content are submitted to the server, how content should be packaged (
format
,
embedPDF
and
xdpContent
) and how the content should be encoded (
textEncoding
).
The behavior of a
submit
element differs depending on other properties in the submitting event. That is,
submission may invoke any of the following behaviors:
●
Client submits the specified content to the server. The server executes scripts flagged for execution on
the server or on both the server and the client.
Client submits the specified content with the expectation that the server will perform the script and
return a result. The server performs the script and returns the result in its response to the HTTP POST.
●
The factors that influence submission behavior include the following:
Factor
Event trigger
Explanation
Submission may differ for an event triggered by user interaction, as
opposed to an event activated by some other trigger. User-triggered
events include:
enter
,
exit
,
mouseEnter
,
mouseExit
,
change
,
click
,
mouseUp
, and
mouseDown
.
Submission may differ, depending on whether a script is included in
the event and on the value of the script’s
runAt
attribute. The
runAt
attribute specifies where the script should be executed.
Script