Autonomous AI is transforming the way organizations operate, and Salesforce’s Agentforce is at the forefront of this revolution. The product was made generally available by Salesforce in October 2024. Whether you want to streamline case management, enhance lead nurturing, or delight customers, Agentforce empowers businesses to accomplish more with fewer resources. In this post, we’ll share five practical tips to help you successfully implement and use Agentforce. 

Feeling anxious about diving all in with Agentforce? Contact the Sercante team for an Agentforce readiness assessment. That way, you can be sure you’re getting set up for success before you implement Agentforce in your org.

Understanding Agentforce

Before diving into the tips, let’s take a closer look at what Agentforce is.

Agentforce enables autonomous AI agents to perform tasks without human intervention, acting as digital workers within Salesforce or external customer channels. These agents enhance productivity by automating routine tasks and assisting with complex ones. With tools like Agent Builder, you can customize agents using pre-built topics and actions or create entirely new ones tailored to your organization’s needs.

Agentforce integrates seamlessly across the Salesforce platform, leveraging Data Cloud for reasoning and learning. Out-of-the-box agents include Service Agents for case deflection, with more capabilities to be released in December 2024, such as SDR and sales coaching agents.

Unleashing the Power of Agentforce: Five Steps to Get Started

Follow these five steps to get started on the right foot when you dive into Agentforce.

Tip 1: Identify Use Cases

Start by identifying where Agentforce can deliver the most value in your organization. Ask yourself:

• How are you using your CRM today?
• What are the current pain points in your processes?
• Are there routine tasks that could be automated to free up team capacity?
• Are there new processes you’ve avoided due to resource constraints?

Examples of use cases include automating FAQ responses for service teams, generating campaign briefs for marketing, or assisting sales reps with lead prioritization and moving deals faster.

Then for each use case, think about what would be needed to transition to an agent:

• What job should they do?
• What actions will they need to take?
• What actions should they NOT take?  (This is just as if not more important to make sure you have defined the lane where an agent should operate within that use case)

Your responses to those questions are going to help you to understand the level of effort involved in use case. This in turn is going to help you to prioritize based on the level of effort and potential value

Tip 2: Define Success Metrics

To gauge the success of your Agentforce implementation, establish clear goals and KPIs. 

Questions you can ask:

• What does success mean? How will we know we have addressed our problem? 
• What metrics are we tracking today that we want to see improvement on?
• Are there additional metrics that will let us know we are seeing success?

For example:

• Reducing average case handling time by 20%
• Improving lead response times
• Increasing campaign ROI by automating content creation

Ensure you have baseline data for comparison and that the necessary measurement tools are in place to help you track success.

Tip 3: Assess Your Data

Your AI agents are only as good as the data they access. For the use cases identified, evaluate your data readiness:

• What data do need? 
• Where is it located? Is it in your CRM, Data Cloud, or other external systems?
• Is it accessible from your CRM? If it’s stored in an external system, do you have APIs in place to get that information?
• Is the data clean, accurate, and up-to-date?
  • Follow this blog post for tips on how to keep your imported Pardot prospect data clean.
• Do you have a single view of the customer across systems?
  • Get tips for creating that single source of truth in this blog post that covers marketing asset reporting, and this blog post that covers customer data platform reporting.
• Lastly, are knowledge bases and metadata structured for easy access? 
  • Agents need knowledge to inform how they will operate and answer questions. This is all of the background configurations your agents actions will rely on — flows, prompts, and Apex for example — they need to also be clearly identifiable and accessible. 
  • When you add actions to your topics, it uses the descriptions to help fuel the instructions. The naming conventions of your resources will also make it easier to determine what the inputs and outputs need to be.

Data and metadata are the backbone of AI performance, so this is an important area to pay attention to.

Tip 4: Start Small

After completing the previous steps, you may have more than one great use case to start with. Here’s where you ask yourself: What are the quick wins that we can get started on that can move the needle and that we can expand on as we mature?

It’s really easy to get caught up on how this can solve ALL the things. There are many challenges to starting a complex process all at once. If a lot of effort is required to get the data in place or to get the actions set up, it will be more difficult to roll out, not to mention making it potentially disruptive and prone to issues 

Avoid the temptation to tackle complex processes right away. Instead, focus on a simple, high-impact use case to pilot Agentforce. There are many out-of-the-box topics and actions that make getting started easier. For example, automating a single FAQ response or generating summaries for sales reps.

Starting small helps build confidence, momentum, and organizational buy-in, and it also reduces the risk of missteps.

Tip 5: Nail Down Clear Instructions

When designing agents, clarity is key. Use the Agent Builder to create and test well-defined topics and actions:

• Topics – Include precise instructions for classifying user requests, setting guardrails, and outlining scope.
• Actions – Clearly define what the agent should do, including required inputs and expected outputs.

Salesforce Agentforce Topic Instruction Best Practices

Instructions are the foundation for grounding how agents perform. They set the guardrails for how the agent should behave and give the agent the context it needs to do its job. 

Here are a few best practices for writing Agentforce topic instructions:

• Start simple
  • Start with the main use case first to ensure the agent is performing as expected. Then, add in more detail to address edge cases. Be sure to test existing instructions for any conflict. You don’t want to confuse the agent! 
• Use plain language
  • Use concise natural language to describe what your action does. Keep it to 1-3 sentences, and it can include the goal of the action, any use cases, and the objects or records it uses or modifies. 
  • In general, the more relevant detail you include in your instructions, the easier it is for the agent to differentiate between actions. Also, be sure to vary the words you use. For example, use a mix of “Get,” “Find,” “Retrieve,” or “Identify” for actions that will query records.
• Avoid industry or company jargon
  • Write like you are instructing someone who doesn’t know your business. Even terms like ‘qualified lead’ could mean something different from one organization to another. Give context where necessary, and reference clear criteria using the data it will have access to. 
  • For example, instead of vague terms like “qualify lead,” specify conditions such as “lead status equals MQL.” 
  • The agent isn’t not going to know your business processes either, so be explicit about the sequence of instructions or any conditions a conversation must meet for an agent to apply an action.
• Think of all the paths
  • You want to go through every possible permutation to determine the actions required. For example: a customer reaches out because they didn’t receive their order. 
  • First think about the order status ( Order Shipped, Delayed, Not Found, Processing). If the status is Shipped then there could be different tracking statuses (In Transit or Delivered for example). If the order is showing as Delivered, was it delivered to the customer’s correct address? Was it stolen? …and so on.
• Remember the Guardrails
  • Keep the Agent in its lane by providing clear instructions on what the agent should not do to prevent unwanted responses. In cases where the agent is customer-facing, be sure to also give clear direction on when an interaction should be routed to a human.

