QDM Report Configuration Database Details
UI Report Builder was placed in project wise and each project has following collections to store the report builder related documents.
The project wise means, each project has its database and each database has its set of default collections which contains following report builder related collections.
QDMReports
Source and consumer details of UI Report Builder
The source or UI of Report Builder was client projects ie) ipmo, survillance, clmm etc.
The UI of Report Builder consumes Arango Adapter API, Arango Adapter was a java spring boot application which consists set of APIs.
Using Arango Adapter API, we can perform CRUD operation in Arango DB server.
Collections with details
| Collection Name | Usage |
| QDMReports | This collection used to store the Report configuration details |
Collection attributes with details
Collection Name: QDMReports
| Attributes | Usage |
| clientid | This attribute used to store the clientid. |
| metadataid | This attributes holds the metadataid |
| projectid | This attribute stores the projectid |
| readjsonschema | This attribute stores json schema for the read query |
| readquery | This attribute stores the read query for the specific report |
| reportid | This attribute stores the specific reportid |
| reportname | This attribute stores the reportname |
| reporttype | This attribute stores the reporttype(flexmonster,jasper,superset) |
| template | This attribute stores the template for the specific report |
| jrxmlfileid | This attribute stores the jasper report file uniqueid |
| jrxmltemplate | This attribute stores the template for the jasper report file |
| jrxmlfilename | This attribute stores the jasper report filename |
| activestatus | This attribute stores the value(true/false) active or not |
Production Collection
QDMReports