Assign Task to Current User

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

The current user assigns an unassigned task of one of their candidate roles to themselves. People see this as Assign to me in My Tasks. In BPMN terms, it's a claim.

Typical Use Cases

• Add an Assign to me button to your own list of unassigned purchase checks
• Let a buyer take an order task from a page that shows one task
• Take a task first, then start it with Start Task

Don't use it to

• Assign a task to someone else. Use Assign Task or Reassign Task instead.
• Assign a task and complete it in one go. Use Complete Task with Assign to Me If Unassigned instead.
• Assign a task in an escalation step's workflow. That workflow acts as the system, which has no user to assign the task to.

Related Actions

Action Name	Description
Unassign Task	Gives the task back to its candidate roles.
Start Task	Moves the task from Open to In progress.
Complete Task	Completes the task, and can assign it to the user first.
Get Tasks	Lists the unassigned tasks of the user's roles, with the Unassigned view.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Task Id	The id of the task, usually a token such as [Id] in a grid row.	Yes	empty	Yes
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 assigned to the user. [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>:Assignee], [<Output Token Name>:Status] and the other fields	The task after the change. See Task fields in tokens.

Considerations

• Only candidates. The user must be a member of one of the task's candidate roles, and the task must be unassigned. Task administrators and superusers need a candidate role too.
• First come, first served. When two members take the same task at the same moment, the second one is told This task was just assigned to someone else.
• The status doesn't change. The task stays Open until the user starts or completes it.
• The Assigned event. The workflow the type binds to Assigned runs with the reason claim.
• A completed or cancelled task can't be assigned.

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

Message	Why
You already have this task.	The task is already assigned to the user.
This task was just assigned to someone else.	Another user has the task.
Only a member of the task's candidate roles can assign it to themselves.	The user isn't in a candidate role, or the action runs as the system or for an anonymous visitor.

A user who isn't in a candidate role usually can't see an unassigned task at all, and gets Task #<id> was not found or you cannot see it.

Examples

tip

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

1. An Assign to me button

Add this action to a row button of a grid that lists unassigned tasks, for example one on the Tasks Data Source with the Unassigned view. [Id] holds the task's id. If someone else was quicker, the user sees why.

{
    "Title": "Assign Task to Current User",
    "ActionType": "PlantAnApp.Tasks.ClaimTask",
    "Description": "Assign the task to me",
    "Condition": null,
    "Parameters": {
        "TaskId": "[Id]",
        "OutputToken": "Task",
        "OnError": [
            {
                "Title": "Display Error Message",
                "ActionType": "ShowError",
                "Parameters": {
                    "Message": "<p>[ExceptionMessage]</p>"
                }
            }
        ]
    }
}

Revised 11/12/2026