Customize How a Blueprint Runs Based on Criteria with Variants in Agentforce Operations

How Variants Work

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 you want the same process 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. Agentforce Operations evaluates variant conditions by using first-match logic based on each variant's original publish date, with the earliest published variant evaluated first. When Agentforce Operations selects a variant and the workflow starts, Agentforce Operations doesn't reevaluate the variant conditions when workflow field values change.

Note Configure variant conditions so that only one variant can match. If multiple variants have overlapping conditions, the system selects one variant, but the selection order isn't guaranteed. Overlapping conditions indicate a configuration error.

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.

Each variant has its own version history and blueprint ID, separate from the standard blueprint. To update a variant, create a new version, make your updates, and publish the blueprint. To unlink a variant from the standard blueprint, remove the variant condition, and publish the variant. Learn more in Turn on and Manage Blueprint Variants in Agentforce Operations

Variants in Linked Workflows

When a standard blueprint with variants is used in a linked workflow task and the linked workflow task restarts, variant conditions are reevaluated based on the task's state:

• If the linked workflow task hasn't started, Agentforce Operations evaluates variant conditions by using the latest field values.
• If the linked workflow task is in progress, Agentforce Operations pauses the existing workflow and resumes it. Variant conditions aren’t reevaluated.
• If the linked workflow task completes, Agentforce Operations evaluates variant conditions by using the latest field values and creates a new workflow.

Variant Behavior If the Standard Blueprint Is Changed

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 Request information field.
• Make a previously optional Request information field required.