Templates & Autofill

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.

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.

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 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.

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.

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.

Source tabs in the document bar assemble a template's output from workspace documents, other templates, and blank pages. Document reflows locates moving fields when layouts shift.

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 templates fill one row-repeating document against many cases at once. A Run with your documents… run fills a template against ad-hoc PDFs. Both reuse the standard single-case fill engine.

Open a file, pick a template in the right-side Autofill rail, and click Run Autofill. The finished PDF or Word document lands as a row in the case Documents list, tagged with the template Output category.