Test these instructions thoroughly in the Agent Builder’s testing environment to ensure your agents behave as expected.

Ready to Explore Agentforce?

Agentforce offers an exciting opportunity to enhance productivity and streamline operations. By identifying the right use cases, preparing your data, and starting with manageable projects, you can set your organization up for success.

Want to learn more? Check out Salesforce’s Agentforce Trailhead and virtual workshops to get hands-on experience. Need expert guidance? Contact the Sercante team for an Agentforce readiness assessment.

Original article: Five Tips for Getting Started with Salesforce Agentforce

©2025 The Spot. All Rights Reserved.

The post Five Tips for Getting Started with Salesforce Agentforce appeared first on The Spot.

In the Summer ‘24 Release, Salesforce launched the beta version of Einstein for Flow, which is a generative AI tool that helps Salesforce admins, regardless of their programming experience, to easily create functional Salesforce Flows via natural language prompts. 

New to Flow? Check out An Introductory Guide to Salesforce Flow for Marketers

How Einstein for Flow works

Einstein for Flow is a generative AI tool that helps Salesforce admins, regardless of their programming experience, to easily create functional Salesforce Flows via natural language prompts. You simply describe your flow requirements in plain text instructions, and Einstein does its thing to interpret those instructions and generate a draft flow for you.

Salesforce Einstein for Flow Requirements

To take advantage of Einstein for Flow, you’ll need to ensure:

• Your org supports Einstein for Flow. This feature is available with:
  • All Einstein 1 Editions
  • Enterprise, Performance, and Unlimited Editions with the Einstein for Sales, Einstein for Service, or Einstein for Platform add-on.
• Users who will use Einstein for Flow must have permission to use Manage Flows.
• You also need to make sure you have enabled Einstein Generative AI in your org.
• You will also need to opt in from the Einstein for Flow (Beta) setup screen.

Creating a Flow with Einstein for Flow

1. When you click New Flow, select Let Einstein Help You Build and click Next.

2. Enter a prompt with instructions on the flow you want to build.

• In the Instructions section, describe the task or process you want to automate. Provide as much detail as possible to try to get better results.
• 
• Not sure how to write your instructions? Expand the Get Started with Sample Instructions section.
• 
• For more tips on how to craft your prompts, see the Prompt Tips section below.

3. After a few seconds, the flow is created, and a feedback modal is included on the canvas.

• See the Helping Einstein Improve section below.
• You’ll also notice that ‘This flow was created by generative AI.” banner is located at the top of the page, so that it’s clear how this flow was built.

Tips for Building a Great Prompt

When writing your prompt instructions, there are some guidelines for getting started:

• Start the instructions with “Create a flow.”
• Effective instructions include:
  • The type of flow to create
    • for example, “Create a record-triggered flow that….”
  • When the flow starts or if it has screens.
    • for example, “…that starts when a lead is created…” 
  • The names of objects and fields to use for criteria and actions.
    • for example, “… create a task for the Lead Owner” instead of  “..create a task for the sales rep”
  • The actions you want the flow to take.
    • for example, “…send an email to the Lead owner…”
  • The criteria and logic to use to identify specific records.
    • for example, “…accounts with an annual revenue over $500,000…”
• Provide as much detail as possible.
• Start simple and expand from there. Stick to basic instructions that the resulting flow needs a small number of elements to implement. Confirm the resulting flow is built as expected before adding more complexity to your instructions.
• Don’t forget to use proper grammar and spelling!

Helping Einstein Improve

Einstein for Flow is still learning how to build accurate flows. Some flows created by Einstein for Flow won’t be built the way you expected. Here’s how you can give feedback:

• Start Over – If the output doesn’t meet your expectations, you can generate a new output by starting over. You can use the clipboard icon to copy the previous prompt if you want to tweak it in the next version. The generated output from the previous attempt isn’t saved and the new output replaces it.
  
• Provide Feedback – You can also give your feedback about what’s wrong with the flow. That helps Einstein for Flow continue to improve and build increasingly accurate flows.
  

Einstein for Flow Considerations

• Flow Types supported include:
  • Screen Flow
  • Record Triggered Flow
  • Schedule Triggered Flow
• Support building flows that include:
  • Standard and custom objects & fields
  • 3-6 custom objects
  • Create, Update, and Get Records, Screens and Send Email
  • Record variables, formulas, email templates
  • Fault paths
• Einstein for Flow uses their CodeGen model for its natural language processing. 
• Keep in mind that this is feature is in beta and as a generative AI tool it’s still learning. It’s a good idea to review all aspects of your flow to ensure accuracy. Check for things like field names and dates are correct, for example.

Additional Resources to check out:

• Video: Get to Know Einstein for Flow
• Let Einstein Build a Draft Flow for You (Beta)
• Einstein for Flow: Using Generative AI to Assist Your Flows 

The Future is Bright

While this is still in its early stages, the potential looks to be awesome as a tool that can: 

• Help those who are less technical or new to Flow get up to speed more quickly
• Give more advanced admins a starting point that they can run with instead of starting completely from scratch

And the possibilities don’t end there. Imagine a world where we had a genAI tool that could:

• Scan a flow and summarize what it does. As a new admin, how amazing would it be to scan the flows in your new company’s org to get up to speed more quickly!
• Evaluate a flow against best practices. Think of how much easier it would be to find and resolve hardcoded IDs or DML elements in a loop!
• Creating tests for the flows built

(*these are my opinions only and not tied to Salesforce’s roadmap for this tool, although I hope the Flow team keeps this wishlist in mind .)

What has you most excited about this tool? What would you love to see this feature do in the future? Let us know in the comments.

Original article: Getting Started with Einstein for Flow

©2025 The Spot. All Rights Reserved.

The post Getting Started with Einstein for Flow appeared first on The Spot.

The Salesforce Summer ‘24 Release is on its way! Let’s dive into the top declarative features and updates for admins.

In line with messaging from Salesforce, the Summer ‘24 Release includes new and enhanced features that all center on the relationships between CRM, data, AI, and trust.

Salesforce Summer ’24 Highlights

Security & Access

Get a Summary of a User’s Permissions and Access

Viewing what access a user has will be easier with the User Access Summary. Accessible directly from the user details record, you can see what a user has access to without having to spend multiple clicks checking each profile, permission set, public group, or queue.

Other great Security & Access Updates:

• See Where a Public Group Is Used
• View Summary on Permission Sets and Permission Set Groups now GA
• User Access Policies now GA

Customization

Set Conditional Visibility for Individual Tabs in Lightning App Builder

Now you can control visibility to tabs and their contents in the Lightning App Builder, based on specific criteria, giving you another tool to customize the user experience, and what users can see and when. 

View Field History Tracking from Setup

