Reporting on data from low-code apps

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Reporting on Data from Low-Code Apps

    ServiceNow applications typically require reporting to make data actionable. Reporting includes displaying data from fact tables, such as incidents, and creating key performance indicators (KPIs) through the Performance Analytics application. The ServiceNow AI Platform® is transitioning between two user interfaces for reporting: the Core UI and the newer Platform Analytics technology.

    Show full answer Show less

    Key Features

    • Core UI: Includes the Reporting application for table data and PA Widgets for Performance Analytics indicators. Reports and widgets can be added to responsive dashboards.
    • Platform Analytics: Offers Data Visualizations for reporting from various sources, which can be incorporated into Platform Analytics dashboards. It supports a user-friendly experience for non-developers.
    • Guidelines for Reporting:
      • Filter large tables to maintain performance.
      • Avoid grouping by fields with many values to prevent performance issues.
      • Consider scheduling exports for regular report distribution.
    • Multiple Visualization Options: Users can create visualizations entirely in the Platform Analytics experience, utilize UI Builder for custom pages, or create technical dashboards that can be shared.

    Key Outcomes

    By leveraging the reporting capabilities in ServiceNow, customers can effectively visualize and analyze data, leading to informed decision-making. Understanding the differences between Core UI and Platform Analytics allows users to select the best tools for their reporting needs, ensuring performance is optimized while accessing critical insights. Regularly scheduled reports and dashboards enhance data accessibility and usability across the organization.

    Most applications that you create have some level of reporting requirements. Reports should be actionable to drive change.

    "Reporting" generally refers to showing the data inside facts tables like Incident [incident]. You can also create key performance indicators (KPIs) to track changes in this data over time, through the Performance Analytics application.

    Currently the ServiceNow AI Platform® is in transition between two user interfaces for showing this information:
    • The older Core UI technology. This UI includes the Reporting application, which only shows data directly from tables, and PA Widgets, which show data from Performance Analytics indicators. Both reports and PA widgets can be placed on Core UI responsive dashboards. For more information, see Reporting, dashboards, and Performance Analytics in the Core UI.
    • The newer Platform Analytics technology. This UI includes Data Visualizations, which let you report on data from any source. These visualizations can be placed on Platform Analytics dashboards, along with Platform Analytics filters. For more information, see Platform Analytics experience.

      All Platform Analytics objects are rooted in the Next Experience UI Framework and are available to developers. However, a non-developer can still build their own objects through the Platform Analytics experience, without using UI Builder. For more information, see Platform Analytics experience.

    Note:
    Although "reporting" is a general term, this documentation usually uses "report" and "reporting" to refer to the Core UI Reporting application and "visualization" or "visualize" to refer to Platform Analytics data visualizations, for disambiguation.

    Follow these guidelines when building reports or data visualizations:

    • Creating reports or visualizations on large tables can negatively impact performance. Be sure to filter by a date range or other limiting criteria rather than showing all records on the table.
    • Grouping by fields that contain many possible values can negatively impact performance.
    • If loading a report or visualization gives a Long running transaction timer message, consider adding more data filters to reduce the load time.
    • If you need to export a report, data visualization, or dashboard on a regular basis, schedule the export and email.
    In Platform Analytics, you have several possibilities for showing multiple data visualizations on one page:
    • Create the data visualizations and the dashboards entirely inside the Platform Analytics experience. This approach does not require a developer role or special technical knowledge, and probably should be explored before you try a more complex solution.
    • Create data visualization components in a generic UI Builder page, along with filters and other components. This approach gives you the most freedom as a developer, but also requires the most configuration.
    • Create the data visualizations and the dashboards inside the Platform Analytics experience, but then place the dashboards inside UI Builder pages using the Dashboard page template. This approach lets you use the convenience of the Platform Analytics experience to create dashboards, data visualizations, and filters in your own experiences/workspaces. It also gives you the freedom to customize the page configuration partially. For more information, see Creating Platform Analytics pages in your own workspace.
    • Create a technical dashboard and populate it inside UI Builder. This approach is almost the same as creating your own UI Builder page from scratch, but the dashboard is available in the dashboard library, has dashboard details, and can be shared like other dashboards. For more information, see Technical dashboards.