Overview
The Data Agent will read from the Central Square Enterprise Reporting Database. To do this we need a user to connect.
To prepare for this connection, we need the following details.
Configuration | Explanation |
| Host of the reporting database |
| Database user |
TOGGLE: | Toggle will enable the use of a domain service account that is configured to run the agent service as authentication to SQL server |
| Database password |
| Database Schema to read from |
TOGGLE: | Toggle on will cause the agent to query a SP in SQL. GovWorx will assist in the query fields needed to be returned from SP. |
| Name of SP in SQL |
TOGGLE: | Toggle will enable Method of Call Receive field from Response_Master_Incident table to be used for CommsCoach Call Source |
TOGGLE: | Toggle will enable Confirmation Number field from Response_Master_Incident table to be used for CommsCoach Event Number |
TOGGLE: | Toggle will use Time_CallEnteredQueue from Response_Master_Incident table as CommsCoach Event Time |
TOGGLE: | Toggle will append the CAD Address with the Premise Name field from CAD (on: 123 Main Street) (off: 123 Main Street - Starbucks) |
TOGGLE: | Toggle will append the CAD Caller name with the Caller Location field from CAD (on: John Smith) (off: John Smith - Starbucks Parking Lot) |
TOGGLE: | Toggle will disable the caller name entirely. If this is configured true, the above parameter (Include caller location) is ignored. |
TOGGLE: | Toggle will enable SQL query to check the linked incidents table and not pull any CAD incidents into CommsCoach that where cloned from other CAD Incidents (i.e. "ADD AGENCY") |
TOGGLE: | Toggle will relate linked incidents in CommsCoach |
TOGGLE: |
|
TOGGLE: |
|
TOGGLE: |
|
Agency Type (NOT IN) | Comma separated values to list agency types to exclude from data query |
Jurisdiction (IN) | Comma separated values to list jurisdictions to include in the data query |
TOGGLE: | Add information about premise and caution notes to the "additional context" field of each incident. Disabled when using a stored procedure. |
TOGGLE: | Disabled when using a stored procedure. |
Additional context custom view name |
|
TOGGLE: | Requires dbo.problem table access |
Note: Fields marked with an asterisk (*) are required.
SQL Server Configuration Notes
To ensure a successful and secure connection, verify the following:
Firewall Access: Ensure the server hosting the GovWorx Data Agent can reach the SQL Server over the appropriate network and port (typically TCP 1433).
Minimum Permissions: The provided database user must have read-only access to relevant tables, views, or stored procedures. Write access is not required or recommended.
Instance Visibility: If using a named instance, confirm SQL Server Browser service is running, or explicitly provide the port number.
Troubleshooting Tips
Login Failed? Verify the SQL user is enabled and not locked out.
Timeout Errors? Check network routes and firewall rules.
Invalid Database? Ensure the
databasefield in the config matches the actual schema name.
β
Network Requirements: The server running the Data Agent should be able to connect to the CAD Reporting server over port 1433. This can be tested using PowerShell.
PowerShell Command:
Test-NetConnection -ComputerName {CAD Reporting Server name or IP} -Port 1433
