Task Workflow
Task Workflow
This guide explains the task workflow from draft planning to billable approval, including the new submit/save draft semantics and notification behavior.
Task form actions
- Submit: runs workflow transitions and approval-readiness checks.
- Save draft: persists current edits and skips workflow transition/readiness logic.
- Cancel: closes or navigates away without changing task state.
- Task forms no longer expose PDCA/action select fields directly.
Workflow states
- New tasks start as PDCA
planand actiondraft. - Quick-start tasks from dashboard play start as PDCA
doand actionactive. - Submit from task edit moves task toward approval processing (
check+donebehavior in workflow path).
Plus additions and auto-task defaults
When adding a task entry from plus without selecting an existing task:
- Goods: creates a task with check/done defaults and a title derived from product name.
- Milage: creates a task with check/done defaults and a date/from-to based title.
- Expense: creates a task with check/done defaults and a default expense title.
Approval readiness and fallback behavior
Billable compile validates readiness per entry kind before creating pending billable items.
Readiness checks include:
- contact id
- quantity, unit, price
- owner, title
- odometer start/stop (milage)
- transport start/stop datetime (milage)
- product id (goods)
- attached file, expense type, amount, date from/to (expense)
If a task is not ready:
- task is moved to PDCA
actand actiondraft - pending billable items for the task are canceled
- readiness errors are written to entry metadata
Notifications
- Approver notification: memberships with TeamRole
approve tasksare notified when compile prepares new pending billable items. - Owner notification: task owner is notified when a task is returned to draft due to readiness failures.
Review and continue
- Approvers can review pending items from the Billable Items index.
- Owners can open the task edit page from notification links, update missing details, and submit again.