Reports and exports
Six report types rendered from the same queries as the on-screen tables, as CSV or PDF, on daily/weekly/monthly schedules, delivered as a download link with at-most-once-per-window guarantees.
Audit packs on a schedule
ITAM work is recurring: a monthly license position for the software asset manager, a weekly patch-posture pack for security, a quarterly financial summary for finance. The Reports tab in Inventory turns each of those into a definition that runs on its own and delivers itself, so nobody has to remember to log in and export a table.
The six report types
| Type | Contents | Typical audience |
|---|---|---|
| Hosts inventory | Every asset with its identity, lifecycle, presence and posture | Asset register, audit evidence |
| Software usage | Products with their measured usage and adoption | Renewal and tool-rationalization decisions |
| License position | Entitled versus consumed per license, with the compliance position | Software asset management |
| True-up | The full true-up table, including cost-to-cure, plus a summary section | Vendor audit preparation, budgeting |
| Patch posture | Worst offenders, plus fleet counts by bucket | Security review |
| Financials summary | Totals by currency and key financial figures | Finance, refresh planning |
A report and the screen cannot disagree. Every report is rendered from the same query that backs the equivalent on-screen table — no report re-implements a query of its own. Given identical filters, a report matches the table row for row by construction, not by discipline. This is what makes an exported pack defensible.
Multi-section reports
Some reports carry more than one table. Where they do, the first section is the primary table — the one that mirrors the UI — and later sections add summary context. In Patch posture the offenders table leads and the fleet counts follow; in True-up the per-license table leads and the summary follows.
Formats
| Format | Details |
|---|---|
| CSV | RFC-4180 quoting throughout, so product names containing commas or quotes survive the trip into a spreadsheet intact. Multi-section reports separate sections with a blank line and a title row, and remain valid CSV. |
| A4 landscape, with your organization name, the report name and the generation date in the header, and dense tables in the spirit of the Inventory design system. Rendered server-side — no headless browser, no external service. |
Scheduling
A definition carries a name, a type, its parameters (such as a group scope or a posture filter), a format, a schedule and its recipients.
| Schedule | Anchor |
|---|---|
| Daily | An hour of the day |
| Weekly | A day of the week (Monday through Sunday) and an hour |
| Monthly | A day of the month between 1 and 28, and an hour |
Anchors run in your organization's timezone. The monthly anchor is capped at 28 deliberately: an anchor of 30 would silently skip February, so it is rejected at validation rather than quietly coerced into something you did not ask for.
Three scheduling guarantees
- At most once per window. A daily report fires once for its day no matter how many times the scheduler runs, and this holds across multiple platform nodes.
- A missed window fires late rather than being skipped. If the platform was restarting when your report was due, it runs when the platform is back. The window guarantee still applies, so catching up can never double-deliver.
- A new definition does not fire immediately. Creating a monthly report on the 20th does not run it on the spot; it starts with the next window. This reads as correct rather than as a bug.
Run now is always available for an ad-hoc run, and does not affect the schedule.
Recipients and delivery
Recipients are users of your own organization, chosen from a picker. They are validated when you save the definition, so an invalid or cross-organization recipient is rejected there and then rather than failing silently at delivery time. Arbitrary external email addresses are not supported in this release.
Delivery is a notification email containing a download link, not an attachment. This is deliberate, and it is a tenancy decision as much as a technical one: an attachment leaves your organization's boundary the moment it is sent and can be forwarded anywhere, whereas a link keeps the artifact behind VerOps authentication. Downloading requires inventory.view and membership of the organization that owns the report.
Run history and retention
Each definition keeps a run history — when it started and finished, its status, and a download link for the artifact. Two behaviours worth knowing:
- A failed run is recorded, and never blocks the next one. The failure is written to the run with its error, and the following window proceeds normally. One broken definition cannot stall your reporting.
- Runs and their artifacts are retained for 90 days, then swept automatically. Archive anything you need to keep beyond that outside VerOps.
Getting started
- Open Inventory → Reports and create a definition — start with True-up as CSV, monthly.
- Use Run now and download the result to confirm the contents and scope are what you expected.
- Add recipients and enable it.
- Add a Patch posture PDF on a weekly schedule for your security review, and a monthly Financials summary for finance.
VerOps does not offer a custom report builder, XLSX output or BI-connector export in this release — the six types above, in CSV or PDF, are the supported set.