This Quick Start describes how to use the Forms to render an interactive PDF form with pre-filled data. For more information about the Forms service, see LiveCycle ES2 Services.
Using the Forms service, a form design can be merged with XML data, and rendered as a pre-filled, interactive PDF form. For example, users log in to a web-based system and open an interactive purchase form using Adobe Acrobat version 8.0 or later. The form is pre-filled with shipping, contact, and purchase order information. Users fill in the remaining purchase order details and save the PDF form.
An application, named poPDFApp, implements this service for the organization. The form design, named purchaseOrder.xdp, is available as part of the application. An XML file, which contains the shipping, contact, and purchase order information, is merged with the form design to render the interactive PDF form. The resulting PDF form is saved to the network location specified by the user, such as \\user1\POForm.pdf. Users retrieve the PDF form from the network location, fill, save, and send it electronically.
The following assets are in the poPDFApp application:
The process diagram for the createPOForm process looks like the following illustration:
The following XML file provides the shipping information to pre-fill the rendered PDF form:
<?xml version="1.0" encoding="UTF-8"?> <poform1> <txtPONum>8745236985</txtPONum> <dtmDate>2004-02-08</dtmDate> <txtShipCompanyName>Fin@nce Incorporated</txtOrderedByCompanyName> <txtShipAddress>123, Any Blvd.</txtOrderedByAddress> <txtShipCity>Any City</txtOrderedByCity> <txtShipStateProv>Any State</txtOrderedByStateProv> <txtShipZipCode>12345</txtOrderedByZipCode> <txtShipCountry>Any Country</txtOrderedByCountry> <txtShipPhone>(123) 456-7890</txtOrderedByPhone> <txtShipFax>(123) 456-7899</txtOrderedByFax> <txtShipContactName>Akira Tanaka</txtOrderedByContactName> </poform1>
For the renderPDFOrm operation, the following properties are configured to generate an interactive PDF form:
For the Write Document operation, the following properties are configured to save the interactive PDF form to a network location:
Instead of writing the PDF form to a network location, consider sending the PDF form (as a byte stream) to a Java servlet. The Java servlet can display the form to a web page. (See Creating Web Applications that Renders Forms in Programming with LiveCycle ES2.)
Consider using the processFormSubmission operation in a separate process to handle the submission of data from a rendered PDF form. (See Handling a form submission as XML in Creating Processes Using LiveCycle Workbench ES2.)
Use the Reader Extensions service to apply usage rights to the PDF form when users use Adobe Reader to fill the form. (See Apply Usage Rights in Creating Processes Using LiveCycle Workbench ES2.)
Any references to company names, company logos and user names in sample material or sample forms included in this documentation and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.