You can create forms with Paper Forms Barcodes using Designer. However,
they can only be viewed using the Acrobat Standard or Professional,
unless Reader Extensions are enabled. This situation may be evolving, as
usage right signatures are deprecated in PDF 2.0.
I have a form that is bound to a schema that has a definition like
The problem is that when the data is exported using
Acrobat XI's Export Data (as XML) option, the attributes (which are not
bound), are included in the output, i.e.Which causes issue when validating the schema, using
XMLSpy. The output I expect (and need is this):Is there a
way to accomplish this?
I'm not sure what's causing this strange functionality. I can tell you
that both the XSD and XSL are stored as packets in the XDP part of the
PDF. You can use a third party tool such as iText RUPS to view this
information (Designer's XML view does not always represent what is
stored in the PDF).
If you are looking for a turnkey solution, then the products you mention
will work. However, if you are willing to build some components
yourself, you can accomplish most of what you want without cost. Without
reader extensions you cannot save a filled PDF, however, you can submit
your XML to a server. That same XML can be used to be imported into a
PDF, using a "turncoat" XDP.
I'm afraid the show / hide approach may be your only other option.
LiveCycle is template based, not page based. This is a key feature of
the tool as it allows content to dynamically flow over multiple pages
according to the content requirements.
Assuming that you only want the report to be printed, you can employ the
solution in the blog below:Multiple Top Level Subforms Essentially you
will be authoring two "forms", one for interactive (Acrobat) use, and
another or printing.
I am not familiar enough with AcroForms to give you a similar approach,
but LiveCycle is XML based. You can easily export XML from one form to
feed another. This can be done seamlessly if the forms fields have the
same name, otherwise you will need to add a mapping layer (XSLT).
Q1) LiveCycle uses an XML based technology to build forms (called XFA),
while Acroforms is an extension of the core PDF standard. XFA has more
features than Acroforms at this time. For your purposes, either will
work.Q2) I believe the Import / Export restriction applies equally to
Acroforms and XFA forms. Using Acrobat lifts these restrictions.Q3) ES4
is the last version of LiveCycle. The new product is called AEM. You can
download a trial using these instructions:LiveCycle Blog: AEM Forms