Templates & autofill
Chapter 02 · 11 articles · 58 min total
- Fields & value sources
A field is one value a template produces. Its inputs say where the value comes from: a question, the document, a fixed text, the case, or the delivery that brought the file. Its outputs say what stamps on the page, and the field type shapes both.
- Placing fields on the page
Placement is exact and deterministic: you set a field's position, size, and page on the canvas, and autofill stamps the value at that same spot every run.
- Build from a completed example
Two shortcuts build the template fields for you. A PDF with its own form fields lists them in a Detected fields panel. A flat form and a filled copy let the app find the values, name the fields, and place the write zones, and more copies teach it.
- AI extraction & instructions
AI extraction reads each file and returns one value for every extracted input you define, and only those. A field can define more than one, each with its own rule. When a value comes back wrong, add an instruction to steer the next run.
- Computed expressions
A computed output derives a value with a deterministic JSON expression that re-evaluates live in the case detail and again at document generation, with $today and $now keeping date math current.
- Field bindings
Bindings stamp values from outside the case (today's date, or your company profile) onto generated output at fill time; they resolve at generation and are never stored in case data. Values that arrived with the file are not bindings: those are delivery inputs.
- Combining & reflowing documents
Source tabs in the document bar assemble a template's output from workspace documents and blank pages. Document reflows locates moving fields when layouts shift.
- 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.
- Batch & quick autofill
Batch templates fill one row-repeating document against many cases at once. An upload run from the editor fills a template against a file you drop in. Both reuse the standard single-case fill engine.
- Run autofill
Open a file and click Run a template, or pick Run a template on this file in a Documents row menu. The run screen covers the case: pick the template in the list beside it, check the file it picked, and click Run. The finished PDF or Word document lands as a row in the case Documents list, tagged with the template Output category.
- Bring cases up to date after a template change
When you change a template, the cases it already ran on keep the data and documents from the earlier version. Press Review cases after saving, select the cases, choose what to update on the bar, and confirm in the chat. Up to 100 cases run at once.
