Document templates and merge fields
How FlyerOS generates a document from a template and a merge-field registry, with a sensitivity level and a versioned record of every document produced.
Last reviewed
A document in FlyerOS is generated from a template, not written from scratch each time. The template holds the wording and layout; the details are filled in from the system.
Merge fields come from one registry
A template uses merge fields, and every merge field resolves from a single registry of the things FlyerOS knows: a student's name, an aircraft's registration, a course, a date. Because they come from one place, a field means the same thing in every template, and a document cannot quietly contain a stale figure someone typed in.
Sensitivity
A template carries a sensitivity level, so a document that contains personal or commercial detail is handled and shared accordingly rather than treated like a public leaflet.
Every document is a versioned record
When a document is generated it is kept as a record, with the version of the template it used and the data it was built from. So you can always see what a given document said when it was issued, which is what makes a generated document an answer rather than a printout that could have been swapped.
Uploaded documents are separate
This is about documents FlyerOS produces. Files you upload and store are handled separately. See Generating a document.