Turn operational records into a view you can act on.

01 / REPORTING

Define a view of the relevant work

Saved views describe a repeatable way to inspect supported record, process, task or incident sources. Choose the source and fields that answer the question, then apply filters and sorting. Where the report supports grouping and aggregation, use them to summarize the selected information.

A useful report starts with a precise definition. Decide which records belong in the result and what a count or aggregate represents. A task count, for example, is not automatically a measure of effort or business value. The data and filter choices determine what the result means.

02 / REPORTING

Compose a dashboard for a particular responsibility

Supported dashboard widgets include KPI summaries, tables, bar, line and donut charts. Use a table when people need to inspect individual items, a KPI for a defined aggregate and a chart when the grouping makes comparison easier. Combine views that help the intended audience decide what to do next.

The illustrative composition below names supported presentations rather than inventing live customer performance. In your evaluation, configure a dashboard with representative records and check both the detailed rows and the summarized values. Confirm that the chart describes the same data selection as its source.

03 / REPORTING

Keep reporting inside the access boundary

Reporting respects the relevant application and organization authorization. A saved view or dashboard is not a way to obtain data outside the user’s effective access. CSV export provides a portable result for permitted data; it should be handled according to the organization’s own information policies after download.

Evaluate reporting with a scoped user as well as an administrator. Check that filtering, grouping and export produce the intended result, then review how the view relates to the work queue or record workspace. Reports are most useful when a person can understand the underlying work and its current state.

• Choose a supported source and define the question.
• Check filters, sorting and aggregate meaning.
• Match the widget to the decision it supports.
• Verify scoped access and the exported result.