Render XML through stored XSLT and an HTML-to-PDF service.

Overview

Render XML through stored XSLT and an HTML-to-PDF service. Document formats have different failure modes. Confirm whether the workflow transforms data, fills an existing form, packages OpenXML, or only converts a file.

Key points

• The stored template is compiled as XSLT.
• Submitted XML is transformed into HTML or page-ready content.
• Attached resources are forwarded to the PDF service.
• Compilation failures identify the template UUID and name.
• Test CSS, fonts, images, and page breaks on the production renderer.

Recommended procedure

1. Choose the exact PDF or DOCX workflow.
2. Validate the source template or file.
3. Submit representative data with the expected response mode.
4. Open the resulting file and verify layout, fonts, fields, and metadata.

Troubleshooting

The PDF is blank or malformed

Validate the transform output or field mapping before blaming the conversion engine.

Fonts or pagination differ

Install required fonts and test with the same conversion engine used in production.

Conversion fails for one file

Open and resave the source DOCX, remove unsupported content, and compare it with a known-good file.

Related documentation

• PDF Form Template Structure
• Inspect PDF Form Fields
• Fill a PDF Form

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.