A template says what a report looks like. The data comes new with every call, the template stays. Templates are created in the running system, not at build time: the platform ships system templates, a tenant adapts them, and a person can keep their own.
Subject area
Templates
How a template is built, how CRMS finds it for a request, how it changes through revisions and approvals, which FreeMarker language it speaks, and how templates from a build get into the system.
Topics in this subject area
- 1.How a template is built
Key, output type, scope, edition, language variant, draft and revision: the parts of a template and what a revision holds.
- 2.How CRMS finds the template
The order in which CRMS searches scopes and languages, why only published revisions count, and what the document says about where it came from.
- 3.Life cycle of a revision
From the draft through review to the published revision, plus reject, roll back and retire. Nothing is changed; every step is a new entry in a hash chain.
- 4.Approval chains
Stages per scope, who approves at which stage, the four-eyes principle, what an approval means, and where a project defines its chains.
- 5.The template language
FreeMarker in a sandbox: how a template reads the payload, how numbers and dates are formatted, how assets and SVG graphics get in, and what is locked.
- 6.Templates shipped with a build
Templates that ship with a build get into the system the same way as any other: as a draft, submitted by a platform administrator. Shown with the hub's reports.