The task a piece of content is being produced from, exposed as {{ Task.* }}.
Only populated where a task is genuinely behind the render — a workflow step's email, or a task
or step description being materialised. Everywhere else (broadcasts, ad-hoc client emails,
document templates, signatures) the whole namespace is left null, so the tokens render blank
rather than quietly showing another task's dates.
Values are DateOnly so Fluid renders them in the tenant's short date format by default and the
formatDate filter works natively: {{ Task.DueDate | formatDate: "long" }}.
Properties
| Name | Type | Description |
|---|---|---|
| name | string | The task's name. Usage: {{ Task.Name }} |
The task's name. Usage: {{ Task.Name }} | ||
| code | string | The task's code. Usage: {{ Task.Code }} |
The task's code. Usage: {{ Task.Code }} | ||
| startDate | string | The task's start date. Usage: {{ Task.StartDate }} |
The task's start date. Usage: {{ Task.StartDate }} | ||
| dueDate | string | The task's due date — the internal deadline the practice works to. Usage: {{ Task.DueDate }} |
The task's due date — the internal deadline the practice works to. Usage: {{ Task.DueDate }} | ||
| statutoryDueDate | string | The statutory deadline behind the task (Companies House, HMRC), where the task has one. |
The statutory deadline behind the task (Companies House, HMRC), where the task has one. | ||
JSON Example
{
"name": "string",
"code": "string",
"startDate": "2024-01-01",
"dueDate": "2024-01-01",
"statutoryDueDate": "2024-01-01"
}