Document Services and Output Generation
What to know
Document Services include Output (XDP/PDF generation from data), Forms (render PDF forms), Assembler (combine/split/convert PDFs), PDF Generator (convert Office/native files to PDF), Reader Extensions (enable usage rights), and Document Assurance/Signatures. Understand XDP templates and how data (XML) merges with them via Output service. Know DDX (Document Description XML) for Assembler operations.
Output concepts
Know the Output service workflow: template (XDP) + data (XML) → PDF. Understand render options (PDF, print, web), tagged PDF for accessibility, and font embedding. Know how PDF Generator handles native vs PDFBox conversion and the role of watched folders for batch conversion.
Traps
A common trap: Output service requires an XDP template, not a PDF. Another: Assembler operations are defined by DDX, and using the wrong DDX element (e.g., PDFUtility vs Assemble) fails. Questions also test that Reader Extensions apply usage rights to a PDF so Acrobat Reader users can save/comment - this is not encryption. Watch for confusion between Forms service (renders interactive forms) and Output service (merges data into a template).
Rule of thumb
If you need a data-driven PDF from a designed template, use Output + XDP. If you need to combine existing PDFs, use Assembler + DDX.
Worked example
Generate a personalized statement: design an XDP, provide customer XML, invoke Output service with render option PDF and tagged output for accessibility. To merge that statement with a cover page, use Assembler with a DDX Assemble operation.