Task actions determine the details of an assignment given to a specified user by an
automated process. You can associate task actions with workflow rules, approval processes,
or entitlement processes.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Enterprise, Performance, Unlimited, and
Developer Editions
|
From Setup, enter Tasks in the Quick Find
box, and select Tasks. Then use these settings to configure your
task.
| Field |
Description |
| Object |
Select an object for your task. Remember, tasks can only be
associated with workflow rules or approval processes for the same
object type. Choose an object that tracks activities.
Tasks
aren’t available for article types.
|
| Assigned to |
Select an assignee for your task. An assignee can be in the form of a
user, role, record owner, record creator, opportunity team role, or
account team role, depending on the type of record you chose.
- If the assignee of a task is set to the record owner and the
owner of a lead or case is a queue, the task is assigned to
the person who triggered the rule.
- If a custom object has a master-detail relationship with
a standard object, the owner of the custom object record is
automatically set to the owner of the main standard object
record. For example, if a custom object called
“Expenses” has a master-detail relationship
with Accounts, the owner of each expense record is the owner
of the account for the expense.
- If the assignee of a workflow task is a role and more than one user belongs to that role, the
record owner becomes the task assignee, regardless of their role. We recommend
that you don’t assign tasks to roles with multiple users. Assigning tasks to
roles with one user allows you to easily change the user in that role without
modifying the workflow rule. If the assignee of a workflow task is a role and
that role is empty, the record owner becomes the task assignee, regardless of
their role.
- When a lead is converted by someone
who isn't the lead owner, all workflow tasks associated
with the lead that are assigned to that user, except
email alerts, are reassigned to the lead owner. Workflow
tasks assigned to users other than the lead owner and
lead converter aren't changed.
|
| Subject |
Enter a subject for the task. Distinguish automated tasks from
user-created ones by starting the subject with a specific notation, such
as adding (Automated) at the end. |
| Unique Name |
Enter a unique name to refer to this component in the API. The
requirement for uniqueness is only within the selected object
type. You can have actions of the same type with the same unique
name, provided they’re defined for different objects.
The Unique Name
field can contain only underscores and alphanumeric characters.
It must be unique within the selected object type, begin with a
letter, not include spaces, not end with an underscore, and not
contain two consecutive underscores.
|
| Due Date |
Choose a due date for the task. Due dates appear in the
time zone of the assignee.
Configuring a task’s Due
Date to "Rule Trigger Date" sets time triggers
and workflow task due dates based on the date that the workflow time
trigger’s action is executed. For example, if the task due date is
"Rule Trigger Date plus 10 days" and the time trigger is
executed on January 1, Salesforce sets the task due date to January
11.
|
| Status |
Choose a status for the task. |
| Priority |
Choose a priority for the task. |
| Comments |
Enter comments for the task. |
Notice that all your tasks include a Created By field. For
tasks, this field contains the name of the person who saved the record that
triggered the rule to assign the task.
Tasks don't trigger task-based workflow rules if they’re created automatically, such as
by clicking the Send An Email button or by using the Email to
Salesforce BCC address field.