Ad Hoc Report Builder

Report Appearance Options

Report Name
Allows you to specify a meaningful name (up to 50 characters) for the report. This name appears in the ad hoc reports list and in the list of available reports for subscriptions (if the report has been published).
Layout
Allows you to specify one of the following three layouts for the report:
  • Simple Table — basic, list-style reports displaying a single row of fields. Columns can be rearranged by dragging fields left and right. Charts are not supported. For an example of this report layout, see "Recordings From a Particular Area Code" in the Ad Hoc Reports section of the NICE Uptivity Reports Reference Guide.
  • Summary Table — provides for nested, collapsible subcategories or groupings. Column fields can be dragged left and right to rearrange. Rows can be dragged up and down to regroup data. Lower fields are nested within higher fields. Bar and pie charts are supported. For an example of this report layout, see "QA Score in Relation to Content Library Items" in the Ad Hoc Reports section of the NICE Uptivity Reports Reference Guide.
  • Matrix Table — provides for measuring one or more pieces of information across a period of time. Fields controlling the information to be measured and the time range are displayed in the Columns area, and are limited to one field in each area per report. Fields that control grouping of that information are displayed in the Rows area. Multiple fields can be dragged, dropped, and rearranged to provide for different logical groupings of the information. Bar, pie and line charts are supported. Line charts illustrating large data sets may become difficult to read and use. For an example of this report layout, see "Average QA Score by Evaluator" in the Ad Hoc Reports section of the NICE Uptivity Reports Reference Guide.
Reporting Format
Allows you to specify one of the following two formats for the report:
  • RDL — works with Microsoft SQL Reporting Services and provides export formats of PDF, Microsoft Word, or Microsoft Excel files. Charts are simply laid out, displaying all the information in a non-interactive way. Large reports with pagination can be created. Categories and groupings in RDL reports are expanded by default. However, RDL reports do not support drill-down functionality.
  • HTML — provides for reports and charts that are interactive. Information can be displayed on mouse-over, and clicking bars within a chart allows you to drill down into subcategories and see more detailed results. If there are multiple detail levels, clicking through will loop back to the top level. However, this format cannot be exported, does not support pagination, and is limited to displaying only 1000 results. HTML works best as a basic data preview, or for reports that will only be viewed online. Categories and groupings in HTML reports are collapsed by default. For an example of this report layout, see "QA Score in Relation to Content Library Items" in the Ad Hoc Reports section of the NICE Uptivity Reports Reference Guide.
Description
Allows you to provide a brief description (up to 200 characters) for the report. This description appears in the ad hoc reports list and its content is included when you filter that page (see Ad Hoc Reports List).

Fields

The Fields section provides access to the database fields you use to build reports. The categories and specific fields vary depending on the type of report. In some cases, field labels in this section are affected by your system's terminology settings (see Terminology Settings).

Field Categories for NICE Uptivity Speech Analytics Reports

Field Categories for Call Recording Reports

Field Categories for Quality Assurance Reports

Quality Assurance (QA) data available for ad hoc reporting includes both QA form data and completed QA data. It is important not to mix these data types. Mixing them can yield inaccurate, inconsistent, or unexpected results. In general, QA reporting can serve two purposes:

  • Reporting on available QA forms (QA forms, sections, questions, and available responses).
  • Reporting on completed QA evaluations, which is what the vast majority of the printable reports provide

Using a single interface to create reports for both purposes is challenging because this data has different meanings and is linked together depending on context. To help ensure accurate reporting, keep the following in mind when building reports:

  • Use categories beginning with "QA" to report on available QA forms (for example, a listing of forms that include a specific question)
  • Use categories beginning with "Completed QA" to report on QA evaluations (for example, a listing of evaluations performed by a specific evaluator)

Related Tasks