---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Create a report definition

# Create a report definition {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can create a new KPI Composer report definition directly from the
relevant artifact in the Data Definition tab. Fill the report definition with the necessary
information for creating a report.

## Before you begin

You have an existing [KPI Composer project](https://servicenow-prod.fluidtopics.net/8bc2IdG13Z_mYSyy0y95pw "KPI Composer is based on projects. Each project in KPI Composer consists of Key Performance Indicator (KPI) trees and the functional and technical definitions of all artifacts within those trees. You can create multiple projects.") with a complete draft of the [KPI tree](https://servicenow-prod.fluidtopics.net/Yl9bA96maXAKm_Eib3E~Wg#design-kpi-tree "In the Analysis tab of KPI Composer, design your KPI tree. Specify your business goals, their associated critical success factors, and the measurement related to those factors. Chart the logical relationship between these factors and the personas who are responsible for them.") in the Analytics tab. You also need technical knowledge of Reporting.

Role required:
sn_kpi_composer.admin or admin to link to an existing report, sn_kpi_composer.user
for other functionality. Responsible users and users with edit access also can use
any functionality other than linking to an existing report.

## Procedure

1. Navigate to AllKPI Composer and open the relevant project.
2. Navigate to the Data Definition tab.
3. Locate an artifact that has a create report definition link and open that link.  
   Only artifacts associated with Report widgets in the Dashboard Visualization tab have links for creating report definitions.
4. Provide a name and a description for the report.  
   By default, the report definition has the same name as the artifact that contains it. This default name is the same as the default for an indicator definition for that artifact, so consider differentiating them.
5. In the Development instructions field, provide the developer with any technical information they need besides the report properties.  
   The Description field should contain information for the user. The Development instructions field should contain internal information for the developer.
6. Select either a Facts Table or a Report Source.
7. In the Condition field, describe the filtering conditions for the report.  
   You can write the conditions in plain text instead of the condition builder syntax.

*[\>]: and then