Capabilities

Capabilities	Supported
Connector Capabilities
Read	Yes
Backfill	No
Bidirectional Capabilities
Incident Create	No
Incident Update	No
Narrative Update	No

Customers of this CAD may be able to use bidirectional capabilities through IntelliComm. See Bidirectional CAD Integrations.

Overview

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.

⚠️ Tyler Generic XMLs do not contain CAD positional data

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

Standard Data Fields

These are the standard data fields the Data Agent reads from Tyler New World Cloud XML files. The tables below show each GovWorx incident field and the XML element it comes from. The Data Agent reads files where ClosedFlag is true. The closed call filter settings change this rule. Source names are elements of the call XML file unless the row says otherwise.

Note: Additional fields are considered enhancement requests.

Incident fields

GovWorx field	Tyler New World Cloud XML source	Notes
Incident ID	`CallId`	CAD record key.
Incident Number	`Incidents/Incident/Number`	The first Incident element.
Incident Type	`AgencyContexts/AgencyContext/CallType`	With the Fire setting on, the value comes from the Fire context. With the first agency context setting on, the value comes from the first context. The Data Agent uses Incident/Type, then NatureOfCall, when these are empty.
Initial Incident Type	`AgencyContexts/AgencyContext/CallType`	The Incident Type rules apply to the earliest file with the same CallId, by CreateDateTime.
Caller Number	`CallerPhone`
Caller Name	`CallerName`
Agency	`Incident/Jurisdiction`	Uses Location/PoliceOri when empty.
Agency Type	`Incident/AgencyType`
Incident Date	`CreateDateTime`
Disposition	`Dispositions/CallDisposition/Description`	The Call Completed disposition when present. Otherwise the first disposition.
Location	`Location/FullAddress`
Priority	`AgencyContexts/AgencyContext/Priority`	The first agency context.
Latitude	`Location/LatitudeY`
Longitude	`Location/LongitudeX`
Call Taker ID	`CreatedBy`
Call Received Time	`CreateDateTime`	The earliest CAD note timestamp setting replaces this with the earliest note time.
Closed At	`CloseDateTime`	Uses the date and time of the Call Completed disposition when empty. The Data Agent skips files with no closed time.
Call Source	`CallSource`

Notes

GovWorx field	Tyler New World Cloud XML source	Notes
Note Text	`Narratives/Narrative/Text`
Note By	`Narratives/Narrative/CreateUser`
Note Time	`Narratives/Narrative/CreateDateTime`
Initial location note	`Location/FullAddress`	Only with the Include initial location setting on. The value comes from the earliest file with the same CallId. The note author is GovWorx.

Responders and units

Source names are elements of the Unit element in AssignedUnits.

GovWorx field	Tyler New World Cloud XML source	Notes
Unit Name	`AssignedUnits/Unit/UnitNumber`
Personnel ID	`Personnel/UnitPersonnel (FirstName, LastName, ShieldNumber)`	The primary officer, in the format First Last (Shield number).
Dispatched By	`AgencyContexts/AgencyContext/Dispatcher`	The first dispatcher value found. All units on the call get the same value.
Dispatched At	`DispatchDateTime`
Enroute At	`EnrouteDateTime`
Arrived At	`ArriveDateTime`
Cleared At	`ClearDateTime`

Data Agent Settings

To prepare for this connection, we need the following details. These are settings in the GovWorx Data Agent configuration for this connector. A toggle is an on/off switch in that configuration.

*: Required.

**: Either Integrated Security or (Username and Password) is required.

Setting	Type	Explanation
`UNC Share / Directory*`	Text	A local directory path or UNC share path. A UNC share path begins with two backslashes ("\\").
`Use Integrated Security**`	Toggle	When configured true, authenticate using gMSA instead of explicit credentials
`Username**`	Text	The user for the share. Use with Password when Integrated Security is off.
`Password**`	Password	The password for the share user.
`Delete files after being processed`	Toggle	Whether to delete XML files after processing. The Data Agent deletes every file for an uploaded call, including earlier in-progress files.
`Hours back to look for files (default: 2)`	Text	The Data Agent reads files from up to this many hours back. It compares this to the last modified time of each file. Default: 2.
`Use disposition as call closed filter`	Toggle	When configured true, only include incidents whose disposition is "Call Completed".
`Use closed time as call closed filter (overridden by above)`	Toggle	When enabled, only process XMLs that contain the <CloseDateTime> tag. In progress XMLs do not contain this tag. The disposition setting above takes precedence.
`Pull call type from "Fire" context, if available`	Toggle	Toggle will read Incident Type from the Fire agency context in the XML file.
`Use first agency context's call type as incident type, if available`	Toggle	Toggle will read Incident Type from the first agency context in the XML file. The Fire setting above takes precedence.
`Include initial location, if any, in notes`	Toggle	Toggle will add a note with the first location entered for the call.
`Use earliest CAD note timestamp for Received At`	Toggle	Toggle will use the earliest CAD note time as Call Received Time. Use it when the first note marks the start of the call better than the CAD pickup time. Call Pickup Time does not change. When no note has a time, Call Received Time stays as read from CAD. Default: off. This setting is on every CAD connector.

CAD Connector - Tyler New World Cloud/XML