📘 Introduction to Task types
Task types define what kinds of tasks can be created related to assets or service targets. Task types can be managed through the Task types button found in the menu at the top right corner of the desktop application.
From the Task types list view, you can either select an existing Task type or create a new one. Task types appear in the menu that opens via the Perform Task button on the Asset view (depending on filter settings). In the Task type page, you can configure related settings (on the left) and a form (on the right), which determines what information should be documented when carrying out the task.
Next, we'll go through the available settings that can be configured for a Task type.
🛠 Settings (items 1–12)
The following settings are located under the same "Settings" section in the application, though in this document they are grouped for clarity.
⚙️ Basic Settings
These define the core properties and structure of the task type: name, creation method, default status, and recurrence.
1. Task type name
Enter a descriptive name for the task type, e.g., Fault report or Scheduled maintenance.
2. Task creation method
Choose one of three options:
By scheduling or filling a form
Allows both scheduled creation and creation via a form.
By scheduling only
Tasks can only be created through scheduling in advance.
By filling a form only
Used for e.g. fault reports, which are created based on events.
3. Default status
Defines the initial status of the task:
Pending (most common): Task is awaiting action.
Completed: Used when documenting an observation only, no further processing needed.
4. Can be a recurring task (yes/no)
Enables creating recurring tasks (e.g. for scheduled maintenance).
🧑 When filling a form, user
Defines what options and fields are available to the user when completing the form.
5. Can select task priority (yes/no)
Determines whether the form includes a priority selection field.
6. Can select task members (yes/no)
Lets the user assign responsible persons while filling the form.
7. Can select a date when the task was performed (yes/no)
Allows specifying when the task was actually completed (e.g., for retroactive entries).
🔧 Advanced Settings
Used to customize the task type for special cases or more restricted use.
8. Tasks do not have a date/time (yes/no)
Removes the task date field entirely.
9. Tasks do not have a status (yes/no)
Removes the status field (e.g., open/done).
10. Task is a request (yes/no)
Used for fault reports, observations, etc.
Requests are always created through the form and default to the default status.
Requests are visible in the home screen "New request" button.
11. Allow saving non-completed requests (yes/no)
If selected: form can be edited later.
If not selected: original form is preserved.
12. Set a default duration in hours (yes/no)
Specifies default task duration (e.g., 3 hours).
✉️ Task Notifications
Define when and to whom notifications are sent about tasks.
13. Send notifications to users (yes/no)
When enabled: users/teams can be added to receive notifications (e.g. new, overdue, completed).
Notification options:
New open task
New completed task
Task is overdue
Task status changed to done
13.1. Send notifications for users (yes/no)
New task members are notified automatically.
👁️ Visibility
Controls who can create and manage tasks of this type.
14. Allow non-logged-in users to create tasks of this type
Options: Private (default) / Public
Public allows task creation via QR code without login.
15. Restrict by user roles
A table where each role can be allowed:
View
Create
Edit
Delete
📦 Limit for Asset Types
Restrict usage of the task type to specific asset categories or items.
16. Restriction levels
Category
Asset Type
Individual asset
Example: The inspection task type can be restricted to only be visible for assets in the "Vehicles" category.
🔗 Chaining of Tasks
Allows workflow automation based on responses in form fields. Requires a radio button field on the form.
17. Configure chaining
If field: Select a radio button field from the form
Has value: Specify the trigger value
Then do task: Choose another task type to create automatically
Example: If inspection field “Approved” = No → Automatically create a fault report.
🛠 Update Asset Status
Enables updating the asset’s status based on form response.
18. Asset status update
If field: Select a radio button field
Has value: Specify the triggering value
Set asset status to: Choose the new asset status
🗓️ Set Date on Submit
19. Update assets field
Automatically sets the selected asset date field (e.g. "Last maintenance date") to the time when the form was submitted.