Output naming & behavior
A template can define an output filename pattern with {token} placeholders; generated PDFs save to the case Documents section under Files Generated, tagged with the template output category and named by that pattern.
How filename patterns work
The pattern is a string with {token} placeholders. At autofill time each placeholder is replaced with its resolved value.
The four built-in tokens:
{template}: the template's name{id}: the case identifier{date}: today's date (YYYY-MM-DD){timestamp}: full Unix-millisecond timestamp
Plus any of this template's field IDs as a token. The field ID is the stable snake-case key the field stores under, usually a lowercased display name with underscores. A field named Vendor Name has the ID vendor_name, so the token is {vendor_name}. Spaces and capitalization don't carry over: {Vendor Name} won't resolve.
Output file name (like the output category) appears only on templates that generate a file: those with at least one write zone. An extraction-only template has no output to name.
What happens after autofill runs
When autofill produces a PDF, it's saved to the case's Documents section under Files Generated, tagged with the template's output category, named per the pattern above, and recorded in the activity timeline. The output is a real, permanent file on the case, not a temporary download. A Generate <template> row in Files Generated produces the same output without starting from a received file.
Received and uploaded files live in Files Received; generated ones in Files Generated, distinguished by the output category chip. Each row shows the filename, the category chip, and the timestamp. Click any output to preview or download. Remove one via the case's Edit mode (or the row's delete action), or re-run autofill to generate a fresh copy alongside the existing one.
How fields land in the output
The renderer takes one of two branches per field. Render mode is binary:
- AcroForm fill: write into a PDF form field, either reusing one that exists in the source PDF (
fill_existing_pdf_field) or creating a new AcroForm field at the placement coordinates (create_pdf_field). Both enum values belong to this branch. - Coordinate stamp: the fall-through when no AcroForm match is possible. The value is stamped as plain text at the placement coordinates.
Coordinate-stamped values land at their authored coordinates. Templates with Document reflows enabled (in the template name dropdown) relocate write zones at fill time to follow the document's content. AcroForm-named fields are placed by name and never move.