Output naming & behavior
A template can define an output filename pattern with {token} placeholders; generated PDFs land as their own row in the case Documents list, 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 fields, named after the field itself. Each token is a slug of the field's display name: lowercased, with spaces turned into underscores. A field named Vendor Name gives the token {vendor_name}. Capitalization and spaces don't carry over ({Vendor Name} won't resolve), so build patterns by clicking the token chips rather than typing them by hand.
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.
Sending output to Google Drive
Below the file name pattern, Drive folder names a folder in your connected Google Drive. When set, every document this template generates is also uploaded there. The app creates the folder on the first run; after that you can move or rename it anywhere in your Drive and uploads keep following it. An optional Folder path builds subfolders inside it from the same tokens as the file name, so id/Bids files each case's output under its own job folder. Leave the folder empty for no Drive copy. If the file name would repeat every run, a note under the field reminds you that copies stack up in Drive; add the timestamp token to make each run unique.
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.
Every file on a case (received and generated) appears as one row in the case's Documents list, newest first (a sort toggle flips to oldest first). Each row shows the filename, its category chip, and a subline saying when it arrived or which template generated it. Click the filename to preview it; expand the row to run a template on it, the ones built on that document first. The values a file put on the case live in the case-data card and in the Activity timeline's extraction entry, which lists each extracted field and shows what changed on a re-extract. Remove a file from the row's overflow menu, or re-run a template 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:
- Fill existing AcroForm field: write into a matching PDF form field already present in the source PDF (
fill_existing_pdf_field). - Create AcroForm field: create a new PDF form field at the placement coordinates (
create_pdf_field). Coordinate overlays only happen inside this branch for rotated-page text and image/signature values; there is no standalone text-stamping mode.
Created fields 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.