Reporting on data from pro-code apps
Summarize
Summary of Reporting on Data from Pro-Code Apps
This document outlines how to effectively report on data from pro-code applications within the ServiceNow environment. Reporting is essential for actionable insights and often involves using the Reporting application for Core UI and Data Visualizations in Platform Analytics. The transition between these two user interfaces allows for varied reporting capabilities.
Show less
Key Features
- Core UI: Utilizes the Reporting application and Performance Analytics (PA) Widgets, focusing on data directly from tables. Reports and PA widgets can be added to responsive dashboards.
- Platform Analytics: Offers Data Visualizations that allow reporting from any data source, which can be placed on Platform Analytics dashboards with filters.
- User Experience: Non-developers can create visualizations without using UI Builder, streamlining the reporting process.
Key Outcomes
By following best practices in report and visualization creation, users can enhance performance and usability:
- Filter large tables to avoid performance issues and improve load times.
- Schedule regular exports of reports or dashboards via email for consistent data sharing.
- Utilize various methods for creating dashboards, from using the Platform Analytics experience alone to integrating with UI Builder for customization.
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.
- 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.
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.
- 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.