DragonDocs

DragonDocs merges your records into a Word template and produces a PDF or DOCX. You upload a template with merge fields in it, connect a form to it here, and records on that form are sent across.

This page covers the FormDragon side. Templates, merge fields and the conditions that decide which records become documents are in the DragonDocs documentation.

Connecting a form

Which records become documents

FormDragon sends every saved record on that form, drafts included, with the record’s status attached. It does not decide which ones deserve a document — DragonDocs does, on the template’s Generation tab.

That is deliberate: the conditions live with the templates, so changing a rule means changing one thing in one place. A template with no conditions makes a document from everything it receives, so if you only want approved records, add a condition there: submission.status equals approved.

What the template can use

Every answer arrives in three forms, because templates and conditions want different things:

Plus submission (status, timestamps, who, GPS), form, organization and attachments. Dates arrive as stored; format them in the template.

Write conditions against raw, not fields: a stored value survives somebody renaming an option; a label does not.

Where the document goes

To DragonDocs, and it stays there. Find it in the DragonDocs library, or have DragonDocs email it. On this side, Recent sends shows what left, what DragonDocs said, and the job reference:

• Queued — accepted; the document is being made.
• Skipped — accepted, but the template’s conditions said no. Normal.
• Failed — it did not get through, with the reason.