XFA Specification
New XFA Template Features
967
Noninteractive fields, version 2.1
Fields may be designated to be non-interactive. Such fields participate in data binding, but after that they
are treated as
draw
elements.
Automation and Web-Related Interactions
URL-encoded option for submit, version 2.4
Data submitted to a host can be URL-encoded in a consistent way. For more information see the
“Template
Specification” on page 418.
Choice-list enter and exit events pair up, version 2.4
The event model for choice lists is modified to ensure enter and exit events always pair up.
See “Field
Events” on page 308.
Manifests as scripting variables, version 2.4
Manifests (sets of objects for signing or other processing) can be specified via scripting variables. For more
information see the
“Template Specification” on page 418.
Support for Web Services, version 2.1
XFA template now supports Web Services that implement 'doc-literal' SOAP operations over HTTP. In such
operations, the Web Service's WSDL defines SOAP binding operations with 'document' style, and SOAP
messages with 'literal' encoding. This capability has added properties to the elements
xfa:datasets
,
dd:dataDescription
, and
xfa:event
.
Submission of form parts to a target URI, version 2.1
An event may include a submission property. When such an event is activated, the submission property
causes the form (all or part) to be submitted to a target URI. The submission property indicate the parts,
the packaging, the encoding, and the destination URI.
Subforms may include calculations, verison 2.1
Subforms may include calculations, which simplies declaring a calculation influenced by multiple
child-containers within a subform.
Calculations may specify override conditions, version 2.1
Calculate elements may include override the
override
attribute, which specifies whether the calculation
may be executed or not. If allowed to execute, the
override
attribute specifies whether the user is
allowed to override the calculated value.
Scripts specify whether they should be executed on the client, server or both, version 2.1
Scripts may now specify whether they should be executed on an XFA processing application that thinks it
is a client, one that thinks it is a server, or both.
Previously, there was no such distinction.
Event for populating drop-down choice list widgets, version 2.2
Fields containing drop-down choice lists may have a new event, which is triggered when the user clicks on
the down-arrow symbol. This new event is intended to house scripts that add choices to the choice list.