Datasources & building

Building a report means deciding what data it draws on and how that data is presented. TraceUnified reports are built on datasources — live views of your records — so a report always reflects the current state rather than a stale extract.

Datasources

A report draws from one or more datasources, each exposing a kind of record: requirements, test cases, risks, SBOM components, traceability links, releases, review sessions, and compliance data, among others. Because these are live sources rather than copied data, a report run today shows today’s records. The datasource you choose determines the fields available to the report.

Selecting fields and filters

From a datasource you select the fields to include — the columns of the report — and apply filters to narrow it to what matters: a particular project, a status, a risk level, a date range. This is how a broad source becomes a focused document — “approved requirements verified by passing tests,” say, rather than every requirement that exists.

Querying across the data

Behind the scenes a query engine assembles the report from your selections, joining and filtering the underlying records. For traceability-style reports, this is what lets a single report relate one kind of item to another — requirements to their tests, risks to their controls — pulling the connections from the thread rather than from a manual cross-reference.

Layout and saved views

You arrange how the report presents its data, and you can save the configuration as a saved view so a particular cut of a report can be recalled without rebuilding it. A saved view captures the datasource, fields, filters, and layout together — the recipe for a report you’ll want again.

From definition to run

Building defines the report; running it produces the document with current data and your chosen parameters. That step — running on demand and on a schedule — is covered next in Running & scheduling.