Adobe LiveCycle Implementation Considerations

Designing and Implementing Business Process Models : Implementing Content Service Platform for BPM : Implementing E-forms : Adobe LiveCycle Implementation Considerations

Creating XFA-Compliant Forms with LiveCycle Designer

Adobe Design Time Considerations for Task Applications

Using an XML Schema as a Template Source

Making Adobe E-form Instances Available at Run Time

Using LiveCycle E-forms with Adobe Reader

Using Traditional PDF Forms Created with Adobe Acrobat

Using Digital Signatures with Adobe LiveCycle E-forms

The webMethods product suite supports interactive Adobe forms that comply with XML Forms Architecture (XFA). Interactive XML forms can be deployed as PDF or as an XML Data Package (XDP). An XDP file is an XML file that packages a PDF file in XML, along with XML form and template data.

The webMethods product suite requires that the form elements and data be presented in XDP format to satisfy both its design time and run-time requirements.

Adobe Forms come in two categories:

XFA-compliant, XML-based forms created, modified, and managed with Adobe LiveCycle Designer. These e-forms are the primary implementation for use with the webMethods product suite.

Acrobat forms created, modified, and managed with Adobe Acrobat. These forms must be imported into Adobe LiveCycle Designer before they can be used with webMethods product suite. For more information, see Using Traditional PDF Forms Created with Adobe Acrobat.

Contact Support | Community | Feedback