Glossary
A quick reference for the terms used throughout this manual.
| Term | Meaning |
|---|---|
| Report | A Qlik-powered email built from objects, text, and attachments, sent on a schedule or on demand. |
| Execution (Run) | A single instance of a report being generated and sent. |
| Trigger | What starts a report: a time schedule, a Qlik task reload, or another report finishing. |
| Burst / Cycle | Sending one tailored copy of a report per distinct value of a chosen field (the cycle field). |
| Section | A group of report elements that only appears when a condition is met. |
| Cell | A single element on the report canvas - a Qlik object, text, image, or current selections. |
| Template | A reusable Excel workbook that fills with live data when a report runs. |
| Binding | The link between a template element and the Qlik object or token that fills it. |
| Mail profile | The email (SMTP) configuration used to send. There is a default for the installation; a report can use its own. |
| Recipient | A person in the shared registry who can receive reports and alerts. |
| Recipient group | A named set of recipients you can address as one. |
| Alert | An automatic email sent when a Qlik task reloads or a report run finishes. |
| Data destination | An external SQL database that report data can be exported to. |
| Preload | Opening the Qlik app and applying filters before capturing data - slower, but more reliable. |
| Repository | KPImailer’s catalogue of published Qlik apps synced from your servers. |
| Role | A named set of permissions (e.g. view, manage, run on a given area) assigned to user accounts. KPImailer ships User, Superuser, and Admin; administrators can also create custom roles. |
| Background job | A scheduled task running inside KPImailer - either a report’s own schedule or a system maintenance task like log cleanup or database backup. |
| API key | A scoped credential that lets an external script or monitoring tool call specific KPImailer endpoints without a personal login. |