Overview

Enghouse InteractiveQuality Management Suite’s (QMS) Custom Reporting feature enables the continuous, near real-time export of QMS’s internal data to another SQL Server database to support your organization’s custom reporting needs. The Custom Reporting database allows QMS data to be manipulated, analyzed and presented using your organization’s preferred toolset while preserving data integrity and minimizing performance impact in QMS. Custom Reporting requires a feature license. The Custom Reporting database can be co-located with the QMS database, hosted remotely or cloud-hosted. QMS data is published to the Custom Reporting database every 15 minutes.

There are three elements to enabling the Custom Reporting feature: DB, Admin and Migrate

• DB - Create the Custom Reporting database and enabling auditing in the QMS database.
• Admin - Administer the external database credentials and record retention behavior for the feature.
• Migrate - Complete the initial data migration. The initial data migration will migrate any existing QMS data within the record retention scope to the Custom Reporting database.

If site security allows, all three elements can be completed using the QMS web client. Performing the Admin at the web client will automatically attempt to perform the DB element if the Custom Reporting database doesn’t exist and offer the option to start a Migrate upon database creation. Executing DB using the QMS web client requires that the service account running the QMS Data Service has permission to alter a database in the SQL Server hosting the QMS database to turn on auditing. Additionally, if Custom Reporting is setup using Windows authentication that same service account needs to have database creation permissions (dbcreator) at the Custom Reporting database host. If Custom Reporting is setup using SQL Server authentication the administered SQL user would need to have database creation permissions at the Custom Reporting database host.

Alternatively, the database operations, DB, and optionally the initial data migration, Migrate, can be completed via the QMSInsightsTool. Performing the DB element using the QMSInsightsTool allows an administrative account to log into the tool host and run the tool, easing security constraints. The QMSInsightsTool can also optionally run the initial data migration and provides better progress feedback when migrating a large data set. Lastly, the QMSInsightsTool allows the Custom Reporting database script to be exported for a manual creation at the Custom Reporting SQL Server host. It is permissible to perform elements DB then Migrate using the QMSInsightsTool then perform element Admin last via the QMS web client.

In all cases the Admin element needs to be performed via the QMS web client and Migrate has to be run via the web client or from QMSInsightsTool before QMS data is routinely published to the Custom Reporting server. In all cases the database credentials provided in the Admin element will require insert, update, delete, and execute permissions at the Custom Reporting database. If Windows Authentication is used the service account running the Data Service will require these permissions, the named SQL Server user account requires them in the case of SQL Server Authentication.

If the Custom Reporting feature is enabled and later disabled in the QMS client the Custom Reporting database will be left intact. Re-enabling Custom Reporting with the same database will require the database be reset to a clean state and an initial data migration performed.