Time Tracking Widget
The Time Tracking widget enables recording working hours directly on the dashboard – broken down by projects, orders, or other reference objects. A timer can be started and stopped for each reference object. When stopped, a time entry is automatically saved in the configured data schema.
This allows working hours to be documented seamlessly without manual post-entry.
Typical Use Cases
| Use Case | Description |
|---|---|
| Project hours | Track working time per client project for reporting. |
| Order time | Record time spent per production or service order. |
| Client consulting | Document consulting time per client for billing. |
| Maintenance work | Capture duration of maintenance tasks per machine or facility. |
| Support tickets | Track handling time per ticket for SLA reporting. |
| Freelancer billing | Log hours worked per contract or assignment. |
Features
- Reference list: The widget shows a list of all available reference objects (e.g., projects or orders).
- Start/Stop: A timer can be started and stopped individually for each reference object.
- Live counter: The current elapsed time is displayed in real time in HH:MM:SS format.
- Automatic entry: When stopped, a data object with start time, end time, and duration is created automatically.
- Multiple timers: Several timers can run simultaneously – e.g., when switching between projects.
Configuration
The following settings are configured in the properties panel:
- Entries Schema: In which data schema should time entries be saved?
- Reference Source: Where do the reference objects (e.g., projects) come from?
- Schema mode: Reference objects are loaded from a second data schema.
- SQL mode: Reference objects are loaded via an SQL query (e.g., for filtered or computed lists).
- Field Mapping: Which fields of the entries schema are populated with start time, end time, duration, and reference?
Reference Modes
| Mode | Description |
|---|---|
| Schema | Reference objects are loaded directly from a data schema (e.g., all projects). |
| SQL | Reference objects are determined via an SQL query – e.g., only active projects or orders assigned to a specific team. |
Example
An employee opens the dashboard and sees the timer tile with all active projects. The timer for "Project Alpha" is started. After one hour of work, it is stopped. A time entry with start, end, and duration is automatically saved in the "Time Entries" schema.
Tips
- SQL mode for filtered lists: When only specific projects should be shown (e.g., only active or user-assigned ones), the SQL mode is recommended.
- Combine with table: A table widget displaying the time entries of the same schema provides a good overview of recorded hours.
- Multiple timers: Running multiple timers simultaneously is possible, but unused timers should be stopped promptly.