Output naming & behavior
A template can define an output filename pattern with {token} placeholders. Generated PDFs land in the case Documents list, tagged with the template output category and named by that pattern.
The pattern is a text string containing placeholders. The app evaluates these tokens when the template runs and generates a file.
Finding output settings
Output settings live in template settings, in the Output section. Click the template's name in the editor toolbar, at the top-left of the canvas, and the settings open over the editor. Back to template returns you to it.
The Output file name field appears below Output category. It only shows on templates that generate a file. A template generates a file if it has at least one write zone. A write zone creates a new form field at those coordinates or fills an existing one. An extraction-only template produces no new file, so it has no output to name.
The Output category field always shows. It appears disabled with the prompt Add a field output to generate a file you can categorize. when the template generates no file.
Building a filename pattern
You build a pattern by clicking the token chips or typing them.
The four built-in tokens are:
{template}: the template's name{id}: the case identifier{date}: today's UTC date asYYYY-MM-DD{timestamp}: a full Unix-millisecond timestamp
You can use any template field as a token. The token is a slug of the field's name. A field named Vendor Name gives the chip {vendor_name}. Token matching is case-insensitive, so {Vendor_Name} works. Renaming a field does not change its assigned token. The identifier field acts as an alias. Typing its name normalizes to {id}.
Changes in template settings save to the editor draft when you click away. Template settings have no Save of their own: you must click Save in the header to persist them.
How the app formats names
Omit the .pdf extension from your pattern. The editor strips it. The app appends .pdf automatically when it saves the output. If you leave the pattern empty, the app defaults to <Template_Name>_<timestamp>.pdf.
The app sanitizes token values before using them. Any character other than a letter, digit, dot, hyphen, or underscore becomes an underscore, and repeated underscores collapse to one. Values are capped at 80 characters. A client name of Acme Supply Co. becomes Acme_Supply_Co..
Field tokens read the case as the run leaves it, so a value the run reads from the document names the file it fills. Empty fields produce empty strings in the filename. If a field has no value on the case and the run reads none, its token survives literally in the output name.
If a generated filename matches an existing file on the case, or a file that was deleted from it, the app appends a number like (1). It never overwrites previous outputs. If your pattern repeats every run, a note warns you that copies stack up. Add the {timestamp} token to make each run unique.
Sending copies to Google Drive
You can send copies of generated files to a connected Google Drive. Type a destination in Drive folder. Leave it empty to keep no Drive copy.
The app creates the folder on its first run. After that, you can move or rename the folder anywhere in your Drive. The app tracks the folder ID and keeps uploading there. If you rename the folder inside the app, it abandons that folder and creates a fresh one in Drive.
Once you enter a Drive folder, the Folder path field appears. It accepts the same tokens to build subfolders. Type id/Invoices to put each case's output in its own job folder. The folder name is capped at 100 characters, and the path at 200.
Drive copies are best-effort. If the Drive connection is missing or fails, the run succeeds and the app keeps the canonical file.
Where generated files go
The app saves generated PDFs in the case Documents console. It tags the output with the template's Output category. If the template has no output category, the generated file stays untagged. The output is a permanent file, not a temporary download.
The console is one flat list of files sorted by date. A toggle switches between newest and oldest first. Each row shows the filename, its category chip, and a subline stating when it arrived and the template used.
Files generated without a source document sit under the Generate from template header. You click Generate on the template row to produce them. The rest sit under Fill from template.
Click a filename to preview it. Expand the row to see templates you can run on it. The overflow menu holds actions like Share, Move to another case..., Start a new case from this file, and Delete. Client portal users see a read-only list with no row expansion.
The app records the generated file in the Activity timeline. Values placed on the case appear in the case data card and the timeline extraction entry. The entry shows what changed compared to the prior run.
Moving fields at fill time
In the Fill section of template settings, the Document reflows toggle lets AI reposition write zones at fill time to follow shifted document content. If you map a field to an existing AcroForm name, the app writes into that exact box and ignores reflows entirely.