Chapter 4 — Reports(Tutorial example at the end)
Why this chapter matters
Reports help owners and managers see operations in numbers and charts: how busy messaging and workflows are, how many forms were approved, and whether to add people or tune flows. Filter by period and export when the report supports it.
Examples:
- Operations reviews real-time or daily reports weekly to decide on support staffing.
- Finance opens monthly reports and form instance reports at month-end to reconcile signups vs approvals.
- Managers use form pivot analysis to slice survey or application data from different angles.
The left menu Reports section lists multiple sub-reports; each may be licensed separately — without permission the menu hides or the page shows access denied.
| Menu name | Rough purpose |
|---|---|
| Real-time report | Near-live operational or workflow snapshot. |
| Daily report | Statistics and trends aggregated by day. |
| Monthly report | Monthly rollups for month-end reviews. |
| Apps media report | Media / file usage related to apps or workflows. |
| Form instance report | Submission counts, statuses, ranges per form. |
| Form pivot analysis | Cross-tab analysis of form data across dimensions. |
4.1 Typical workflow
- Open Reports in the left menu, then pick a report type.
- Set date range, workflow, form, or other filters on the page.
- If Export exists, download PDF or Excel (when that report implements export).
If numbers do not change after changing filters, confirm you clicked Query / Apply (or similar) and wait for loading to finish.
TutorialExample: reviewing leave, expense, or sales form statistics
When leave, expense, or quote-request forms are collected through forms and flows, managers use Form instance reports for volumes and status by period, and Form pivot analysis when they need cross-tabs — matching “HR attendance stats” or “expense history” style needs in the reference diagrams.
- Report permissions may be separate from menu visibility; ask your administrator if something is missing.
How the product ties together: reporting reads stored form instances and workflow-related data; filters are meaningful when names and fields match what you designed in Chapter 2.