Field Types
Every entity field has a type, which determines how it's stored, displayed, and edited. Some types are available right away in the entity creation wizard (see Entities Overview); the rest are added later, in the full schema editor, on the form layout tab.
Basic types
| Type | Description | Used for |
|---|---|---|
| Text | Single-line text | Names, short labels |
| Textarea | Multiline text | Descriptions, comments, long-form text |
| Integer | Whole number | Quantities, sequence numbers |
| Float | Floating-point number | Amounts, measurements |
| Boolean | Yes/no (toggle) | Flags, indicators |
| Date | Date without time | Deadlines, birthdays |
| Date & Time | Date and time | Deadlines, event timestamps |
| Email address with basic format validation | Contact information |
Types for specific value formats
| Type | Description | Used for |
|---|---|---|
| Phone (📞) | Phone number | Contact information |
| URL (🔗) | Link | External resources, documentation |
| Telegram (✈️) | Telegram contact/link | Contact information |
| WhatsApp (💬) | WhatsApp contact | Contact information |
For the Phone and WhatsApp types, you can additionally configure the number format/mask in the field editor.
Value lists and statuses
| Type | Description | Used for |
|---|---|---|
| Value List | A field with a fixed set of options defined by the administrator (value + display name) | Priority, request type, and any enumerable values |
| State Model | The record's state model — a status with a limited set of allowed transitions | Record lifecycle. See State Models for details |
| Category | A reference to a node in a tree-structured catalog (category catalog) | Categories, sections, hierarchical classifiers — see Categorization |
An entity can have only one State Model field.
Relations to other entities and users
| Type | Description | Used for |
|---|---|---|
| Model List | A reference to one or more records of another entity (which records can be selected may depend on the value of another field, and already-linked records can be excluded) | For example, a "Responsible Department" field referencing the "Departments" entity |
| User | A reference to a system user | Requester, assignee, approver |
| Company | A reference to a company (with the option to restrict visibility scope) | Multi-company scenarios, customers |
| Org Unit | A reference to a department in the org structure | Linking a record to a department/unit |
Org Unit and User fields can be restricted to "internal only" and filtered by an employee's presence (current activity) status.
For relations between entities that need a bidirectional table with their own attributes (rather than just a reference in a field), a separate mechanism is used — see Relations.
Files and media
| Type | Description | Used for |
|---|---|---|
| File | One or more files of any type (configurable via the "Allow multiple files" checkbox) | Attachments, documents |
| Image | A single image or a gallery ("Allow multiple images" checkbox) | Photos, screenshots |
| Point on Map | A geographic point (coordinates) | Site addresses, geolocation |
| Image Map | An image with marked points on it | Diagrams, floor plans with records linked to points on the plan |
Service and builder types
| Type | Description | Used for |
|---|---|---|
| Type Extender | A record subtype — turns one entity into several variants, each with its own set of visible fields and (optionally) its own set of state model statuses | For example, a "Ticket" entity with "Incident" / "Change Request" subtypes |
A subtype (Type Extender) doesn't duplicate the state model — all statuses are stored once in the entity's shared registry, and for each subtype the administrator simply marks which of the shared statuses and transitions are available to it. See State Models for details.
Catalogs (category references)
If an entity is created as a tree-structured catalog (category catalog), only a reduced set of simple types is available for it: Text, Textarea, Integer, Float, Boolean, Email, Date, Date & Time, Value List — no relations, media, or service types. This is because catalogs don't have a record card, history, or chat — they're just a tree of labeled nodes.
System fields
In addition to custom fields, every record has system fields that aren't editable in the builder but are visible in the list and card: id, creation date, last modified date, creator, and last editor.