Autogenerate Workflow Names with Merge Fields in Agentforce Operations
Create a naming convention for workflows so each workflow started from a blueprint
gets a consistent, descriptive name based on field values 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.
Role or Access Needed
To create a blueprint from scratch, using AI, or by importing a .rex file in
Agentforce Operations:
Admin role or Creator role
To create a blueprint by importing a .docx file in Agentforce Operations:
Admin role
To publish a blueprint in Agentforce Operations:
Admin role or Publisher role with View access for the blueprint
Autogenerated workflow names help you quickly identify and organize workflows without relying
on manual naming. When you add merge fields to the name, Agentforce Operations replaces each
field with the workflow's value for that field. For example, a name template like
{Region} - {Supplier} - {Quarter} creates workflow names like
EMEA - Acme Corp - Q2.
You can only set up autogenerated workflow names on draft blueprints. To change autogenerate
settings after publishing, create a new blueprint version.
In the navigation sidebar, click Blueprints.
Click the Draft blueprints tab.
Locate the blueprint and click Edit.
Click the About tab.
Click Edit blueprint details.
Select Autogenerate workflow name.
Enter the name template, adding fields where you want them to appear.
To add a field, click Add fields.
Search for and select the field you want to include.
Check the preview to make sure that the name looks right.
Enter a version note that describes the change, such as Updated autogenerated
name.
Click Save changes.
New workflows started from this blueprint use the autogenerated name based on
the fields you selected.
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.