Task Types

Task Types are configuration templates that define the structure, appearance, and behavior of tasks in LMI. Each task type specifies what data fields a task contains, how it appears in different views (cards, lists, calendars), and what entity it may be linked to. Task Types enable flexible task management where different types of work can have completely different data structures and visual presentations.

Overview

A task type configuration includes:

• Basic information - Name, description, color, and icon for visual identification
• Entity linkage - Connection to plugins like Customer, Opportunity, Lead, or Work Order
• Editor configuration - How the task editing interface behaves
• Data schema - Custom fields that tasks of this type contain
• Layout configuration - How tasks appear in Card, List, Calendar, and Mobile views
• Operational settings - Billing support, templates, and checklists

Accessing Task Types

Navigate to Settings → Task Management → Task Types from the sidebar.

Task Types List

The Task Types page displays all configured task types in a searchable, filterable table.

Table Columns

Column	Description
Name	Task type name with color indicator (click to view details)
Color	Visual color swatch for the task type
Icon	Icon displayed on tasks of this type
Editor Type	How the task editing interface is configured
Plugin	Associated entity type (Basic, Customer, Opportunity, etc.)
Created	Date the task type was created

Tip

Click on any task type name to open the detail panel.

Search

Use the search box to find task types by name. The search performs partial matching on the task type name.

Filtering

Click the Filters button to filter task types by multiple criteria.

Filter	Description
Entity Type	Filter by plugin type (General, Customer, Order Header, Equipment, Opportunity, Lead)
Editor Type	Filter by editor configuration (Basic, Custom, Opportunity, Lead, Work Order)

Viewing Task Type Details

Click on a task type name to open the detail panel, which shows the complete task type configuration.

Detail Information

The detail panel displays:

• Task type name and description
• Color swatch and icon preview
• Active status badge
• Billing support indicator
• Template availability
• Entity type/plugin assignment
• Creation date

Adding a New Task Type

1. Click the Add Task Type button in the page header dropdown
2. Fill in the required fields in the edit panel
3. Configure data schema if needed
4. Set up layout configurations for different views
5. Click Save to create the task type

Editing a Task Type

From the task type detail panel, click Edit to modify the configuration. The edit panel is organized into tabs for different aspects of the task type.

Info Tab

The Info tab contains basic configuration and settings.

Basic Information

Field	Required	Description
Name	Yes	Display name for the task type
Description	No	Optional description explaining the task type’s purpose
Color	Yes	Hex color code for visual identification (click to open color picker)
Icon	Yes	Icon from the Tabler Icons library (click to browse icons)

Configuration Settings

Field	Required	Description
Editor Type	No	Defines how the task editing interface behaves
Plugin	No	Links tasks to entities (Customer, Opportunity, Lead, Work Order, etc.)

Status Toggles

Toggle	Default	Description
Active	On	Whether this task type is available for use
Supports Billing	Off	Enable billing features for tasks of this type
Has Template	Off	Enable template functionality for this task type

Note

When you select a Plugin, the task type automatically inherits data fields from that plugin’s entity. For example, selecting “Customer” makes customer-related fields available on tasks.

Data Tab

The Data tab allows you to define custom fields for tasks of this type. This tab only appears when the Entity Type is set to something other than “Basic”.

Schema Mode

Choose how data fields are configured:

Mode	Description
None	No custom fields; use only entity data from the plugin
Custom Fields	Define your own fields using the schema builder
Predefined Schema	Use a predefined schema from the plugin registry

Custom Field Builder

When using Custom Fields mode, you can add fields with these types:

Field Type	Description
String	Text input field
Number	Numeric input field
Boolean	Yes/No toggle
Select	Dropdown with predefined options
Date	Date picker
Time	Time picker
Lookup	Reference to another entity (uses predefined lookup configurations)

Each field supports additional options:

• Required - Make the field mandatory
• Pattern - Regex validation for text fields
• Min/Max - Range limits for numbers
• Enum Values - Options for select fields
• Format - Display format specifiers

Tip

Drag and drop fields to reorder them. The order determines how fields appear in forms.

JSON Schema Definition (Entity/Complex Types)

For plugins that connect to external entities, the Data tab displays a JSON schema editor instead of the custom field builder. This schema defines which fields from the source entity are available for layouts and task data.

The JSON schema uses a simple format where field paths are set to true to include them:

{
  "customer_name": true,
  "order_total": true,
  "contact_info": {
    "email": true,
    "phone": true
  }
}

Element	Description
Validation Badge	Displays “Valid” or “Invalid” status for the JSON syntax
Insert Default	Populates the editor with the plugin’s default schema
Copy Schema	Copies the current schema to your clipboard

Note

Nested objects in the schema (like contact_info above) create grouped field sections in the layout editor.

Layouts Tab

The Layouts tab configures how tasks of this type appear in different UI contexts. Each layout context has its own independent configuration.

Layout Contexts

Configure separate layouts using the context tabs at the top:

