Architecture 

The following graphics show you the architecture that is implemented when you create and print a PDF-based form.

 

Creating a Form

The form interface is created separately from the form, which consists of the form context and layout. When you create a form, you must assign it to a form interface. You can assign multiple forms to the same interface, if they use the same data. Form interfaces and forms are stored as separate development objects in the repository. The form description includes the complete form design as a complex description in XML.

Form Output - Runtime

If you use an application to create a form, you generally need to insert application data in the form. The architecture of PDF-based forms is designed to separate the collection of the application data from the definition of the actual form:

 

When you activate the PDF-based form, a function module is generated that encapsulates all properties of the form. When the application program calls the function module, it uses its interface (corresponds to the form interface) to send it the application data. This can be, for example, table data selected previously in the application program. When the generated function module is called, the form description and application data is sent to Adobe document services. These services create the actual form:

●     As a PDF to be processed later by the application or for the preview in Adobe Reader

●     As a PCL, PostScript, or ZPL to be sent to the spool

A function module is available for more precise control of the output.