Admins can now view and control field history tracking across objects in on place, from the Setup menu. From here you can view and control the objects that have tracking en tracked, and enable, view and update the fields. 

Other Customization updates worth mentioning:

• Use Blank Spaces to Align Fields on Dynamic Forms-Enabled Pages
• Add New Custom Fields to Dynamic Forms-Enabled Pages on creation
• See Dynamic Forms-Enabled Lightning Page Usage for Custom Fields (via Where is this Used?)

Sales Productivity

Do More in the Intelligence Views

More functionality is coming to Account, Contact, Lead and Pipeline Intelligence views to help users do more in one place. Now it’s possible to perform mass actions like Add to Campaign or Send Email, and inline editing of the same field, from these Intelligence views.

Organize and Find Records Easily with Personal Labels

Users can apply their own private labels to records to help them organize, track, and find the records they need quickly and easily. Labels work on several objects including:

• Account
• Campaign
• Contact
• Case
• Email Template
• Lead
• Opportunity
• Task
• …and more

The once added to the page layout, a Labels related list will appear on the record page, allowing users to add their labels. Then the Labels tab provide a view to all of the records that have that Label applied.

Note: Users will need access to the Labels object. This is enabled by default in standard profiles but will need to be granted in custom profiles or permission sets.

Flows

Flow Management 

Automation Lightning App

The Automation Lighning App includes a Home page showing recently modified flows, and flow errors, as well as quick links to flow topics on Trailhead and to the Flow Community. 

The app also includes a Flows tab where list views to access standard and custom list views of existing flows. From here you can open a flow, open the latest version, change the owner, or delete the flow.

Note you may have to enable this features from Setup > Process Automation Settings, and checking the Enable the Automation Lighting App checkbox.

View Flow Details from a Lighting Page

When using the Automation App and list views, you’ll notice that clicking on a flow shows the details on a Lightning record page. This lets you take advantage of customizing your page layout as I’ve done in the screenshot below. 

Organize Your Flows Based on Categories and Subcategories That You Define

Another new flow admin feature, new Category & Subcategory text fields are now available on the Flow object, and accessible when creating custom list views, which can be a handy tool for organizing long lists of flows. 

Control User Access to Specific Flow Elements

Use new permissions to enable users who don’t have the Manage Flows permission, to use specific flow elements when building segment-triggered and form-triggered flows. Elements supported include:  Assignment, Collection Filter, Collection Sort, Delete Records, Get Records, Loop, and Subflow. 

Keep in mind that these permissions are available for Enterprise and Unlimited Edition with Marketing Cloud Growth. 

Flow Builder

Check for Duplicates Before Creating Records in a Flow

The Create Records element in flow just got more intelligent for preventing duplicates. Now you can first check to see if another record with specific criteria exists before creating a new record.  If an existing record is found, the field values are applied to the existing record, otherwise a new record is created. 

Before you would have to use a Get element to search for an existing record and a decision to check if anything was found before creating a new record. Having this all rolled into one element makes the flow build and maintenance much simpler and more efficient.

Required fields automatically added for Create elements

Another cool feature spotted in the pre-release org is that Create elements also automatically include required fields.

I didn’t see this feature mentioned in the Release Notes, but as this could be a super helpful I’m hoping it will turn up in the Release. Admins can probably relate to the headache of building a flow that creates a record, hitting error when a required fields are not included, then having to go back the flow to make sure that field is populated… maybe more than once!

A couple of notes to consider for this to be useful: 

• Only fields that are marked required at the field level are included. Fields that are flagged as required on the page layout are not included. 
• Also, the element may include other non-required fields. For example when creating a Lead, the IsConverted and IsReadbyOwner fields were also added to the element automatically.  This may be something only seen in the pre-release org, so it may look a bit different in the actual release.

Other cool Flow Builder Updates:

• Changes to ‘New Flow’ modal
• Transform Your Data in Flows (GA)
• ‘Is Blank’ and ‘Is Empty’ Operators in Conditions
• Debug Scheduled Flows More Successfully
• Lock and Unlock Records with an Action
• Use Threading Tokens in Emails

Screen flows

New Action Button Component (Beta)

Now you can Add an Action Button to a flow screen to run and retrieve information from an active autolaunched flow, without leaving the screen. This is a huge win for creating a better user experience. Before you’d have to use one screen to collect some information, then click next to do the necessary actions and display the output on a second screen. 

Other Updates

• Repeater Component (now GA)
• Restrict User Input on Screen Components with the Disabled and Read Only Fields
• Update Records Using the State and Country Codes Selected in Address Screen Components

Other Notable Updates

A few other updates in this release that are worth noting.

Default No-Reply Email Required

To stay in line with increased email security standards, orgs are required to create and verify a Default No-reply address in their Organization-Wide Email Address settings (replacing noreply@salesforce.com). This will affect any orgs that send emails from Salesforce. Think automated emails like Lead or Case assignment, or even emails sent from a flow. This is will be enforced starting in Winter’25, meaning that some emails may not send, so its a good idea to set up a default no-reply email address sooner rather than later.

Get Ready for the Salesforce Summer ’24 Release

This is just a handful of platform features planned for the Salesforce Summer ‘24 Release. If you’re interested in diving in to learn more about the updates in this release, I highly recommend reading through the full release notes. 

You can also check out our post on the Salesforce Summer ’24 Release for Marketing Cloud Account Engagement (Pardot) here.

Which Salesforce Summer ‘24 features have you the most excited? Let us know in the comments!

Original article: Salesforce Summer ‘24 Release Highlights: Platform Updates

©2025 The Spot. All Rights Reserved.

The post Salesforce Summer ‘24 Release Highlights: Platform Updates appeared first on The Spot.

You may be aware that when it comes to improving user experience on a record page,  Dynamic Forms have become more and more powerful over the last few Salesforce releases. A good example is the ‘Add Fields from Related Objects to Dynamic Forms-Enabled Pages’ feature from the Spring ‘24 release, which came from a  Salesforce IdeaExchange request.

Dynamic forms are a huge win for making more customizable and engaging user experiences, at least for custom objects and most standard objects. There are still a few that don’t have this feature yet. (I’m looking at you, Campaigns) 

Here’s a handy workaround that may help where dynamic forms in Salesforce aren’t supported.

Check out the latest Spring ‘24 Release updates here, including where you can display related record fields on a record. 

The Use Case: A “Dynamic” Campaign Page

You want to collect certain information for your campaigns, but the data differs depending on the type of campaign. 

Examples may include:

• Events
  • Location
  • Venue Address
  • Venue Contact Info
  • # of Days
• Webinar
  • Webinar platform
  • Presenter details
• Partnerships
  • Partner Information
  • Type of Partnership
  • Partner Contact Info

