Skip to main content
Version: 2023.1

Server reporting

The Reporting micro front-end enables your application's users to create report specifications, run them, or save them for later use.

From the GUI, users can:

  • select columns from existing data sources
  • save the report with a name and retrieve it for future use
  • apply ad hoc filtering to a report
  • export the report results to .csv format

The micro front-end has a GUI that walks the user through generating a report.

Example showing creating a new report

Once the report has been created, it can be viewed in the GUI. It can also be exported to a .csv file.

Example showing the list of all generated reports

All the generated reports are stored for retrieval later. The report configuration is saved and the report updated when the user runs the report again.

Example showing the list of all generated reports


Front-end configuration

See the web section of the documentation to see the micro front-end documentation.

Server configuration

To enable this component on the server, pull in the from Artifactory, and unzip it alongside genesis and auth modules in the standard genesis deployment server directory.

To make data available to users so that they can create reports, you must insert entries into the REPORT_DATASOURCES table. This table determines which data resources can be reported on. In most cases, you will have already set up queries in your Data Server to provide the data, but you can add new sources by creating new queries in your application-dataserver.kts.

For example, to make two dataserver queries available to the reporting server:


using an example file REPORT_DATASOURCES.csv


The Report Server adds the following metadata services:

  • ALL_SAVED_REPORTS (Data Server)
  • SAVED_REPORTS (Request Response)
  • ALL_REPORT_DATASOURCES (Request Response)