Configuration

Explanation

Host*

Host of the database

Use Integrated Security**

Username**

Database user

Password**

Database password

Database*

Database Schema to read from

Action ID

To determine the user and machine that created a call, we will use a specific ActionID from the call log

Append ORIID to Incident Number

Hours back to look for data (default: 2)

Agencies to include (comma-separated)

Agencies to include in pulled data. Agencies not listed are excluded.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.

TOGGLE: Include "Nature of call" as a note

TOGGLE: Include premise alerts in additional context.

Not able to utilize if using stored procedure

TOGGLE: Include extra timestamps in notes

Stored procedure to use

Name of the stored procedure to use. Data agent uses its own query if left blank.

TOGGLE: Use first/last name for note entered by

TOGGLE: Remove leading dash from agency value

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**

TOGGLE: Delete files after being processed

Whether to delete XML files after processing

TOGGLE: Use disposition as call closed filter

When configured true, only include incidents whose disposition is "Call Closed".

TOGGLE: 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.

TOGGLE: Pull call type from "Fire" context, if available

TOGGLE: Include initial location, if any, in notes