Capabilities
Capabilities | Supported |
Connector Capabilities | |
Read | Yes |
Backfill | Yes |
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
The Data Agent has two ways to connect to Tyler New World Enterprise CAD. The agent can connect to a replicated/reporting SQL database or process XML files created at the time CAD was closed. The replicated/reporting database can be cloud hosted or on premise.
SQL
To do this we need a user to connect to the database. You should create a read only user. The frequency the query is run is configurable and is typically set to every 8-10 minutes.
XML Files
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. The settings for XML files are in CAD Connector - Tyler New World Cloud/XML.
⚠️ Tyler Generic XMLs do not contain CAD positional data
Standard Data Fields
These are the standard data fields the Data Agent reads from Tyler New World Enterprise with the SQL connection. The Data Agent reads closed incidents. The tables below show each GovWorx incident field and the Tyler column it comes from. Source names are call.call columns unless the row says otherwise. With a stored procedure, the stored procedure returns the incident fields.
Note: Additional fields are considered enhancement requests.
Incident fields
GovWorx field | Tyler New World Enterprise source | Notes |
Incident ID |
| CAD record key. |
Incident Number |
| The ORIID setting adds the ORI ID. The training CAD setting uses TR-CallID when empty. |
Incident Type |
| |
Initial Incident Type |
| The validation set entry value for the incident type on the incident record. |
Caller Number |
| |
Caller Name |
| The primary caller. |
Agency |
| The first value that is set. Four settings change this to a description, abbreviation, or department. |
Agency Type |
| |
Incident Date |
| |
Disposition |
| The validation set entry value. |
Location |
| |
Location Name |
| The Additional Location Information box. The Data Agent reads it only when the column exists. Not available with a stored procedure. |
Initial Location |
| Only with the Include initial location setting on. |
Priority |
| |
Latitude |
| |
Longitude |
| |
Call Position |
| From the earliest call log entry that matches the Action Id. |
Call Taker ID |
| The earliest call log entry that matches the Action Id. Looked up in general.Users for the LoginID. The LoginID setting reads inc.UserID first. |
Call Taker Name |
| The same call log user. |
Call Source |
| The validation set entry value. The Class of Service setting reads E911Item.ClassOfService first. |
Call Received Time |
| The earliest CAD note timestamp setting replaces this with the earliest note time. |
Closed At |
| |
Dispatch Queue At |
| The first Call Ready for Dispatch entry. Only with the extra timestamps setting on. |
Response Area |
| Only with the Beat/Zone setting. Matches call.Beat to AreaID. |
Additional Context | Nature of call, premise alerts | Each source is a setting. Not available with a stored procedure for premise alerts. |
Notes
GovWorx field | Tyler New World Enterprise source | Notes |
Note ID |
| |
Note Text |
| |
Note By |
| The first/last name setting looks up the user name in general.Users. |
Note Time |
| |
Generated notes | Nature of call, location changes, EMD code changes | Written by GovWorx when the matching setting is on. The author is GovWorx. |
Responders and units
GovWorx field | Tyler New World Enterprise source | Notes |
Unit Name |
| |
Personnel ID |
| The person assigned to the unit. |
Dispatched By |
| Looked up in general.Users for the LoginID. |
Dispatched At |
| |
Enroute At |
| |
Arrived At |
| |
Cleared At |
|
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.
Setting | Type | Explanation |
| Text | Host of the database |
| Toggle | Toggle will enable the use of a domain service account that is configured to run the agent service as authentication to SQL server |
| Text | Database user |
| Password | Database password |
| Text | Database Schema to read from |
| Text | To determine the user and machine that created a call, we will use a specific ActionID from the call log. Default: 63. |
| Toggle | Toggle will append the ORI ID to the incident number (on: 24-001234-ORI123) |
| Text | Hours back to look for data |
| Text | Agencies to include in pulled data. Agencies not listed are excluded. |
| Toggle | Toggle will include the Nature of call field from the call |
| Text | Where the Nature of call goes: Note, Additional Context, or Both. Default: Note. Shown when the Nature of call toggle is on. If Additional Context is chosen and the premise alerts toggle is also on, the premise alert text replaces the Nature of call text. |
| Toggle | Toggle will add a line to additional context when the call taker viewed the alerts tab. Not able to utilize if using stored procedure. |
| Toggle | Toggle will add notes for location changes and EMD code changes, and will set Dispatch Queue At from the first Call Ready for Dispatch entry |
| Text | Name of the stored procedure to use. Data agent uses its own query if left blank. |
| Toggle | Toggle will show the user's first and last name as the note author. When off, the note author is the value stored in CAD. |
| Toggle | Toggle will use the LoginID from general.users for the incident user (inc.UserID) as the Call Taker ID |
| Toggle | Toggle will look up the agency description with the CallORI_2_ORIDepartament function. Turn this on only if the database has this function. |
| Text | Leave blank if the function is in the current database. Shown when the agency description lookup toggle is on. |
| Toggle | Toggle will use Abbreviation from the readonly.ori table as the agency. Takes precedence over the agency description lookup. |
| Toggle | Toggle will use Department from the readonly.ori table as the agency. Takes precedence over the two settings above. |
| Toggle | Toggle will fill Initial Location with the first address entered, when it differs from the final address |
| Number | AreaTypeID in geography.Area to read Response Area from. Leave blank to skip. |
| Number | Leave blank for the default of 30 seconds |
| Toggle | Toggle will query over a fixed time interval instead of time back, for backfilling historical data. A stored procedure receives only the beginning time. |
| Text | Beginning time (yyyy-MM-dd HH:mm). Shown when the fixed interval toggle is on. |
| Text | End time (yyyy-MM-dd HH:mm). Shown when the fixed interval toggle is on. |
| Text | Splits the fixed interval into chunks. Blank disables splitting. Shown when the fixed interval toggle is on. |
| Toggle | Toggle will use TR-<CallID> as the incident number when the call has none |
| Toggle | Toggle will use the E911 Class of Service as the Call Source. When no matching E911 record is found for the call's address, the existing Call Source stays. |
| Number | Caps how far back a stale cursor can reach so an idle or reconnected connector does not issue an oversized catch-up query. Default: 8. |
| 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. |
Note: *: Required. **: Either Integrated Security or (Username and Password) is required.
