Process Orchestrator

Assignment and tasks

Decide who receives a stage's work, which activity table the tasks use, and how tasks are created.

Each stage hands its work to people as activity records, usually Dataverse tasks. The Assignment section of the stage panel decides which activity table to use, who receives the activities, what they are called, when they are due, and when the stage counts as done. Users work on these tasks in their normal views and queues; when they complete or cancel a task, the stage checks its completion criteria.

Configure the assignment

Open the stage and expand Assignment.
Choose the Task Entity: an activity table such as Task, Phone Call or a custom activity. Select the task columns that the completion criteria need, such as a custom Decision column.
Choose Assign To and fill in the field that appears for it.
Enter the task Title and Due Date.
Enter the Completion Criteria. See Stages.

Assign To options

Option	Field	What happens
User	User: an expression that returns a user	One task, owned by that user. It is also added to the user’s personal queue, when the user has one.
Team	Team: an expression that returns a team	One task, owned by the team. It is added to the team’s default queue, when the team has one. Any member can then pick it up through normal Dataverse queue handling.
Each Team Member	Team Member: an expression that returns a team	One task for each enabled member of the team. Disabled users are skipped. All members are included, however large the team.
Custom (Single task)	Task: an expression that returns one task record	You create the task yourself, typically in an On Entering flow, and the stage tracks it.
Custom (Multi tasks)	Tasks: an expression that returns a list of task records	You create the tasks yourself, typically in an On Entering flow, and the stage tracks all of them.

When the stage’s completion criteria become true, tasks that are still open are cancelled for Each Team Member and Custom assignments, so team members who have not acted do not keep open tasks. User and Team assignments create a single task, so there is nothing to cancel.

There is no “system” assignment. For a step that needs no person, such as calculating a score or calling an external service, run a logic flow in On Entering or On Exiting of the stage before or after it.

Task settings

Setting	What it does	Notes
Task Entity	The activity table used for the tasks, plus the columns the completion criteria can read.	Required to publish.
Task Title	The subject of each task.	Localized. It is evaluated in the assignee’s language.
Due Date	The deadline of the stage and of each of its tasks.	A date and time expression. This is the date shown in the process viewer and the date escalation checks. Use the same expression in General > Due Date.

Each task’s Regarding is the process instance, so users can open the instance (and its viewer) from the task. A task has no built-in instructions, required fields or forms; put guidance in the task title, in the record the process runs on, or in a form for your custom activity table.

Because the assignment is evaluated after the stage’s On Entering flows run, the User, Team, Task or Tasks expressions can use the flows’ outputs. That is how custom assignment works: an On Entering flow finds the right people or creates the tasks, and the assignment reads its outputs.

Choose an option

Scenario	Use
A named person must act, such as the account manager	User
Any member of a group can do the work, such as the claims desk	Team
Several people must each respond, such as a three-person approval board	Each Team Member
The assignees depend on business rules, such as region and amount	Custom (Single task) or Custom (Multi tasks), with an On Entering flow that creates the tasks

Example

A credit-limit change on an account must be approved by every member of the Credit Committee team.

Task Entity: Task, with the columns Status and a custom Vote choice (Approve or Reject).
Assign To: Each Team Member, Team Member: the Credit Committee team.
Task Title: “Approve credit limit for “ followed by the account name.
Completion Criteria: every task is completed, or any task has Vote = Reject.

A member whose user account is disabled receives no task, so the committee is not held up by people who have left.