Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Defining reporting requirements

Updated on April 21, 2021

Consider your reporting requirements early in the planning process. Before introducing a new report, answer the following questions:

Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide
  • Does the report already exist? For information about the reports included with the out-of-the-box application, see Pega Customer Service reports.
  • Who needs the report?
  • When do they need the report?
  • What is the content of the report?
  • Why do they need the report?
  • Where will it be run? Will it be run in the Pega Customer Service application, or using another reporting tool and source?

Determining reporting architecture

Determine which reports you are going to generate from the application, and which you are going to generate using a different reporting tool.

To understand reporting requirements, see Reporting.
  1. Review the description of each application-provided report, identify the expected volume of data, and determine how often you expect to run each report.
  2. Identify other reporting tools at your site.

Reviewing existing reports

The application includes numerous reports. Identify the application-provided reports that meet your business needs.

  1. Log in by using an administrator account. Dev Studio opens.
  2. Click Launch web interfaceInteraction Portal.
  3. Click the My Reports link.
  4. Review each of the reports in the Public categories section.
  5. Determine who needs the report, what it contains, and when and why it is needed.

Identifying key metrics

Identify key metrics early in the planning process so that you can structure your application to generate the required metrics.

  1. Review the list of existing reports with supervisors and managers, sales managers and sales representatives.
  2. Identify any metrics that are already provided by the application.
  3. Identify metrics that are not already provided by the application.
  4. Determine who needs each report, what it contains, and when and why it is needed.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us