Context	Description
Card	Compact cards used in Kanban boards and dashboards
List	Table-style rows with configurable columns
Calendar	Calendar event representation
Mobile	Mobile-optimized compact display

Line-Based Layout Editing

Layouts are organized into lines (rows), where each line contains one or more fields. This enables multi-line displays with flexible arrangements.

Managing Lines:

• Each layout starts with default lines based on the plugin type
• Lines display fields horizontally within the same row
• Click the trash icon on a line to remove it and all its fields
• Empty lines are automatically cleaned up when fields are removed

Adding Fields to Layouts

The Available Fields section shows all fields that can be added to the layout, organized by category:

Category	Description
Core Fields	Built-in fields like Title and Description (Basic plugin only)
Plugin Fields	Fields from the selected plugin’s entity schema
Object Groups	Nested fields organized by their parent object

To add a field:

1. Expand the appropriate category in the Available Fields accordion
2. Click the + button next to the field
3. Select which line to add the field to, or choose New Line

Field Styling Options

Click any field in the layout to open the styling popover and customize its appearance.

Option	Values	Description
Display Type	Text, Badge, Date, Time, Currency, Avatar	How the field value is rendered
Color	Light, Dark	Text color (text display type only)
Weight	Light, Heavy	Font weight (text display type only)
Size	X-Small, Small, Normal, Large	Font size (text display type only)
Variant	Default, Outline	Badge style (badge display type only)
Move to	Line 1, Line 2, …, New Line	Move field to a different line

Reorder Mode

Enable Reorder mode to drag and drop fields within a line to change their order.

1. Click the Reorder button (it highlights when active)
2. Drag fields left or right to reposition them
3. Click Reorder again to exit reorder mode

Caution

Some plugins have fixed layouts that cannot be modified. When a fixed layout is detected, the editor displays a message indicating the layout is read-only.

Task Type Relationships

Task Types connect to other entities in LMI:

Task Type
├── Workflows (uses task type to define task structure)
├── Tasks (instances of this type)
├── Plugins (entity linkage)
│   ├── Basic (standalone tasks)
│   ├── Basic Customer
│   ├── Customer
│   ├── Opportunity
│   ├── Lead
│   ├── Work Order
│   ├── Resource Shift
│   ├── Fuel Order
│   └── Fuel Billing
├── Teams (assignment rules)
└── Labels (categorization)

Workflows

Workflows use task types to define what kind of tasks move through the workflow stages. Each workflow is associated with one or more task types.

See Workflows for more details.

Tasks

Individual tasks are instances of a task type. The task type determines:

• What fields are available on the task
• How the task appears in different views
• What billing options are available
• What entity the task is linked to

Plugins

Plugins provide pre-built data schemas and entity connections:

Plugin	Entity Connection	Use Case
Basic	None	Standalone tasks with core fields only
Basic Customer	Customer records	Simple customer-related tasks
Customer	Customer records	Full customer tasks with detailed fields
Opportunity	Sales opportunities	Sales pipeline management
Lead	Lead records	Lead qualification and conversion
Work Order	Work orders	Field service and maintenance
Resource Shift	Resource schedules	Shift management tasks
Fuel Order	Fuel orders	Delivery-related tasks
Fuel Billing	Billing records	Billing and invoicing tasks

Best Practices

Naming Conventions

• Use clear, descriptive names that indicate the task’s purpose
• Keep names concise but meaningful (e.g., “Customer Follow-up” not “Task for following up with customers”)
• Use consistent naming patterns across related task types

Color and Icon Selection

• Choose distinct colors that are easily distinguishable in views
• Select icons that visually represent the task type’s purpose
• Avoid using the same color/icon combination for multiple types
• Consider colorblind-friendly palettes for accessibility

Data Schema Design

• Only add fields that are actually needed
• Use appropriate field types (don’t use string for dates)
• Make required fields truly required
• Group related fields logically in the layout
• Leverage plugins to avoid duplicating entity data

Layout Optimization

• Card views should show only the most critical information (2-3 lines max)
• List views can include more columns for scanning
• Calendar views should highlight time-relevant information
• Mobile views should prioritize actionable information

Troubleshooting

Task type not appearing in workflows

• Verify the task type is set to Active
• Check that the task type’s entity type is compatible with the workflow
• Ensure you have permissions to view the task type

Custom fields not showing on tasks

• Confirm the Data tab has the correct schema mode selected
• Verify fields are properly configured in the schema builder
• Check that the layout includes the custom fields

Layout changes not reflected in views

• Clear your browser cache and refresh the page
• Verify you clicked Save after making layout changes
• Check that the correct layout context (Card, List, etc.) was modified

Plugin data not available

• Ensure the correct Plugin is selected in the Info tab
• Verify the entity_data_schema is properly configured
• Check that tasks are linked to the appropriate entity records

Cannot delete task type

• Task types with associated tasks cannot be deleted
• Deactivate the task type by setting Active to Off
• Archive associated tasks before attempting deletion