Task Detail View
Clicking a task in the list opens the detail view as a sidebar on top of the current view. Here you see all information about the task, change the status, check off the checklist, and complete the task.
Features Overview
Read View
The sidebar presents the task clearly: on the left title, description and — in this order — checklist, bound form and photo proof (the work first, then the evidence); on the right the "Properties" panel with status, property, checkpoints, assignee, due date, recurrence, priority, categories, and reaction. Tasks created from an incident carry the note "From incident"; a customer or work order is not shown in the task itself — the work order shows its execution task on the order page. Each task also has a change history — every edit is recorded there automatically.
Changing the Status
Use the status field under "Properties" to change the status directly — without entering edit mode. The defaults are Open, In progress, Cancelled, and Done; you create custom phases in between under Settings → Catalogs → Task phases. The proof (photo, form, scan) is only checked when completing via "Mark as done", not on a plain status change — so always finish tasks with mandatory proof via that button.
Checklist
If the task contains a checklist, you can check off the individual items directly in the detail view. This makes the task's progress visible at any time. The checklist is not a completion condition — the task can be completed even with open items.
Comments
Use the comment section to discuss the task. For tasks that originated from a customer ticket, the comment section also serves as feedback to the customer.
Completing
Use "Mark as done" to finish the task. For a series, you complete the opened occurrence — the header of the sidebar shows it as the chip "Occurrence …". An occurrence can be completed only once: afterwards the green chip Done with time and person replaces the "Mark as done" button. At the same time the header of the detail view shows the button "Proof PDF": it downloads the same completion proof that an automation rule can send by e-mail (task, checklist, photos; "Completed by" as personnel number) — for a form completion the form PDF. One-off tasks move to the Done phase on completion and disappear from the open lists; the "Proof PDF" button appears for them as well once they are done. If photo proof is required, you are prompted to upload a photo when completing — without a photo, the task cannot be completed. In the portal you upload the photo as a file; its origin (camera or gallery) is shown as an icon on the image. In the app, only the live camera is allowed. If a form is bound to the task, it is completed by submitting the form instead; manual completion is then locked. The button "Submit form & complete" (for a checklist template "Finish checklist & complete") is available both in the sidebar header and at the end of the form — both trigger the same submission. Mandatory hints no longer appear as a sentence above the fields: an info icon in the header of the form tile explains via tooltip that the form has to be submitted to complete the task, and the pencil icon next to it opens the template in the form editor. The "Photo proof" tile carries the requirement as an asterisk on its title; the allowed formats and sizes are shown as a tooltip on the add tile. If "Complete only at checkpoint" is enabled, employees can complete the task in the app only after scanning a linked checkpoint; in the portal you can still complete it — the completion is then saved with the note "completed without scan".
Cancel a completion instead of deleting it. A recorded completion can no longer be deleted — it is cancelled: the card Completion (on the right, above the properties) carries the button "Cancel completion" (permission: delete tasks). A reason is always mandatory — chosen from the known reasons (correction, error fix, customer request …), with free text for "Other". If the task or its property requires a digital signature, the cancellation must be signed as well. Afterwards the proof stays visible — as a red banner "Cancelled by … on …, reason: …" in the card, as a Cancelled row in the completions export, with the note CANCELLED in the proof PDF and in the signature log (the original signature shows Cancelled there, the cancellation gets its own signature row). The occurrence counts as open again (overdue, coverage, schedule and automation rules treat it as not done) and can be completed anew; a one-off task moves from Done back to Open. The cancellation appears in the task history and under History → Settings as the area Task completion. The LiteLog app still shows the occurrence as done until its next data pull.
If your company uses the bookable Digital Signature feature (re-authentication per 21 CFR Part 11), completing a task may additionally demand a signature — in the portal by re-entering the password, in the LiteLog app with password, PIN, NFC chip or QR code. Whether a task must be signed is controlled by the property settings; individual tasks can override this in the detail view — section "Digital signature on completion" with the options Inherit from property, Always required and Off.
Reporting as Not Feasible
If a due task cannot be completed, report it via Not feasible… next to "Mark as done". The dialog asks for the reason from a fixed list — Access denied, Material missing, Area occupied, Safety risk, Equipment defective, or Other — plus an optional explanation and photo; for "Other" the explanation is mandatory. For a series, the report applies to the opened occurrence. An occurrence that is already done can no longer be reported. Usually the report comes from the LiteLog app, where the employee is on site.
Report: Not Feasible
If a report exists, the detail view shows an amber banner and the section Report: Not feasible with reason, explanation, photo, and "Reported on … by …". From the report onwards, the task counts neither as done nor as overdue; its phase (Open, In progress, …) does not change because of the report. Two actions are available (permission Edit tasks):
| Action | Effect |
|---|---|
| Acknowledged | Sets the review note with your name and the time. The report remains; in the list, the task drops out of the sub-filter "Unreviewed". |
| Dismiss | Lifts the report. The task counts as open or overdue again; the report remains visible in the change history. |
If the same occurrence is completed later after all, LiteLog dismisses the report automatically — the history then shows "dismissed (completed)". The task's change history records every step: Reported as not feasible, Report reviewed, Report dismissed. For a customer ticket, the customer only sees the tag "Not feasible: reason" in the customer portal — explanation and photo stay internal.
Editing
Edit mode uses the same view as creating: name plus detail fields (description, checklist, photo proof, form) and the "Properties" panel. The assigned property can also be changed later; checkpoints of the previous property are detached after confirmation, and a reaction that applied to the previous property only falls back to the default. If an assignee is absent on the due date, the note "Absent on the due date" appears under the "Assignee" row — also when reassigning or rescheduling. A due date before today is shown in red on open tasks.
Good to Know
:::tip Note
- When completing a task that a customer reported as a ticket, the customer is automatically notified of the completion.
- If a completed or cancelled task is reopened, the completion date is removed automatically.
- If you archive an employee, their open tasks remain assigned to them, but they no longer appear in the list's assignee filter. Reassign open tasks before archiving.
- Every detail view has its own web address — you can share the link to a task directly with colleagues.
- If the same occurrence is completed a second time — for example from the app and the portal at the same time — no second completion is created: LiteLog merges both entries into one proof and reports no error. :::
Permissions
:::info Permission To open the detail view, you need the View tasks permission. Contact your administrator if you do not have access. :::
| Action | Permission |
|---|---|
| View and comment on a task | View tasks |
| Edit a task, change its status | Edit tasks |
| Complete a task (incl. photo proof) | Complete tasks |
| Report a task as not feasible | Complete tasks |
| Acknowledge or dismiss a report | Edit tasks |