All of this different data living on the record page can be cluttered and noisy, and forcing the user to scroll through the page to get to the data they need to fill in. It’s not a great user experience and not a great recipe for capturing quality data. 

Wouldn’t it be nice if we could bump up specific fields to more prominent areas of the page based on the type?

Unfortunately, Dynamic Forms can’t help us here (at least not yet — you can upvote the idea here). Some may choose to use record types and page layouts, but that may not be ideal for all companies. 

An Alternative Solution for Salesforce Dynamic Forms

While we may not be able to use Dynamic forms, there are some other Lightning features that can give us a potential workable solution: 

• First we create a Quick Action, which allows us to build a mini page layout of the fields we want to highlight.
• Then we use Lightning Page builder features to display this mini-layout above the fold so it’s easy for the user to find and update:
  • Related Record component
  • Set Component Visibility 

Here’s how.

Create an Action for Partner fields

1. From Object Manager > Campaign > Buttons, Links, and Actions
2. Click New Action
3. For Object Name, select Campaign
4. For Action Type select Update a Record
5. For Label, enter a label that is appropriate for this purpose. It’s a good idea to make it relevant and easy to idenity what it’s for.
   • For example ‘Update Campaign – Event Details’
6. Enter a Description outlining the purpose of this action
7. Click Save

Edit the Action Layout

Once you have saved, you will be looking at the Action Layout page. Here is where you can choose what Campaign fields to display and the arrangement. 

1. Just like you would for a page layout, drag and drop the fields that you want to be visible. 
2. Click Save
3. If you see this message, go ahead and select Yes. We won’t need the Campaign Name on this layout for our use case.
   
4. You can edit this later from the Edit Layout button at the top of the page.

Now we can add our new layout to the Campaign record page

1. From Object Manager > Campaign > Lightning Record Pages
2. Select the Lighting Record Page you want to update and click Edit.
3. Drag the ‘Related Record‘ component where you want it on the page
4. In the Related Record settings panel on the right, update the following:
   • Header Label = the heading that should appear at the top of that layout on the page
   • Lookup Field = Use this Campaign
   • Update Action = the action that you created in Step 1
   • Click Save
5. Select ‘Set Component Visibility’ for the Related Record component. 
6. In the filter area, select Type = ‘Conference’

Voila! Now when working on a Campaign record, the Event Details will appear in their own “section” when the Campaign Type = Conference.  You can repeat this for other fields you want to appear on the page in specific circumstances.

To edit these fields, click the pencil icon next to the field you want to edit. All of the fields in that section will become editable, and notice that the other fields are not. These fields are edited separately because they are part of another component. When done, click the Save button to save the fields in that section. 

Build better experiences with this alternative to Dynamic Forms

While Dynamic Forms in Salesforce are fantastic for jazzing up user experiences, there are times when you need alternatives. Diving into Lightning features such as Quick Actions and Lightning Page Builder can help you to cook up custom solutions that do the job,  like the workaround we’ve explored here for displaying those crucial record fields based on different scenarios.

As you tinker around with ways to supercharge your Salesforce setup, remember, we’re in your corner. Want to chat about how to make your Salesforce dreams a reality? Reach out to the Sercante team today. Let’s brainstorm together and unlock the full potential of your Salesforce journey.

Original article: An Alternative to Salesforce Dynamic Forms When You Need It

©2025 The Spot. All Rights Reserved.

The post An Alternative to Salesforce Dynamic Forms When You Need It appeared first on The Spot.

Wow, where did the time go? The Salesforce Spring ‘24 Release notes are out and some cool new features are right around the corner!  Here are the key Salesforce platform features marketers and Salesforce admins should know about. You can also get a closer look at the features from an Account Engagement admin’s perspective in this blog post.

Salesforce Spring ’24 User Interface (UI) Updates

Add Fields from Related Objects to Dynamic Forms-Enabled Pages 

Salesforce continues to build on Dynamic form capabilities by extending the functionality to access fields from related objects. I’m very excited to see this in place, as this is a common ask that previously would have to be delivered using less-than-simple methods. This Idea has been around since 2006 and has logged more than 35,000 points!

Customization Updates for mobile:

This release also includes features that will bring more design flexibility by device, and making the user experience more relevant based on how they are working:

• Set Field Visibility by Device in Dynamic Forms
• Use Dynamic Actions with Standard Objects on Mobile
• Preview Mobile Actions on Record Pages Before Activating

Confirmation Message When You Select the Multi-Select Picklist Field Type

You can say Multi-Select picklists are sort of like raisins much like tags in Account Engagement. For some they are useful for their use case, and for others, they are a no-go because of their limitations (if you’ve tried to use them in reporting or automation you know what I mean ) 

Now, when you create a new field and select the Mutli-Select picklist data type, you will be presented with this pop-up highlighting the limitations to make sure this is the right approach before creating.

Reporting & Dashboard Updates

Easily Update Fields in Lightning Report Filters

This little update will probably save admins a lot of headaches. No more having to completely remove a filter to update it.  Now you can update the field being used in the filter. If you realize after building a report that you used the wrong date filter, all you have to do is swap the data field. The criteria remain intact.

Transfer Lightning Dashboard Ownership (Generally Available)

When someone leaves your organization, it’s now easier to transfer ownership of the dashboard to another user. In the past this had to be achieved by cloning or recreating the dashboard. 

In the Lightning Dashboard view, you can transfer ownership one dashboard at a time 

If you’re using the new Analytics tab, you can select multiple dashboards and change the owner for all selected at once.

Add Images, Rich Text, and Widgets to Dashboards in All Editions

Now you can add images or rich text widgets to make your dashboards more engaging with logos, contextual images, titles and descriptions. This feature previously available only in Unlimited and Premium editions is now available for all editions!

Five dashboard Filters now in All Editions

When creating dashboards you now can use up to five filters to give users even more ways to slice and dice the way they want and get the key information they need.

Automation Updates 

Create Multiple Instances of a Set of Fields with the New Repeater Component (Beta) 

I was very excited to see this feature, which lets users create multiple records in a single screen element. This will be ideal in situations like adding project members to a project team, or even providing a quick custom Create Contact flow. Users just populate the info for one record, then hit Add Item and new form appears allowing them to create the next one!

Supported fields include: Text, Number, Checkbox, Date, DateTime, Currency,Choices (except Choice Lookup), Display Text, Long Text Area

More Awesome Reactivity in Screen Flows

Screen flows have been getting a lot of reactivity love over the last few releases, and Spring ‘24 is no exception. Here’s a summary of features from this release:

• Use More Components to React to Changes on the Same Screen (Generally Available) 
• Use Text Templates to React to Changes on the Same Screen – 

Identify Flows Containing Email Alerts

