Local File Share Option
The data agent application can connect to a cloud or on premise hosted replicated/reporting database. If attempting database connection, check here.
The data agent processes XML files Tyler is able to deliver from either Cloud or On-Premise deployments and place them in a local or shared directory.
*: Required.
**: Either Integrated Security or (Username and Password) is required.
Configuration | Explanation |
UNC Share / Directory* | A local directory path or UNC share path. A UNC share path begins with two backslashes ("\\"). |
Use Integrated Security** | When configured true, authenticate using gMSA instead of explicit credentials |
Username** |
|
Password** |
|
Delete files after being processed | Whether to delete XML files after processing |
Use disposition as call closed filter | When configured true, only include incidents whose disposition is "Call Closed". |
Use closed time as call closed filter | When enabled, only process XMLs that contain the <CloseDateTime> tag. In progress XMLs do not contain this tag. |
SFTP Upload Option
In addition to monitoring a local or shared directory, CommsCoach can also ingest XML files delivered via SFTP directly from Tyler CAD.
This method is commonly used in cloud-hosted Tyler environments where direct file shares are not available.
How it works
Tyler CAD exports incident XML files
Files are securely transmitted via SFTP to a designated endpoint
CommsCoach ingests and processes these XML files the same way as directory-based ingestion
When to use SFTP
Tyler is cloud-hosted and cannot write to a UNC share
Security policies restrict direct file share access
A managed, secure transfer method is preferred
Setup Reference
For full configuration steps and requirements, refer to:
👉 https://support.govworx.net/en/articles/9585970-sftp-incident-ingest