Skip to main content

CAD Connector - Hexagon

GovWorx integration guide for the Hexagon CAD system.

Written by Eli Max

Overview

GovWorx offers two ways to connect to Hexagon CAD depending on your particular deployment.

Direct Database Query

The Data Agent will read from a Hexagon replicated reporting database. Agent will run prebuilt read-only SQL queries on a customer determined time interval. To do this we will need a SQL reader user account to connect.

To prepare for this connection, we need the following details.

Configuration

Explanation

Host*

Host of the reporting database

Username*

Database user

Password*

Database password

Database name*

Database Schema to read from

TOGGLE: Use Integrated Security

Whether to use gMSA to authenticate to the database. Either enable this or supply both a username and password.

TOGGLE: Connect to availability group reader

TOGGLE: Include subtype in incident type

Report incident type as "{type}-{subtype}"

TOGGLE: Do not include system generated notes

TOGGLE: Include related persons and vehicles in notes

TOGGLE: Use note creator's full names instead of CAD IDs

TOGGLE: Use uni_hi_rec_id for responders (Integraph)

TOGGLE: Do not use common_event_call table for call data

Lookback time in minutes (default: 30)

TOGGLE: Add EID to additional context

Depending on your configuration, either num_1 or eid is used for each incident's ID. Enable this to always include the EID in the "Additional context" field of each event.

agency_event view name (optional override)

common_event view name (optional override)

common_event_call view name (optional override)

an_al view name (optional override)

evcom view name (optional override)

persl view name (optional override)

un_hi view name (optional override)

un_hi_persl view name (optional override)

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 database field 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


​

CSV file via SFTP

We have also worked with customers who want more control over the query to programmatically export and upload a CSV. See this article for more details on our SFTP flow.

https://support.govworx.net/en/articles/9585970-sftp-incident-ingest

​


​

Did this answer your question?

Related Articles