How can we help you?

Advanced documentation search

OpenXML Package Manifest Reference

Product: FeraRender Topic: PDF and DOCX Versions: Applies to all documented versions Current
Written by user
Updated

Describe the XML manifest FeraRender uses to assemble a DOCX package.

Audience: Advanced template authors and developers
Recommended visibility: Public

Overview

Describe the XML manifest FeraRender uses to assemble a DOCX package. 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 root element contains file entries.
  • folder and name determine the ZIP part path.
  • transform=true runs XSLT against render XML.
  • transform=base64 decodes binary content.
  • literal entries are copied as XML.
  • Every valid DOCX needs content types, package relationships, document XML, and document relationships.

Example

<root version="1">
  <file name="[Content_Types].xml" transform="false">...</file>
  <file folder="_rels" name=".rels" transform="false">...</file>
  <file folder="word" name="document.xml" transform="true">
    <xsl:stylesheet version="1.0"
      xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main">
      ...
    </xsl:stylesheet>
  </file>
  <file folder="word/_rels" name="document.xml.rels"
    transform="false">...</file>
</root>

Replace bracketed values with values issued for the target environment. Never place production tokens, API keys, or client data in screenshots or public examples.

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

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.