The Output service merges data with a form design, created in Designer, and generates the output in various formats. Data is provided as a series of records. Records represent an XML element that stores a set of form data values for merging with a form design. You can have multiple records to represent multiple groups of related data to merge with a form design. The output is created as an output stream that can be sent to a network printer, local printer, email attachment, or saved as a PDF document. The service is useful for processes that merge large sets of data to generate output, which is typical when providing on-demand document-generation services.

For example, use the generatePrintedOutput operation operation to merge ten records with a form design to generate an output format for each record. The form design is saved in an application to maximize portability. The records are located within an XML data source. Then, using the sendToPrinter operation operation, you can send each output to a printer.

Note: If you process large batches of records or input files, ensure that the Default Document Disposal Timeout value in administration console is set high enough. In administration console, select Settings > Core System Settings > Configuration. (See Core System Settings Help .)

When you merge a form design with data, the Output service can generate these output formats:

  • A PDF or PDF/A document output as PDF files.

  • Adobe PostScript

  • Printer Control Language (PCL)

  • Zebra Programming Language (ZPL)

  • Datamax Printer Language (DPL)

  • Intermec Printer Language (IPL)

  • TEC Printer Command Language (TPCL)

Use the OutputIVS sample to test your form designs. Testing the form design is useful for troubleshooting the form design and for accessing the generated output.

The Output service can send output to a printer by using common printer protocols. You can use default XDC files to specify printer settings or create custom XDC files in XDC Editor. The form designs, data files, and XDC files that are used can be stored in various locations to meet your requirements. The locations include an application, the repository in AEM forms Server, the HTTP location, a network location, or the local file system.

In addition, you can flatten an interactive PDF form. The process of flattening a PDF document converts an interactive PDF document to a non-interactive PDF document. When you flatten a PDF document, users cannot modify form fields in the PDF document. Typically, you flatten a PDF document for archiving or printing. However, signature fields on the PDF can remain interactive, depending on the operation you use and how you configure properties in the operation.

To improve performance, use Output operations in short-lived processes when you use Open Type fonts for PCL. See AEM forms XDC Editor Help .

For information about using the Output service, see Services Reference for AEM forms .

// Ethnio survey code removed