Update Task

Concept

Built-in Tasks is a concept feature. It's still being developed and can change before it's released. It's available only when the site's license includes the Concept feature Tasks.

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Workflows

Changes the title, description, priority or due date of a task. Empty parameters are left unchanged.

Typical Use Cases

• Raise the priority of a late order task to High, in an escalation step's workflow
• Move the due date when the supplier asks for more time
• Rename a task when the record it's about is renamed

Don't use it to

• Change who has the task. Use Assign Task or Reassign Task instead.
• Change the status. Use Start Task, Complete Task or Cancel Task instead.

Related Actions

Action Name	Description
Reassign Task	Sets a new assignee, new candidate roles, or both.
Escalate Task	Runs the task's next escalation step now.
Read Task	Reads a task, with whether the current user may change its due date.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Task Id	The id of the task, usually a token such as [Task] in an escalation or event workflow, or [Id] in a grid row.	Yes	empty	Yes
Title	The new title. At most 450 characters.	Yes	empty	No
Description	The new description.	Yes	empty	No
Priority	The new priority: Low, Normal, High or Urgent. Switch to an expression to set it from a token.	Yes, as an expression	empty	No
Due Date	The new due date. Pick a date and time.	No	empty	No
Due Date (Text)	The new due date as a date or a token, for example [DateTime:Relative(add="2 days")|o]. It's used when Due Date is empty.	Yes	empty	No
Comment	Why the due date changes. The event workflows get it as [Comment]. It's only used when the due date changes.	Yes	empty	No
Output Token Name	The name of a token, without brackets, that receives the task after the change, for example Task. See Task fields in tokens.	No	empty	No
On Error	Actions to run when the task can't be changed. [ExceptionMessage] holds the reason. See Errors and refusals.	No	empty	No

Output

Token	Description
[<Output Token Name>]	The id of the task.
[<Output Token Name>:Priority], [<Output Token Name>:DueDate] and the other fields	The task after the change. See Task fields in tokens.

Considerations

• Who may change what. Only the Task administrators of the type, superusers, and escalation steps' workflows may change the title, description and priority. The due date may also be changed by the assignee, when the type has The assignee can change the due date on.
• Empty means unchanged. You can't clear the description or remove the due date with this action.
• A new due date clears the task's overdue mark, and the escalation steps are rescheduled from the new date. Steps that already ran don't run again.
• Events. A new due date raises Due date changed, and the workflow the type binds to it runs with the comment. A new title, description or priority raises no event.
• Nothing to change. When Title, Description, Priority and both due dates are empty, the action only reads the task into the Output Token Name.

The action can fail with these messages, besides the ones in Errors and refusals:

Message	Why
Only a Task administrator of <type> can edit this task.	The title, description or priority changes and the user isn't a Task administrator of the type.
Only a Task administrator can change the due date of this task.	The due date changes and the user may not change it.
The title of a task can have at most 450 characters.	Title is too long.
The priority must be Low, Normal, High or Urgent.	Priority has another value.
"<value>" is not a date.	Due Date (Text) isn't a date.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Raise the priority of a late order task

Add this action to a workflow that implements the Task Escalation contract, such as "Purchase order - Raise the priority", and use it as the first escalation step of the Purchase order type, at the due date. [Task] holds the id of the late task.

{
    "Title": "Update Task",
    "ActionType": "PlantAnApp.Tasks.UpdateTask",
    "Description": "Raise the priority of the late order",
    "Condition": null,
    "Parameters": {
        "TaskId": "[Task]",
        "Priority": {
            "Expression": "",
            "Value": "High",
            "IsExpression": false,
            "Parameters": {}
        },
        "OnError": []
    }
}

2. Give the buyer two more days

Add this action to a button of a form with a TaskId field and a Note field. It moves the due date to two days from now, and the Due date changed workflow gets the note as [Comment].

{
    "Title": "Update Task",
    "ActionType": "PlantAnApp.Tasks.UpdateTask",
    "Description": "Move the due date",
    "Condition": null,
    "Parameters": {
        "TaskId": "[TaskId]",
        "DueDate": "[DateTime:Relative(add=\"2 days\")|o]",
        "Comment": "[Note]",
        "OutputToken": "Task",
        "OnError": [
            {
                "Title": "Display Error Message",
                "ActionType": "ShowError",
                "Parameters": {
                    "Message": "<p>[ExceptionMessage]</p>"
                }
            }
        ]
    }
}

Revised 11/12/2026