XFA Specification
Chapter 9, Automation Objects
Events
304
error
The form object is required to have a value that conforms to an input mask. Failure to provide such
a value shall constitute an error. The processing will present an error message, and the form object
is considered invalid. XFA application may skip the remaining validations for the field.
scriptTest
Scripts specified as part of a validation should make no assumptions as to how the processing application
might use the validation results, or when the
validate
element is invoked. In particular, the script should
not attempt to provide feedback to a user or alter the state of the form in any way.
The scriptTest attribute on the
validate
element has three potential values that determine how this
validation test is applied to the form:
disabled
The form object is permitted to have a value that does not conform to the script; that is, the field
can be left with a non-conformant value, and it will not negatively impact the validity of the form.
This attribute value disables this validation test.
warn
The form object is recommended to have a value that conforms to the script. If the user does not
supply such a value, the processing application will present the warning message. The message
must inform the user that the form object is recommended to have a value that conforms to the
script's constraints, and provide two choices:
dismiss — The user understands the form's recommendation and wishes to return to the form, so
that s/he may satisfy this constraint.
override — The user understands the form's recommendation, but has chosen to contravene this
constraint.
error
The form object is required to have a value that conforms to the script. Failure to provide such a
value shall constitute an error. The processing will present an error message, and the form object
is considered invalid.
Events
In XFA templates, scripts may be associated with particular
events.
An event is a particular change of state
in the form. When the particular change of state happens, the actions associated with the event are
automatically invoked. Those actions may be any of the following:
Script. A script property specifies a set of scripted instructions that can perform a variety of actions,
such as transforming the data, changing the presentation of the data, or triggering other events.
See
“Scripting” on page 321.
Execute. An execute property invokes a WSDL web service. Such a service can be used to initate a
complex interaction with a server.
See “Using Web Services” on page 329.
Submit. A submit property invokes an HTTP protocol to send all or part of the form to a server, and in
some cases to accept new data provided by that server.
See “Submitting Data and Other Form Content
to a Server” on page 324.
Sign. A signData property causes a signature handler to create an XML digital signature, as specified in
the signData property.
See “XML Digital Signatures” on page 409.
Home Index Bookmark Pages
Pages: Home Index All Pages