On the Email Alerts page, you can now see what flows are using that alert, and whether the flow is active. This can be great if you’re looking to update your emails and want to understand what processes will be impacted by the change.

Other Notable Spring ’24 Release Updates

Marketing App is being Renamed

If you typically use the out-of-the-box Marketing App to access your Campaigns, Leads or Contacts, you’ll notice that the all has been renamed to ‘Marketing CRM Classic’. There doesn’t seem to be any change to the features available beyond the name change, though.

Get Help Understanding Salesforce Spring ’24 Release Enhancements

Contact the team at Sercante to get help implementing these enhancements in your Salesforce org. And leave us a comment below to let us know what you think about the Spring ’24 Release.

Original article: Salesforce Spring ’24 Release: Platform Highlights

©2025 The Spot. All Rights Reserved.

The post Salesforce Spring ’24 Release: Platform Highlights appeared first on The Spot.

Dreamforce 2023 has come and gone, and wow, it did not disappoint. Not only was this my first Dreamforce, I had the honor of co-presenting the Marketing Cloud Release Highlights session with two amazing members of Salesforce product team:  Ruth Bolster, product marketing manager, and Whitni Freeman, lead solution engineer.

In this session, we covered key Winter ’24 release highlights across each of the Marketing Cloud products:

• Data Cloud
• Intelligence
• Engagement
• Account Engagement 
• Personalization

Here’s a recap of the Marketing Cloud Winter ‘24 release features covered…

Highlight #1: Segment Intelligence (Data Cloud)

A new Data Cloud for Marketing feature, Segment Intelligence connects and harmonizes customer and marketing performance data — like revenue data, first party data, as well as paid media data — so you can understand how your segments are interacting with your marketing.

Using out of the box dashboards, you can see how segments are performing across channels, and gives you an executive understanding of how segments are performing across channels.

Plus, you can use Einstein to optimize existing segments, or create new ones based on performance data.

With all that data in one place this allows marketers to have a more holistic view of how segments are doing, without being bogged down by time consuming data management and reconciliation. And having those insights to optimize channel performance by segment – that level of visibility and adaptability means more impactful and relevant marketing campaigns, which leads to better marketing ROI. 

And the built in dashboards and connections means that marketers can get started right away!

This feature will be available for select customers starting in October, and will be available to all customers later this winter. 

Highlight #2: AI-Powered Segment Creation (Data Cloud)

Another Winter ‘24 feature for Data Cloud for Marketing is Segment Creation. Powered by Einstein, this allows marketers to build complex segments using a descriptive prompt. 

So, for example, I can just tell Einstein “Big spenders in North America who made a purchase in the last 3 months and love hiking”, and it will generate the segment for me, showing what that segment looks like, and the attributes used.  

This means that marketers can build their segments without having to be a data scientist to do it. Being able to pull data based on specific criteria has often required technical knowledge of the data model to know where to look, and SQL skills to query the data to know how to access it. This feature will allow marketers to be more self-sufficient to get the data they need when they need it. 

This will be Generally Available in October for Data Cloud Customers.

Highlight #3: Intelligence GA4 Connector (Intelligence)

As of Winter ‘24, Marketing Cloud Intelligence will have a built-in GA4 connector and pre-defined data sets available to ingest GA4 data. Marketing data is the foundation of Marketing Cloud Intelligence. Its data models, dashboards and guidance are built for marketers. There are already more than 100 native connectors available, and now with GA4 data connector this is a natural addition to the platform to have relevant marketing data in one place.

How this will work: When setting up data streams, GA4 properties will appear under the ‘Website’ dropdown. These new properties will be supported in API connectors as well as Marketplace apps.

Marketplace apps will replace previous UA 360 websites and support the new GA4 web properties, dimensions, and other fields for data retrieval. 

One thing to keep in mind: Due to the differences between GA4 and UA properties, the new connector will pull different, yet very similar, datasets into the platform when the GA4 property is selected, so your visualization may need to be tweaked when setting up the data stream for the first time. Marketplace will discontinue support of UA360 properties after the GA4 support begins. 

Highlight #4: Trigger Action on GA4 Data (Engagement)

Marketing Cloud Engagement has some goodies in the Winter ‘24 Release as well. The first is Google Analytics 4 Integration, which lets marketers activate journeys based on Google Analytics 4 segments and events.

This new integration will include two key features in one:

• Visual dashboards embedded within Engagement reporting so that marketers can see real time impact on revenue, AOV, and conversion metrics. 
• Audience activation, which allows marketers to create engagement and re-engagement campaigns based on customer interactions using that GA4 data.
  • So for example, if you had a customer that viewed your product pages for backpacks and hiking boots, then abandon the session, you can use audience activation to trigger an abandoned browse journey.  This also allows you to get cross-channel insights across mobile, web, and email.

There is a fully paid version which includes both Reporting and Audience Activation.  There is also a free version that will feature the Reporting feature only.

Highlight #5: AI-Powered Email Content Creation  (Engagement)

AI is coming to Marketing Cloud Engagement with Email Content Creation, including Typeface partnership!

Marketers can set up and specify personalities with brand voice and tone, and using natural language prompts can get draft ideas on subject, body copy and images. With the ability to give feedback on what works and what doesn’t this lets the model learn and improve over time.  

Marketers can consider this a tool to help them get a first draft in place. They still have control over the content throughout. They’re given choices based on their prompts, which they can use, like or dislike. 

That human element and judgment is a crucial part of the whole process.

Content Creation will be available in Marketing Cloud Engagement this October, and it is currently scheduled to be in Marketing Cloud Account Engagement next February

Highlight #6: Transfer Assets from Sandbox to Production (Account Engagement)

Speaking of Account Engagement… With the Summer ‘23 Release  we saw the ability to move assets between business units, which is fantastic! But that still left a gap with sandboxes. Anyone that has used Salesforce sandboxes has been used to building and promoting configurations, and unfortunately that hasn’t been possible with Account Engagement sandboxes, which has been painful to work around. Any assets built in a sandbox had to be built again in production, which is of course time-consuming and also prone to error if something is missed.

In the Winter ’24 release, marketers can now copy assets from sandbox to production using Salesforce Flow. After installing the flow on your campaign, all you need to do is select your sandbox environment and your production environment, select your assets, and then copy it over. And this supports 8 asset types, including email templates, dynamic content, form handlers, custom redirects, custom fields, landing pages, and more.  

This allows for a more useful Account Engagement sandbox, to perform all asset testing and avoid conflicts – and all that test data – when trying to build in production. Not to mention saving time because you won’t have to build assets multiple times. You can even use this to set up a QA process, giving a subset of users access to build in the Sandbox only and then have another subset of users review the assets and push them to production when approved.

