You are here:
How Blueprints, Workflows, and Tasks Work Together in Agentforce Supply Chain
Understand the relationship between blueprints, workflows, and tasks so you can design and run automated business processes in Agentforce Supply Chain.
Required Editions
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Supply Chain license. To purchase an Agentforce Supply Chain license, contact your Salesforce account executive. |
Every automated process in Agentforce Supply Chain involves four key concepts: blueprints, workflows, stages, and tasks. Each serves a distinct purpose, and they work together in a clear hierarchy.
Blueprints: The Template
A blueprint is a reusable template that defines the structure of a business process. It specifies the stages, tasks, assignments, fields, and rules that make up the process. Think of a blueprint as the instructions. It describes what should to happen, in what order, and who is responsible.
Design blueprints one time and reuse them many times. A single blueprint can generate hundreds of workflows. You can create blueprints from scratch, generate them with AI, or customize an existing blueprint. You can also create variations of a blueprint to handle different scenarios, such as regions or product lines.
Learn more in Blueprints in Agentforce Supply Chain.
Workflows: The Running Instance
A workflow is a single running instance of a blueprint. When you create a workflow from a blueprint, Agentforce Supply Chain uses the blueprint's structure to generate the stages and tasks for that specific run. Each workflow has its own data, assignees, and timeline.
For example, if a blueprint defines a supplier onboarding process, each new supplier you onboard gets its own workflow. The blueprint stays the same, but each workflow tracks a separate supplier through the process.
Workflows start running immediately after creation. Task assignees receive email notifications, and they can complete their work from the email or by logging in to Agentforce Supply Chain.
Learn more in Run Automated Workflows in Agentforce Supply Chain.
Stages: The Structure
Stages are groups of related tasks within a blueprint or workflow. They break a process into logical phases. For example, a supplier onboarding blueprint can have stages for Document Collection, Review, and Approval.
Stages can have dependencies on other stages, making sure that work happens in the correct order. When a stage starts, all tasks within it that are set to start with the stage become active at the same time. A blueprint must have at least one stage with one task before a you can start a workflow from it.
Tasks: The Work
Tasks are the individual units of work inside a workflow. Each task is assigned to a person, a team, or an AI agent. Tasks can request information through custom fields and forms, require document uploads, or ask for approvals and signatures.
Tasks don't all become active at the same time. Each task activates based on its start condition. The start condition can either be when its stage begins or when a prior task is completed. When a user or agent completes a task, the information collected in that task can get passed to downstream tasks, and the next task in the workflow gets triggered automatically.
Learn more in Tasks in Agentforce Supply Chain.
How They Connect
The relationship follows a simple pattern:
- An admin or process owner creates a blueprint that defines the structure, stages, tasks, and rules for a process.
- A user creates a workflow from that blueprint, which generates a running instance of the process with its own data and timeline.
- As the workflow runs, stages activate based on their dependencies. When a stage starts, the tasks within it become active.
- Assignees complete their tasks, and the information flows from task to task until the process is finished.
Changes to a blueprint don’t affect workflows that are running. To apply changes, publish a new version of the blueprint and create new workflows from it.
