The Template library holds reusable document and email templates for your municipality. It is separate from Service templates, which are starting points for a complete service process.
Choose the right kind of template (link to section)
| Template | Purpose |
|---|---|
| Service template | Start a service with a reusable form and route. |
| Document template | Prepare a document using case information. |
| Email template | Reuse the body of a notification. |
Open Template library from the sidebar to manage documents and emails when your role permits it.
Create a document (link to section)
A document generation step can use a library document or a custom document. The visual editor supports headings, formatted text, lists, tables, alignment, and inserted case values.
For a fillable PDF, upload the form and map its fields to the intended answers or case values. Review a generated sample before publishing the service.
Common case values include the case reference, status, applicant, email, and submission date. A question uses its own identifier, such as {{event_name}}.
Use fictional information when checking templates. A sample document should help you verify layout and mappings without containing a resident’s details.
Reuse an email body (link to section)
Choose or create an email template on a notification step. The reusable template supplies the body; the notification step keeps its own subject.
Check both the subject and body in the service. Choosing a different library body does not replace the step’s subject.
Understand service copies (link to section)
Selecting a library template copies it into the service draft. The copy records where it came from, but later library edits do not alter that service copy.
Deleting a library template also does not change published service versions or cases already using their saved configuration. Update and review the relevant service draft when an existing service needs new wording or layout.
Check the result (link to section)
Before publication, confirm that each placeholder points to an available value and that each PDF mapping names a real field. Review the generated output for missing answers, awkward page breaks, and long text.
Generated case documents may need time to prepare. A failed document needs staff attention; the case itself does not wait for document generation to finish.