When you select a Job Report from the Analyze > Reports page, you view the last saved version of that report. You can also view a report by clicking the View Report button while editing a report. Reports you view are populated with Job Action results pulled from the moment you open it and do not automatically refresh data after they are opened.
You can click on the Report Date Range to quickly update the time range and pull new data into the Job Report. Updating the time range when you view a Job Report does not affect the range used by the saved version of that report.
Viewing a Job Report
Viewing a Report's API Payload and Response
Report Builder uses the Validation Platform API to fetch the latest data in your environment and populate your custom reports. The exact POST request and response contents for each component or panel are available to you when you view or edit a report. In any panel, click the button, then select View Request Data.
The Request Payload tab shows you the POST payload used to fetch data for the panel you're viewing. The corresponding Response tab shows you the data that's populating the panel you're viewing.
The Report Builder Panel Request window
Job information included in the Reports
Completed Job Actions are the source data for the reports you build using Report Builder. By default, data on Job Actions that errored is excluded, but you can configure the report to include the errored data. For more information on how to include this information, see Configuring the Report Data Source.
Errored summaries in the Data Tables
To view errored Job Action information in your data table, you can include three Job Action Results data points: Completed, Errored, and Total Job Actions. When you group the data in the tables, the table automatically calculates the percentage and total count for that field. Since the completed, errored, and total Job Actions columns include information that aren't included in other fields, you will see different total counts for those fields. For example, in Annotated Data Table you see several Actions that only have errored information because they didn't complete. Then, if you look at A100-295, there's a total of 8 Actions included, but only 6 that completed. So, the other stats in the table are based on 6 rather than 8.
