Kaseya User-Defined Fields

Autotask Device Discovery uses system-generated User-Defined Fields (UDFs) to map the information from a monitoring service to Autotask entities, for example, organizations and Devices. When an RMM extension module is turned on, the system adds UDFs to Autotask. The number and type of additional UDFs that are added will vary by monitoring service, but all monitoring services add an Organization and a Device UDF.

When the Device Discovery Wizard maps a monitoring service customer to an Autotask organization, a device to an Autotask device, or a ticket or alert to an Autotask ticket, it enters the monitoring service information into the appropriate UDF.

The following table describes the UDFs that are currently generated by the Kaseya Extension. The UDFs also correspond to elements in the XML tokens that are used by the Add Ticket Email Service (ATES).

This Autotask UDF	Maps This Kaseya Entity Type	To This Autotask Entity Type	Used with This ATES Element
Organization UDF: Kaseya Customer ID	Organization ID (Organization, Account, etc)	Organization Entity	<CustomerID source=”Kaseya” name=”[value]”/>
Device UDF: Kaseya Device ID	Machine	Device Entity	<DeviceID source=”Kaseya” name=”[value]”/>
Device UDF: Kaseya Agent GUID	Agent GUID	Device Entity	<DeviceGUID source=”Kaseya” name=”[value]”/>
Ticket UDF: Kaseya Ticket ID	Ticket Number	Autotask Ticket Entity	<TicketID source=”Kaseya” name=”[value]”/>

For additional information on UDFs in monitoring service extensions, refer to System UDFs for remote monitoring extensions.

For additional information on UDFs in ATES, refer to The Add Ticket Email Service (ATES).