Document Templates
A document template is a reusable layout that the Generate Document action turns into a print-ready PDF, filling in your process data as it goes. One template produces a correct, on-brand document for every instance - a contract, an invoice, a report.
What you can put in a template
- Your process data - any field from the process appears in the document, referenced by its name.
- Formatted and rich text - headings, lists, tables, and rich-text fields render as styled content.
- Images and logos - including images carried by the process (for example a signature or a customer logo).
- Page layout - headers, footers, page numbers, and A4 print formatting.
The result is a PDF, ready to email, archive, or store on a record.
How a template is managed
A template is a file, not a setting pasted into a field - so it is uploaded and versioned like any other file:
- Upload the template.
- Bind it: the Generate Document step points its template input at the uploaded file and writes the rendered PDF to its document output.
- Revise by uploading a new version. Templates are pinned per process version, so instances already running keep rendering with the template they started on.
Note
Authoring the template layout itself (the HTML and the data placeholders) is a design-time task handled with the metamorphOS template tooling. This page covers what templates do and how they fit into a process.
Templating vs document templates
Don’t confuse the two:
- Templating -
${FieldName}expressions inside text fields (email subjects/bodies, instance names, connector parameters). - Document templates (this page) - full layouts rendered to a PDF by Generate Document.
Related
- Generate Document - the action that renders the template.
- Run Script - shape or compute values before rendering.
Last updated on