This was first mentioned in Erin Duncan’s post on Winter ‘23 Highlights for Account Engagement. 

Highlight #7: Real-Time Event Stream (Personalization)  

With Winter ‘24 Release, Personalization will now include Real Time Customer Event Stream, a Lightning component that can be added to record pages, giving users a real-time view of the marketing assets that a lead or contact has interacted with. 

This gives sales and service teams better insight into the types of content their customers have been engaging with. They can then have more relevant and informed conversations with them about their current needs and interests, and provide a better overall customer experience.

Learn more about the Marketing Cloud release highlights

If you want to learn more about the Marketing Cloud release features covered, here are a few resources:

• Dreamforce ‘23 Marketing Keynote
• Winter ‘24 Release Feature Demos
• State of Marketing Report
• Marketing Cloud Release Notes – Winter ‘24 Release Notes are expected to drop September 25th.

What do you think about these Marketing Cloud release highlights? Let us know in the comments.

Original article: Dreamforce Session Recap: Winter ’24 Marketing Cloud Release Highlights

©2025 The Spot. All Rights Reserved.

The post Dreamforce Session Recap: Winter ’24 Marketing Cloud Release Highlights appeared first on The Spot.

It’s that time – Salesforce Winter ‘24 release notes are out! Here are the key Salesforce platform features marketers and Salesforce admins should know about.

20 Platform Highlights from the Salesforce Winter ‘24 Release

Highlight#1: Migrate to Hyperforce with Hyperforce Assistant (Generally Available)

If you haven’t heard, Salesforce is undergoing a modernization of their infrastructure with Hyperforce, and undertaking steps to move customer orgs to Hyperforce. To help prepare for the migration, Salesforce has made their Hyperforce Assistant generally available, and updated with improved features to help orgs get ready for the move.

If you’re starting your journey to make the jump to Hyperforce we have more details here: Prepare Your Salesforce Org for the Migration to Hyperforce

Permissions & Record Access

Highlight#2: Report on Custom Permission Set and Permission Set Group Assignments

This is the first of many ideas that were delivered in this release. With this update you can create a report type that you can use to report on which users are assigned specific custom permission sets or permission set groups, or look at all of the assignments by user. This is just for custom permission sets and permission set groups, no word yet on when this would be available for standard permission sets and standard permission set groups.

Highlight #3  What’s Enabled in a Permission Set More Easily (Beta)

Admins who have spent so much time trying to uncover the permissions included in a permission set are going to love this. Another idea exchange request, it’s now easier than ever to see the enabled object, user, and field permissions on one page. You can even see the permission set groups a permission set is included in!

Highlight #4 User Access Policy Filters Improved (Beta)

Until now you could create User Access Policies referencing only one permission set, permission set group, or managed package license in your user access policy filters. With this update you can reference a total of three, giving you more flexibility to define your policy criteria.

What to know more about User Access Policies? Jason Ventura covered this in the post Salesforce Summer ’23: User Access Management Updates 

Highlight #5 Report on Who Has Access to Accounts from Manual Shares and Account Teams

Admins and users will have a new way to understand better who has Read or Edit Access to an Account through Account Teams or Manual Sharing. By creating a report type it’s now possible to see which users and groups have access. Another idea was delivered!

Highlight #6 Report on Public Group Members

Another helpful report that’s going to save clicks! With this new custom report type, Admins will be able to more easily view which users, roles or groups are members of public groups.

Automation Updates

Highlight #7 Reactive Components now GA

With the general release of reactive flow screen components, admins will able to build more interactive single page applications, creating a more dynamic user experience.

Highlight #8 Create Custom Error Messages in Record-Triggered Flows

Another Idea Exchange idea delivered! Flownatics everywhere will be cheering for this. Now admins can customize the error that users see on record triggered flows. You can control one or more messages that will appear, what the messages will be, and when you want them to appear. You can even set them to appear as a window on the record page, or as an inline error on a specific field, similar to validation rules.

In the example below, you can see the Custom Error message element where I’ve configured 2 messages to appear if an opportunity has been created or updated and the stage is advanced and no Opportunity Contact Roles are found. One error will appear in a window on the record page, and the other will appear inline on the Stage field.

When active, the flow will display the configured error messages when the criteria has been met:

Highlight #9 Transform Your Data in Flows (Beta)

This is a new element for flow that lets users map data from a data source to a new target data destination. This can follow the HTTP Callout action that grabs data from an external location, and transforms the data before saving to a Salesforce object. Another use can be to transform field values while mapping from one object to another.

Highlight #10 Save a Flow Without Configuring Some Elements

How many times have you started to build a flow and have partially added elements, only to find you have to exit an element before fully completing the configuration. In the past you had to lose the partial configuration already completed, or add dummy data just to get the element to save, and remember to go back and update later. With this new feature, you now exit Start and Create Record elements before fully configuring them. According to Salesforce this is the “first steps to support saving a draft of a flow at any point in the building process”.

Highlight #11 Use Wait Elements in More Types of Flows

Marketers would be familiar with the ability to add a wait step in a customer journey (Marketing Cloud) or Engagement Studio Program (Account Engagement). The new Wait for Amount of Time and Wait Until Date elements are now available in schedule-triggered flows, autolaunched flows, and orchestrations. This adds more flexibility to being able to pause a flow interview for different use cases. The previous Pause element has also been renamed ‘Wait with Conditions’ for clarity.

Highlight #12 Flow Builder user interface moved to right panel

The element properties are now displayed in a panel on the right side of the screen instead of as a popup. So far this appears to be working for Start, Get, Create, Update, Transform (Beta), and Delete.

Highlight #13 Data Cloud Triggered Flows

For orgs with access to Data Cloud, you will be able to create new Data Cloud-triggered flows from the new Flow screen. After selecting Data Cloud-triggered flow, you will be prompted to configure your Start conditions specific to your Data Cloud object.

Highlight #14 Get Data Cloud Records More Easily in Flow Builder

Another Data Cloud related enhancement, admins can more easily choose between Salesforce objects and Data Cloud objects. Based on the choice more options are provided to specify the criteria.

Highlight #15 Use Filters to Find Record-Triggered Flows Quickly

Orgs with increasing numbers of flows will benefit from this handy additional filtering capability that lets you zero in on the flows you’re looking for. You can now filter on flows by Status, Package State or Process Type.

Highlight #16 Migrate to Flow Updates

In the meantime, admins still working on moving legacy automations like workflow rules and process builder to flow may appreciate that the Migrate to Flow tool has been updated to accommodate more use cases:

• Migrate Workflow Rules with Pending Time-Based Actions to Flow
• Migrate Process Builder Processes with Custom Metadata in Formulas to Flows

