Introduction
Types are schema entities that define the data types used within an application. A type represents a business object, such as a Project, Task, Asset, or Device. Users create records from types, and each record created from a type is called an instance.
Administrators use the Types settings to create and manage types. They can set types as application menus, establish relationships between types, and associate attributes with types to define the information each instance captures. For example, a Task type might include attributes for description, due date, and assigned user. See Attributes for more information about defining fields.
When an Administrator updates a type, instances created from that type display the updated type details on the instance page.
Before deleting a type, the Administrator must remove the attributes associated with the type and any dependent configuration that references it. If users have created instances using the type, the Administrator cannot delete the type.
Type editor sections
The type editor contains these sections:
| Section | Purpose |
|---|---|
| Details | Configure the type name, display names, lifecycle, generated names, tracking IDs, geolocation flags, and thumbnail. |
| Triggers | Select programs that run before or after type events such as create, update, delete, message, attachment, import, export, and get. |
| Attributes | Associate attributes with the type and configure required behavior. |
| File Types | Associate file type definitions with the type. |
| Document Export Templates | Configure .dotx templates for document export. |
| Geofence | Configure geofence events, loitering delay, and geofence trigger programs. |
| Access | Configure create access, report access, default everyone access, and access policy. |