--- schema_version: "1" id: fe4acf3d36465da1e513bcba4f1813e3d3ca627dc822dd95f28608825cb85659 title: Turn on and Manage Blueprint Variants in Agentforce Operations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_blueprints_variants_enable_create.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_variants_enable_create.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 6c7524f6c9620da9aacf45efd1a146bb903c2a6c77069b09b541ce353f1aa182 description: Turn on variants for a blueprint to collect the same data but run different stages and tasks based on conditions you define in Agentforce Operations. Then create, update, and unlink variants as needed. products: - Cross Cloud release: "264" --- # Turn on and Manage Blueprint Variants in Agentforce Operations Turn on variants for a blueprint to collect the same data but run different stages and tasks based on conditions you define in Agentforce Operations. Then create, update, and unlink variants as needed. ### 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
See [Customize How a Blueprint Runs Based on Criteria with Variants in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_variants.htm&release=264.0.0&type=5 "Use variants to adapt a published blueprint for different teams, regions, or scenarios while preserving the original blueprint.") for information about how variants work. ## Turn on 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 off variants. 1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes."). 2. In the blueprint, click the **Settings** tab. 3. For Variants, select **On**. 4. Click the **Access** tab. 5. In the Blueprint access section, click **\+ Grant access**. 6. For People, select the people, teams, or roles to give access to. 7. For Published blueprints, select **Create variants**. Granting Create variants access also gives View access to the published blueprint. 8. Save your changes. 9. 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. After you turn on variants on the blueprint, and publish the standard blueprint, admins, and people with the Create variants permission can create variants. 1. In the navigation sidebar, click **Blueprints**. 2. On the published main blueprint, click **Open**. 3. Click the **Variants** tab. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-agentforce_operations-264-0-0-production-enus/dce314e6-0a31-4a8b-98f7-3d2a3fd02ee2/images/icon_note.png) Note The Variants tab appears only after you publish a blueprint with variants turned on. If you don't see the Variants tab on a published blueprint, create a new version of the blueprint and turn on Variants in the Settings tab before publishing. 4. Click **\+ Create variant**. 5. Select the blueprint to use. 1. To use the standard blueprint, click **From standard**. 2. To use an uploaded blueprint, click **Import from another workspace**. Then, follow the steps to upload the blueprint. 6. Enter a name and description for the variant. 7. 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. 8. 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. 9. Click **Create**. The variant is listed on the standard blueprint's Variants tab. To view variants, open the standard blueprint and click the **Variants** tab. Variants don't appear on the Published blueprints page. Agentforce Operations notifies all standard blueprint editors by email. ## Update a Variant Update a variant by creating a new version, making your changes, and publishing the blueprint. 1. In the navigation sidebar, click **Blueprints**. 2. On the published standard blueprint, click **Open**. 3. Click the **Variants** tab. 4. On the variant you want to update, click the variant name. The variant opens. 5. Click the three-dot dropdown list and click **New version**. The new version of the variant opens as a draft. Only one draft can exist at a time. If a draft is in progress, and you try to create a new version, Agentforce Operations directs you to the existing draft version instead of creating a new one. 6. Make your changes to the draft. 7. Click the three-dot dropdown list and click **Publish blueprint**. 8. Enter version notes that describe what changed and click **Publish**. Publishing requires version notes. They appear in the variant's change log and About tab. Agentforce Operations publishes the updated variant, increments the version number by one, and records the version notes. ## Unlink a Variant from the Standard Blueprint Remove the variant condition in the draft blueprint's About tab to unlink a variant from the standard blueprint. 1. In the navigation sidebar, click **Blueprints**. 2. On the standard blueprint, click **Open**. 3. Click the **Variants** tab. 4. On the variant you want to unlink, click the variant's name. The variant opens. 5. Click the three-dot dropdown list and click **New version**. The new version of the variant opens as a draft. 6. Click the **About** tab. 7. Click **Edit details**. 8. For each variant condition, click the garbage can icon. 9. Click **Save changes**. 10. Click the three-dot dropdown list and click **Publish blueprint**. 11. Enter version notes that describe what changed and click **Publish**. Publishing requires version notes. They appear in the variant's change log and About tab. The variant is no longer linked to the standard blueprint's conditions. To relink it, create a new version and add a variant condition on the About tab.