You are here:
Configuring Tasks in Agentforce Supply Chain
Understand the configuration options available when setting up tasks in blueprints in Agentforce Supply Chain.
Task Fields and How They're Used
| Field | Description | Notes |
|---|---|---|
| Task name | A clear name that describes the work. | Keep names short and action-oriented, such as Review supplier contract. |
| Start | When the task starts in the workflow. | Start when the stage starts, after a prior task completes, or on a specific date. |
| Due | When the task is due. You can set the time to complete in days, hours, and minutes. Or you can use the value from a date field. | For example, if using Time to complete, enter 25 hours to set it to 1 day and 1 hour. If using From a field, select Invoice Due Date to have the task due on the day the invoice is due. |
| Assigned to | Who completes the task: users, roles, teams, or AI agents. | You can assign tasks to multiple assignees. AI agents complete tasks autonomously or alongside human reviewers. Learn more about assigning tasks to AI agents in Assign a Task to an AI Agent in Agentforce Supply Chain. |
| Cc | People who need visibility but aren't responsible for completing the task. | Cc'd users receive task emails and can comment but can't complete the task. |
| Escalation | People automatically added to the task as a CC or an additional assignee as the due date approaches or passes. | Use escalations to notify a manager or backup when a task is at risk. For example, add a team lead 1 day before the due date, or add a director if the task becomes overdue. |
| Description | Specific instructions or context for the assignee. | Include all information that the assignee needs. AI agents rely on descriptions to complete work. If you want to use a field’s value in the instructions, add a merge fields by @ mentioning the field, such as @Supplier Name. When the workflow runs, the merge field is replaced with the field’s value. Checkbox and signature fields aren’t supported, Also, fields used in the Requested information section of a task aren’t supported because the value can change when the requested field is filled out in the task. |
| Documents | Files attached to the task for the assignee to reference or use. | Supported formats include PDF, .docx, .xlsx, .png, and .jpg. |
| Tags | Labels to classify and filter tasks. | Useful for grouping tasks across workflows in list views and reports. |
| Share information | Fields from prior tasks that are shared as context for this task. | AI Agents can only use shared fields explicitly passed to the task. |
| Request information | Fields or forms the assignee must complete. | You can share collected values in later tasks. |
Task Assignee Types
You can assign tasks to multiple people, teams, roles, and AI agents. Determine the correct assignee based on task requirements and assignee type behavior.
| Assignee Type | Behavior |
|---|---|
| Internal user | Individual receives a task notification by email and can complete the task in the workspace or by email. |
| External user | Invite non-workspace users by email to complete specific tasks through email and forms. |
| Team | All team members are notified. Any member can complete the task. |
| AI agent | AI Agent completes the task autonomously without human intervention. |
| AI agent + human co-assignee | AI Agent fills requested fields, then waits for the human to review and submit. Learn more in Add a Human Reviewer to an AI Agent Task in Agentforce Supply Chain |
