Blueprints are reusable templates for automated workflows in Agentforce Operations.
Learn what blueprints are, how to link them, how versions work, and how to use variants for
different scenarios.
Required Editions
License Required
This feature is a workspace that’s external to your Salesforce org and requires
an Agentforce Operations license.
To purchase an Agentforce Operations license, contact your Salesforce account
executive.
Blueprints are reusable templates for automated workflows. They're a structured process
with a defined beginning and end. Create a blueprint first, and then start workflows from
it to run your process.
Linking Multiple Blueprints
A linked blueprint nests a child blueprint
inside a parent as a sub-process. The linked blueprint doesn't run independently. The parent
tracks the child's progress and can receive output fields back from it. At run time, both
appear on the Home page as independent workflows. Permissions don't inherit between parent
and child. A blueprint can contain up to four linked blueprints.
Blueprint Versions
Every time you publish a blueprint, Agentforce Operations creates a new version of the
blueprint and updates the change log to include the new version. Admins and editors can add
version notes when publishing a new version and restore any previous version. There's no
limit on the number of versions a blueprint can have, allowing teams to evolve and improve
their processes over time.
Blueprint Variants
Blueprints can include multiple variants to support
different scenarios, such as regions, product lines, or customer types. Variants are
alternate versions of a standard blueprint that run different stages and tasks based on
conditions you define, such as a single-select field value. Every variant collects the same
data as the standard blueprint but routes the work differently. When a workflow starts, it
evaluates the conditions. Each variant has its own version history and Blueprint
ID.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.