You are here:
Enable and Create Blueprint Variants in Agentforce Operations
Turn on and create variants of a standard blueprint that collect the same data but run different stages and tasks based on conditions you define in Agentforce Operations.
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. |
| User Permissions Needed | |
|---|---|
| To create a blueprint in Agentforce Operations: | Admin role, Creator role, or Create variants blueprint access |
With blueprint variants, you can create alternate versions of a blueprint that run different stages and tasks based on conditions you define. Use variants when the same process needs to follow different paths based on factors such as region, product type, or supplier tier.
The standard blueprint is the default blueprint used when none of the variant conditions are true. Variant conditions are evaluated in the order listed on the Variants tab of the standard blueprint.
At a minimum, every variant collects the same data as the standard blueprint, but you can configure the variant to collect more data than the standard.
Enable Variants on a Blueprint
Turn on variants for a draft blueprint so people with the Create variants permission can create alternate versions.
After you publish a blueprint with variants turned on, you can't turn variants off.
- In the navigation sidebar, click Blueprints.
- On a draft blueprint, click Edit.
- Click the Settings tab.
- For Variants, select On.
- Click the Access tab.
- In the Blueprint access section, click + Grant access.
- For People, select the people, teams, or roles to give access to.
-
For Published blueprints, select Create variants.
Granting Create variants access also gives View access to the published blueprint.
- Save your changes.
- Click the three dot dropdown list and click Publish blueprint.
Create a Variant of a Blueprint
Create a variant of a published standard blueprint to customize the stages, tasks, and access for a specific scenario.
Each variant has its own version history and Blueprint ID, separate from the standard blueprint. To update a variant, open it and create a new version as you would for a standard blueprint. Non-data changes to the standard blueprint, such as reordering tasks or changing access, don't affect variants. However, some data changes to the standard blueprint can cause a variant to become non-compliant, which prevents you from using it to create new workflows. These changes to the standard blueprint can make the variant non-compliant:
- Delete a required intake field.
- Make a previously required intake field optional.
- Add a new Requested information field.
- Make a previously optional Requested information field required.
After you turn on variants on the blueprint, and publish the standard blueprint, admins, and people with the Create variants permission can create variants.
- In the navigation sidebar, click Blueprints.
- On the published main blueprint, click Open.
- Click the Variants tab.
- Click + Create variant.
-
Select the blueprint to use
- To use the standard blueprint, click From standard.
- To use an uploaded blueprint, click Import from another workspace. Then, follow the steps to upload the blueprint.
- Enter a name and description for the variant.
- Define the conditions that determine when Agentforce Operations uses this variant. You can set conditions by using any field of the Select type that the standard blueprint collects as an intake field.
-
Customize the stages, tasks, settings, and access for the variant.
If you remove fields collected in the standard blueprint, you can’t publish the blueprint. To review any required fields from the standard blueprint that are missing from the variant, click the Data tab.
- Publish the variant.
The variant is listed in the standard blueprint's Variants tab and on the Published blueprints page when you select Show variants. Agentforce Operations notifies all standard blueprint editors by email.
