Output behavior and naming
Generated outputs are saved to the case Outputs section, named according to the template filename pattern, and downloadable individually.
Last updated
Generated outputs are saved to the case Outputs section, named according to the template filename pattern, and downloadable individually.
What you need
- A case with at least one generated output
What happens after autofill runs
When autofill produces a PDF:
- The PDF is saved to the case's Outputs section.
- The filename follows the template's output naming pattern.
- The activity timeline records the run.
The output is a real file on the case — it's part of the permanent record, not a temporary download.
Where outputs live
Open any case and find the Outputs section. Every generated PDF is listed with:
- The output filename
- The template that produced it
- The user who ran autofill
- The timestamp
Click any output to preview or download. Use the case's Edit mode to remove an output, 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:
- AcroForm fill — write into a PDF form field, either by reusing one that already exists in the source PDF (
fill_existing_pdf_field) or by creating a new AcroForm field at the placement coordinates (create_pdf_field). Both enum values belong to this branch. - Coordinate stamp — fall-through when no AcroForm match is possible: the value is stamped as plain text at the placement coordinates.
These are the only two render branches. Render mode is binary.