What Is the Difference Between tp!owner and tp!assignees in Appian?
What Is the Difference Between tp!owner and tp!assignees in Appian?
Answer
tp!owner and tp!assignees are both task properties in Appian. Each one identifies users connected to a task in a process model.
Here’s how they differ:
tp!assigneesreturns the users or groups the task is assigned to.tp!ownerreturns the user who accepted the task. Once the task is complete, it can tell you who completed it.
1. tp!assignees: task assignees
This property returns the list of users or groups the task is assigned to.
Example:
A loan approval task is assigned to the Loan_Officers group.
tp!assigneesreturns Loan_Officers.- Members of the group can open and accept the task, depending on how its assignment is configured.
- The task stays available to eligible assignees until someone accepts it.
2. tp!owner: task owner
This property identifies the user who accepted the task.
Example:
A loan approval task is assigned to the Loan_Officers group, and John, a member of the group, accepts it.
tp!assigneesreturns Loan_Officers.tp!ownerreturns John.
John is the task owner because he accepted the task.
If John completes the task, you can use tp!owner to identify him as the person who completed it.
Example: Loan Approval Workflow
A loan application needs approval from the Loan Officers group:
Task stage | tp!assignees | tp!owner |
|---|---|---|
Task assigned to Loan Officers | Loan_Officers | null |
John accepts the task | Loan_Officers | John |
John completes the task | Loan_Officers | John |
This example assumes a group-assigned task that one user has to accept.
What happens if John returns the task?
If John returns the accepted task to the assignee pool:
- Appian clears John as the task owner.
- The task becomes available to the eligible assignees again.
- Another group member can accept it.
So the value of tp!owner can change during the task’s lifecycle.
Main differences
Feature | tp!assignees | tp!owner |
|---|---|---|
Purpose | Identifies the assigned users or groups | Identifies the user who accepted the task |
Return type | List of users or groups | User |
Before acceptance | Holds the assigned users or groups | null |
After acceptance | Still the task assignees | The user who accepted it |
After completion | Assignment information | Can identify who completed the task |
Can it change? | Yes, through reassignment | Yes, when task ownership changes |
Interview points
tp!owneris not the user who created the task.tp!ownercan be null if nobody has accepted the task yet.tp!assigneescan hold several users or groups.- When a task is assigned to a single user, Appian accepts it automatically when that user opens it.
- To find the user who started the process, use
pp!initiator, nottp!owner. tp!ownerandtp!assigneesare task-level properties, whilepp!initiatoris a process-level property.
References:
Check yourself
Question 1 of 3, on what the answer above covers.
- 1.In an Appian Loan Management application, a User Input Task named "Review Loan Application" is assigned to the Loan_Officers group.The task has been created, but no group member has accepted or opened it yet.What are the values of tp!owner and tp!assignees?
- 2.An Appian approval task is assigned to the Loan_Managers group.John and Sarah are members of this group.Sarah accepts the task and approves the loan application.After the task is completed, which Task Property can identify Sarah as the user who completed it?
- 3.A User Input Task is assigned to the Finance_Reviewers group.John accepts the task, making him its owner.Later, John selects Return Task to All Assignees instead of completing it.Assume the task remains assigned to the same group and no other user has accepted it.What happens to tp!owner?