Overview
The GovWorx Data Agent processes XML files generated by Hexagon CAD at the close of each call. These XML files contain call and incident metadata and are written by the CAD system to a local or shared directory, where the Data Agent securely reads and ingests them for downstream processing.
Each XML file represents a completed call event and is processed once it becomes available in the configured directory.
: Required
*: Either Integrated Security or (Username and Password) is required.
Configuration
Configuration | Explanation |
UNC Share / Directory* | The local path or UNC share where Hexagon CAD writes XML files when a call is closed. Recognized as a UNC path if it begins with two backslashes ( |
Use Integrated Security** | Determines whether the Data Agent uses a managed service account (gMSA) or explicit credentials to access the directory. |
Username** | Required if using explicit credentials. The account must have read access to the directory. |
Password** | Required if using explicit credentials. |
Delete files after being processed | Whether to delete each XML file after it has been successfully processed by the Data Agent. |
Hours back | How many hours back the Data Agent should look for XML files when scanning the directory (default: 2). |
How the Connector Works
Call Completion
When a call is closed in Hexagon CAD, the system generates an XML file containing call and incident metadata.
File Detection
The GovWorx Data Agent monitors the configured directory for new XML files.
XML Processing
Each XML file is parsed and processed once it is fully written by the CAD system.
Post-Processing Handling
If enabled, processed XML files are deleted.
If not enabled, files remain in place for auditing or retention purposes.
Directory and Access Requirements
The directory must be accessible from the Data Agent host.
The Data Agent requires read access at minimum.
If file deletion is enabled, delete permissions are also required.
A dedicated service account is strongly recommended to support auditing and least-privilege access.
Best Practices
One File Per Call: Ensure Hexagon CAD is configured to generate a single XML file per closed call.
Write Completion: Confirm files are fully written before being accessed by the Data Agent.
Retention Strategy: If files are not deleted, implement a retention or cleanup policy to prevent directory growth.
Consistent Timing: Avoid manual edits or delayed writes that could cause files to fall outside the configured “Hours back” window.
Troubleshooting Tips
No Files Being Processed
Verify the directory path is correct and accessible
Confirm the Data Agent account has permissions
Increase the “Hours back” value temporarily to capture older files
Duplicate or Missed Calls
Ensure files are not rewritten after initial creation
Avoid reusing filenames
Access Errors
Validate credentials or gMSA configuration
Confirm network connectivity to the file share
Support
For assistance configuring the Hexagon CAD connector or troubleshooting ingestion issues please reach out to us at [email protected] for assistance.