If you’re in the process of migrating your workflow rules and process builders to flow, have you checked out our guide and tools to help with that migration? Check out Automation Facelift: Migrate Workflow Rules and Process Builder to Salesforce Flow

Cool Admin Updates

Highlight #17 Visualize Lightning Reports with Summary Formulas as You Create Them

I don’t know about you but I still struggle with using PARENTGROUPVAL or PREVGROUPVAL. In Classic there was a great feature that helped build the summary with these functions, and showed how they would work in your report. Now this feature is available in Lightning!

Highlight #18 Select Who Has Access To a Sandbox

When creating or refreshing a sandbox for your team to build or test a new configuration any active user in production could access the sandbox. Now, admins can limit access to specific users by adding them to a group. This then freezes all other users in that sandbox, so they can’t access it (unless you unfreeze them). Only the users in the group will be unfrozen automatically. And the “.invalid” won’t be added to their email addresses either. Bonus! Now, apparently this may not be immediately available when orgs are upgraded to WInter ’24. According to the release notes, this will be available “in production orgs when they’re upgraded to the Winter ’24 release starting in mid-October 2023.”

Highlight #19 & 20 Lead & Contact Intelligence VIews

Last but not least…. As part of Winter ’24 release, orgs will now have access to a more actionable lead and contact lists that can help users segment their leads, and take action to build their pipe and grow customer relationships. In one page you can create segments and view key metrics, prioritize important records, view activity history of individual records and make calls or send emails without leaving the list.

• Lead Intelligence View
• Contact Intelligence View

Other Notable Updates

• Mass Quick Actions on Related Lists (Generally Available)
• Dynamic Forms Experience on Mobile (Generally Available)
• Send Salesforce Data to an External Server Without Code via HTTP Callout (Generally Available) – also includes PUT, PATCH, and DELETE methods
• View Slack Channel Recipients in Subscription Reports
• Show Salesblazer Content in the Guidance Center
• Activities captured by EAC now reportable
• Salesforce Maps Lite to View Customers and Prospects
• Transfer Ownership of Lightning Dashboards (Beta)

Which Salesforce Winter ‘24 features are you excited about? Let us know in the comments!

Original article: Salesforce Winter ’24 Release: Platform Highlights

©2025 The Spot. All Rights Reserved.

The post Salesforce Winter ’24 Release: Platform Highlights appeared first on The Spot.

The introduction of Hyperforce is one of those revolutionary milestones for Salesforce customers. That’s because migrating to Hyperforce is going to give Salesforce customers options when it comes to storing their Salesforce data.

If you’re a Salesforce customer, then you likely store Salesforce data in one of the company’s massive data storage centers. With Hyperforce, Salesforce customers can store their data in public cloud storage centers.

This is huge for companies that operate globally as well as ones in highly regulated industries like financial services and healthcare. That’s because it’ll be easier to store data locally and comply with regulations surrounding data storage in countries around the world.

What is Hyperforce?

First introduced in 2020, Salesforce reimagined its platform architecture for the public cloud with the introduction of Hyperforce. It’s code-based rather than hardware-focused infrastructure that allows more agility within the platform. 

The Customer 360 platform can live on top of Hyperforce, and Salesforce customers will store their data in public clouds like Amazon Web Services (AWS), Google Cloud, and Microsoft Azure, inside onsite servers, or within Salesforce data storage warehouses.

Migrating to Hyperforce

So, why is Salesforce having all customers move to Hyperforce? Well, for one thing, it’s a modernization of the platform to meet changing data demands. 

Salesforce will continue to maintain data warehouses they own to use when needed, but moving data to public cloud infrastructure is the most logical way forward. Imagine having better compliance capabilities, top-notch security, ultimate agility, and the power to scale up like a superhero. 

 Salesforce is all about respecting your privacy, too. So with Hyperforce, they’ve got your back.

• Worldwide Wonders with Data: Hyperforce is like your personal travel agent for data. Go global while keeping control over where it hangs out — that’s a win-win for you and your customers.

• Scaling Superpowers: With Hyperforce, growth is more than a dream — it’s a reality. Flexibility and sustainability are your new BFFs.
• Fort Knox Security: Locking things up tight is Hyperforce’s jam. We’re talking about security measures that make your data sleep soundly, including encryption and zero-trust principles.
• Privacy Party: Hyperforce comes with its own set of privacy standards, giving you the reins and a spotlight on your customers’ data.
• Agile Adventures: Who needs downtime? Not us! Hyperforce keeps the party going with seamless releases, environments for testing and development, and an easy-peasy AWS connection.

How do I know it’s time for me to migrate to Hyperforce?

Currently, there is no publicly available migration schedule for Hyperforce, Salesforce is ‘regularly moving customers to balance our workload and modernize our systems.’

Admins of orgs scheduled to migrate will be notified via a Salesforce Product and Service notification, approximately two months and then one month before their migration date. In the meantime, you can check in with your account team to find out when you can expect to receive a notification that it’s time to migrate to Hyperforce.

Below is an example of the product notification Salesforce customers receive:



Learn more about Products & Services Notifications

If you’re notified that you are being migrated but the timeline is inconvenient for your team, you can contact your Salesforce account team (according to this FAQ article).

How to prepare for Hyperforce Migration?

Salesforce has implemented the Hyperforce Assistant in Setup to guide you through your upgrade. The Assistant has all of the latest information and checklist to prepare for the migration. 



For additional information, see the section What can customers do to ensure a smooth upgrade to Hyperforce? in the Hyperforce FAQ article. You can also request a trial org from your account team so you can test your setup and troubleshoot before you make the switch.

Get ready for to migrate to Hyperforce

It’s a matter of time before all orgs are migrated to Hyperforce. So in the meantime, start to think about how data storage location may affect your Salesforce org. For example, the move may affect endpoint things like Single Sign On, OAuth and JSON Web Tokens (JWT). 

Reach out to the team at Sercante to evaluate your data architecture and business goals to see how the migration to Hyperforce may affect your Salesforce org.

Original article: Prepare Your Salesforce Org for the Migration to Hyperforce

©2025 The Spot. All Rights Reserved.

The post Prepare Your Salesforce Org for the Migration to Hyperforce appeared first on The Spot.

Salesforce opportunity record pages are great for displaying all of the key information about a particular record. But, what if you need to be working with and updating multiple related records at the same time, without flipping back and forth?

That’s where this hack for displaying account fields on Salesforce opportunity record pages comes into play. 

Salesforce Opportunity Record Page Example

Let’s say a sales rep is working on an opportunity, but some of the fields they need to see and update are on the account. 

If they only needed to view the information, using custom formula fields on the Opportunity referencing Account fields would have been sufficient. Because they also wanted to update this information while they were on the Opportunity record, an alternative option may be using an Object Specific Action with the Lightning Record Page.

How to Create an Object Specific Action

1. From Setup, go to Object Manager > Account > Buttons, Links, and Actions
2. Click New Action
3. For Action Type select Update a Record
4. For Label, enter a label that is appropriate for this purpose. For example ‘Update Account Details’
5. Enter a Description outlining the purpose of this action. For example ‘Displays Account details to users from Opportunity record page’
6. Click Save.

Edit the Action Layout

This is the key! This is where we decide what fields to display, and how they will be arranged.

1. Once you have saved, you will be looking at the Action layout.
   • Note: you can also access this later from the Action page by clicking on the Edit Layout button.
2. Just like a page layout, drag and drop the fields that you want to be visible.

3. Click Save.

Add the Account Action Layout to the Opportunity record page

Now that we have the Action Layout we want, here’s where we connect it to the Opportunity. 

1. From Setup, go to Object Manager > Opportunity > Lightning Record Pages.
2. Select the Lightning Record Page you want to update.
3. Drag the ‘Related Record’ component where you want it on the page.
4. In the Related Record settings panel on the right, update the following:
   1. Header Label = the heading that will appear at the top of that layout on the page
   2. Lookup Field = Account
   3. Update Action = the name of the action you created above
5. Click Save.

Now when looking at an opportunity, the related Account fields will appear on the Opportunity record page!

Editing Account Fields on the Opportunity Page

Unlike formula fields, these fields can be edited directly from the Opportunity. 

To edit the Account fields, click the pencil icon next to the Account field you want to edit. All of the fields in that section will become editable, and notice that the Opportunity fields are not. When done, click the Save button to save the fields in that section. These fields are edited separately from the Opportunity fields. 

Find Key Account Details on the Salesforce Opportunity Record Page

That’s it! Now the sales team can manage the key details on their Account and Opportunity in one place. All with a handy object-specific action layout and the flexibility of a Lightning record page.
Want to know how you can use this tip in your overall technology strategy? Reach out to the team at Sercante to start a conversation.

You can also check out these resources for more ways to make work flow between your sales and marketing teams:

• Why Salesforce and Marketing Admins Work Better Together 
• Why Should Marketing Admins Have Salesforce Access

Original article: Displaying Account Fields on a Salesforce Opportunity Record Page

©2025 The Spot. All Rights Reserved.

The post Displaying Account Fields on a Salesforce Opportunity Record Page appeared first on The Spot.

With Salesforce moving to Flow as its go to low-code automation tool, and Workflow Rules and Process Builder planned for retirement, it’s a good idea to migrate your existing automations to Flow. Here are best practices to get started on this process BEFORE you begin migrating.

Reviewing Your Current Automation Stack

Depending on how old your org is, it may have a lot of legacy configurations from old or obsolete business processes that don’t mean anything for your organization today. Do you really need to bring all of that technical debt along in your migration process? Or would you rather have an opportunity for a fresh start with your automations?

Before jumping in and migrating all of your current automations, this is a good opportunity to develop a migration strategy so that the changes being made now will meet the current and future needs of your organization. 

Develop a Salesforce Flow Migration Strategy

STEP 1: Audit your current workflow rules and process builders

First, inventory your list of workflow rules and process builders and perform an analysis. Here is a template you can use for your audit (click File > Make a copy).

When looking at your current automation, consider the following questions:

• Which automations are active?
• What automations are still relevant?
• How many automations are there per object?
• How complex is each automation?
• Can any automations be combined?
• Which automations make updates to the same record that triggered it?

STEP 2: Decide Which Automations to Migrate

After completing the audit, you will have a better idea of the automations in your org, which are still relevant and need to be migrated, and which can be decommissioned. 

This is also a great time to decide on which you will consolidate. Candidates for consolidation are:

• Automations on the same object with the same trigger criteria. For example if you have 3 workflow rules that trigger from a Lead Status change, these may be a good candidate for combining into a single flow.
• Automations that include field updates on the triggering record.
• Automations that have similar components that could be combined into a subflow that’s called from each flow.

STEP 3: Prioritize Your Migration Plan

As you assess the automations in your org, you will become aware of those that are critical vs nice to have, and which can be combined into a single well performing flow. Use this understanding to prioritize the workflow rules and process builders you want to tackle first.

STEP 4: Get Familiar with Salesforce Flow

If you’re not familiar with Flow, and the types of flows available, this should be your next step before jumping in, to help make informed decisions about your flow strategy.

There are many resources available to help you get started.

You can check out my recent blog post for more information and links to a few great resources. Or this one from Mike Morris that outlines a process to manage Salesforce campaign activation with Flow.

STEP 5: Decide on a Flow Strategy

Ok so you know what workflow rules and processes need to be migrated and which to tackle first. So how are you going to actually migrate them? 

Salesforce Migrate to Flow Tool

• Salesforce provides a Migrate to Flow Tool to help with the process of migrating current Workflow Rules and Process Builder to flow.
  • Support for migrating Workflow Rules is generally available as of Summer ’22.
  • Support for migrating Process Builder is coming and estimated early 2023.
• The tool is very easy to use and does pretty much all of the lift in the migration process, creating the flow with start criteria and each action, and even makes it easy for you to deactivate the old and active the new.
• One consideration is that the current version of the tool will migrate each workflow rule into its own flow. So if you have 20 workflow rules and use the tool to migrate you will end up with 20 flows. Will this work for your org?

Third-Party Migration Tools

• The UnofficialSF site has a tool called ConvertToFlow v2 that can be used to convert Workflow Rules and Process Builder. I personally have not used it but it has been recommended in the community.

Building Flows Manually

If you have identified automations that can be combined, or are migrating process builders, you will no doubt build some flows. Before clicking that New Flow button, decide on:

• Will this be a ‘Before Save’ vs ‘After Save’ record-triggered Flow?
  • Will the flow make an update on the same record that triggered the flow? If yes then a Before Save flow may be the best fit for better performance.
  • Will this flow be invoking an action or creating/updating related records? Then you will want to create an After Save flow.
• Is there an existing flow with the same entry conditions? Can it be updated to include the logic you are currently migrating?
• Is there an existing flow that has the same components involved? Can those components be converted into a subflow to be used in each of the flows?

Step 5: Build your Flow(s)!

Now that you have completed all of this awesome prep work, you are ready to roll up your sleeves and get building!

Questions about using Salesforce Flow? 

Let us know how you’re using Salesforce Flow in the comments section, or reach out to us with any questions.

We’re here to help!

Original article: Automation Facelift: Migrate Workflow Rules and Process Builder to Salesforce Flow

©2025 The Spot. All Rights Reserved.

The post Automation Facelift: Migrate Workflow Rules and Process Builder to Salesforce Flow appeared first on The Spot.