Play
Show Navigation
Show Transcript
00:00
Play
Seek 10 seconds backwards
Seek 10 seconds forward
00:00 / 01:14:53
Mute
Disable Captions
Settings
Picture in picture
Fullscreen
Search in video
You can search the video captions for specific words or phrases.
Popout transcript
Hide Transcript
Skip transcript
Welcome to Release Readiness Live.
It is important to watch Release
Readiness live so that you get
a snippet of the coming attractions
of the functionality.
That's coming from Salesforce.
We really focus on the features
that are going to be most useful
and impactful with release readiness.
Why have you got the great opportunity
to actually hear it from
the mouths of the people who spend
a lot of time thinking about what exactly
you all are Salesforce developers
and admins, or actually wanting to see
your feedback is so important.
I think that's
one of the most amazing things
actually about the Salesforce
ecosystem, is how involved
trailblazers
are with evolution of our products.
Is really about to start.
Let's get started.
Welcome to Release Readiness
Live from San Francisco.
I'm Julian Bruce, director of developer
marketing at slack and self-proclaimed
Salesforce Super Nerd,
which means I am so honored
to bring Release Readiness Live to you,
because this is where we get to get nerdy
and cover the new product innovations
coming your way in the next release.
But before I get into my happy Nerd zone,
I need to remind you to only make
purchasing decisions based on currently
available features and functionality.
Now with
that covered, I want to say thank you.
Thank you so much for joining us today.
We want to thank you
for investing your time to be with us,
to learn about
what's coming up in the summer 24 release,
and thank you for all the feedback
you provide us.
The feedback you provide us
is what helps our technology teams really
build solutions centered around
your experience.
We've got a great lineup of release
readiness content for you this week.
Right now we're going to learn about the
latest innovations from Salesforce Flow,
a personal favorite product of mine.
And earlier today we covered Sales Cloud
and they shared
what's new in the Sales
Cloud features area.
Now, if you missed any portion
of the show, you can watch on demand
right here on Salesforce.
Plus some of what we covered
earlier on Sales Cloud.
Or if you want to go back and watch
something that you're about to see here.
Now tomorrow, come on back
because we've got the Developer Preview
and CRM analytics.
And then on Friday we're wrapping up
with our Admin Preview and Service Cloud.
You can add any of these
individual sessions to your calendar.
Or you can just hang out here with us
for all three days.
Now we're going to spend the next hour
together with our product managers
here in the studio, who will be giving us
live demos highlighting the top flow
features in the summer 24 release.
But it's not just about us here
in the studio, it's about you.
We want to answer your questions
about all of these new features,
so ask your questions in the chat
right here on Salesforce Plus,
where we've got product experts
standing by to give you answers.
And we'll also be taking your questions
live here on the show
for our product managers
that are here in the studio.
Now let's get started.
First up we have Connor Turco,
Associate Product Manager here to show us
how you can simplify your flows
using the power of Einstein.
Connor, take it away.
Hi everyone.
I'm so excited today
to be sharing with you
our new beta product, Einstein for flow.
Einstein for flow
allows admins to easily create flows
from natural language prompts.
All you need to do is write a description
of what you want Einstein to build,
and magically watch the flow appear
before your eyes.
We built Einstein for flow
with two main user groups in mind.
First of all, admins who are trying
to learn flow often struggle
because of its complexity
with Einstein for flow.
These admins can easily learn flow
by not having to get into the weeds
or the nitty gritty.
Einstein handles
all of the complexity for you.
You can focus on the general structure
and logic of the flow
without having to get
into all of those details.
For our admins
who are more experienced with flow,
Einstein for flow provides
a valuable starting point
so that you don't have to start
from scratch, saving you valuable time.
Einstein for flow will be going beta
this summer.
Don't panic
if you don't see it in your org yet.
Just keep an eye out over the next
few weeks for an official release date.
It will be bating to customers
who have purchased the Einstein
one sales service or platform add on,
and we will be baiting with support
for custom and standard objects.
You can use Einstein for flow
to generate flows of 3 to 6 elements.
In addition to these exciting Einstein
for flow beta announcements.
We also have some exciting UX enhancements
coming to our flow users as well.
And this isn't just to those
who have purchased Einstein for flow.
This is also to all flow users as well.
So these UX enhancements
make it a lot simpler
when you start the flow creation process.
That new modal is a lot simpler
and easier to understand.
A lot less information on there
to make it easier for you
as the customer to create flows.
So let's actually get into a demo
and you can see all of this in action.
So I'm starting here on the setup page.
And from here I can easily
just create a flow like I normally would.
And you'll see here
that this new flow creation modal makes it
a lot easier for you to create a flow.
It's a lot simpler.
You don't have all of this information
that used to be on the old modal.
You just have three simple options.
You can create a flow from scratch, use
a template or let Einstein help you build.
So I will select
let Einstein help me build.
And you'll see here
that there are instructions for
how to best craft your prompt.
there's also sample prompts here.
So if you just want to play around
with Einstein for flow.
Not exactly sure what it is
you want to build off the start,
you can use one of these sample prompts
to get started with the product.
But I have a prompt here
that I'm going to paste in.
I'm going to ask Einstein to create
a screen flow that collects a case,
subject and description,
and provides a pick list
to set the status
to the values of the k status field.
Then create a case record.
So I want Einstein to create a flow
that takes in some information,
and then uses that to create a new case
record.
And one thing that I want to call out here
is how important it is
to be really detailed with your prompts
that you give Einstein.
So you'll see here
I've been really detailed in the steps
that I want Einstein to take in this flow.
And I've also specified here
the type of flow that I want to create.
I specifically said that
I want a screen flow.
So the more detailed you are, the better
the output that you're
going to get from Einstein.
So I'll click Create Draft Flow here.
And it's going to take a few seconds
for Einstein to generate this flow.
One really exciting thing about this
product is that this is actually built
on our own internal cogen model.
So we're not using OpenAI
or any other third party LMS.
We have an AI research team
who's been working year round
to build a custom model
that's specific to generating flows.
And it's also exciting to call out
that we've have internal,
employees here that are actually building
the training data for this model.
So this isn't trained on your customer
data.
We've actually gone in
and built thousands of flows
that this model has been trained off of.
So you'll see here
Einstein has generated a flow for us.
There is a few key differences on the Flow
Builder
screen that you'll notice
when you generate a flow with Einstein.
First of all, we have this banner here
that says this flow is created
by generative AI.
It's important to note
that Einstein can make mistakes.
It's not always perfect.
And so it's always important
to have a human in the loop
to review these flows for correctness,
to make sure that you know
they're touching your customer or data,
you want to make sure
that they're correct.
You'll also notice this docked composer
here in the bottom right corner.
Here you can see the original prompt
that I entered to generate this flow.
We have this little clipboard icon here
that will copy that
prompt to the clipboard.
So if maybe you want to paste that prompt
and save it to use later again,
or maybe tweak the prompt to try,
you know, different prompt variations
to see what produces the best output
can easily copy it to your clipboard here.
I can also click Start Over and if I click
that, it will pop open in a new tab.
That start of that flow creation process
that I showed you earlier.
So these two buttons can be really useful
in unison if,
say, maybe you want to try different
variations of a prompt.
For example,
you can copy the original prompt,
maybe tweak it a little bit and see
which one produces a better output.
You'll also notice we have this
thumbs up and thumbs down here.
This feedback is really important to us
to helping us improve the model.
So if I click thumbs down,
it actually asks me for a few more details
about why the flow didn't meet
my particular standards.
And this feedback helps us
to improve the model further.
But let's actually take a look at the flow
that Einstein created here.
So just like I asked, did create
a screen flow and taking a look at that
first screen, it takes in a case subject,
a case description, and a case status.
And it uses that information
to then create a case record.
So this particular flow
did everything that I wanted it to do.
So I can go in here,
give it a little thumbs up.
And just like any other flow
that I would typically create this flow,
I can go in and edit it.
I can, you know, add elements,
change things and eventually save
and activate it to my org.
So this is a super valuable tool
for our admins to give them
a starting point to ultimately save them
time in this flow creation process.
How cool is that, Julian?
Okay, it's so cool. Connor.
You have no idea if I had this
when I was first starting to learn
how to do flow, I would have been
so much more excited at the onset.
This is a game changer.
I mean, it really makes it so much easier
to really not be distracted
by, like you said, all of the details
and the individual elements
and how flow works at that
tiny like that really detailed level.
You can start at kind of like,
I want a flow that does x, Y, and Z,
and you can experiment with the prompts
to see what you get back,
and then that you can learn from seeing
what Einstein creates from you.
Exactly.
I love that.
So, we have a lot of questions
because people are very excited.
And reminder for all of you tuning
and you can,
ask your questions
live in the chat right now.
Not only do we have Connor, an amazing
lineup of product managers joining us here
in the studios, but we also have,
I know, some amazing experts in the chat.
I know we've got Adam
White, we've got Diana Jaffe in there
waiting to answer your questions as well.
So feel free
to let those questions flow in the chat.
and also thinking of questions, we also
have some people that are very excited.
So, I know Andrew,
you have high hopes for themed outfits.
Stay tuned. Forward looking statement.
And, Mark Jones is very excited.
He says getting started with, Salesforce
viral for flow is always my favorite
release readiness live session.
It's mine too. It's going to be so good,
I promise. Mark, we'll make it.
We'll make it worth your time.
But let's get into some questions.
So, Connor, we're going to talk a little
bit about using prompts to build flow.
Very powerful.
Can you talk a little bit
how to write a good prompt.
And what are some best practices
for writing a prompt for Einstein?
Definitely.
So when we actually train the model,
we train it on a lot of prompts
that start with the word create
or generate a flow.
And so starting with those words generally
also produces a really good output
and specifying, you know,
what type of flow you want to build.
So if you want to build a screen flow
like I showed in the demo, create
a screen flow or generate a screen flow
if you want to auto launch flow
starting with those words to make it clear
to the model, you know what, type of flow
it should build is really useful.
And then really
just being as detailed as possible.
If you're not super detailed
and explaining
how you want the flow to be built,
it generally is going to not produce
output that you're happy with.
So being really detailed,
specifying the object names specifically.
So naming the object name or the API
name for that object that you're
referencing will generally produce
better output as well.
So really the more detail
you can put into that prompt,
the better the output is going to be.
That makes sense.
Well,
and you know,
you also showed how important
it was to really review
what Einstein provides you
and to really kind of make those edits,
make sure it's doing what you asked it to.
okay.
we have some more questions.
Oh, here's a good question.
Can I use Einstein Flow to send emails?
Yes you can.
So it does currently support
email templates right now.
so yep,
you can easily ask it to write an email
to an account owner
or something like that.
And it will, generate a email template,
which it will use to
then send the email, music
to the ears of many admins.
I can hear them right now. okay.
We have a question from Salesforce.
Plus, this is from Andrew.
This is for you, Connor.
Why does the generative AI flow
not have descriptions on the elements?
Seems like a perfect use case
for having descriptions.
Well, yeah for looking statement, but
we definitely want to add that in later.
right now
it does not currently support that.
It will write a description in
for the actual overall flow,
but not for the individual elements.
in the future we would definitely
like to add support for that.
That's something that a lot of our admins
have specifically called out as something
that would be very useful to them.
Yeah, we always like to say,
especially as many years in, admin world
myself, that description field
is so important because specially
when you're working on a team,
you're trying to figure out, like who?
Why did someone build this?
What does it do?
So that's great.
Good to know that it's it's being thought
about carefully by your team.
okay.
We have another question from Salesforce.
Plus this is from Kevin.
Kevin is asking,
Will Einstein be able to read
flows and create a summarized
documentation of what that flow does.
So we kind of talked about this. Yes.
That's another highly requested feature
that we've heard.
we're aiming
to actually have that next release.
We'll see for like a forward
looking statement.
but we, we've looked into,
you know, how you would do that
and we've had some really promising
results so far.
So we really do
want to bring flow summarization in
so that you can actually go into your org
and you know, look at,
you know, what each flow in the org does.
That's been a big complaint of our admins
is they have hundreds, sometimes
thousands of flows.
No idea what all of them do,
especially if you're new to a team.
So definitely looking
to bring that support in the future.
I'm imagining a world
where you inherit an org as an admin
and you just turn Einstein flow on
and you say,
tell me what
all of these hundreds of flows do,
and you get this wonderful
little description for every flow.
Yes, that's
exactly what we're trying to build.
Okay. All right.
So forward looking statements.
Thank you so much for sharing that.
I am really,
really excited about this innovation.
I know a lot of people are as well.
And we're going to have plenty
more questions for you. But guess what?
We've got more flow content,
so we're going to keep on going.
Up next we have an on program director
of Product management here to unveil
our new lightning automation app to help
you search and organize your flows.
Take it away.
And and thanks, Gillian.
On on their PM on the flow team.
And this is my first time
coming on to flow release in live.
I'm going to cover a few innovations
that are coming
your way in the summer release.
First up is the new automation app.
So this is a new home for flow.
I'm going to show a demo of this
in a few minutes, but this is a new way
where admins can create
and manage their flows.
The top three reasons
why I would want you to give the flow.
The automation app a spin.
the ability to search.
We've seen this all where orgs mature
and you have more
and more flows and you're looking for that
one flow and it's hard to find when.
So just to the rescue now
the second feature within this
is the ability to organize your float.
So giving it
categorization and sub categorization
and keeping those flows well organized.
And finally app builder customization.
Now we've got a lot of innovations
in the summer release, but unfortunately
we cannot highlight and demo all of them.
So I'm going to leave you
with the top three.
according to me, to basically have,
have for you to check out as the summer
release rolls out.
The first one is debug enhancement
for schedule flows.
So within schedule flows
you have the option of bringing a batch of
records now will let you debug that flow
without activating it.
Which means you get to provide a record
that is going to be the input,
for that flow.
And also once this was debug run is done,
you're going to get a summary card
which shows you
the number of affected records
that have been run with the debug run.
Second on the list
is the create element
required fields as screenshots shows.
Here you've got a case record case object
that selected and instantly in the field
two values section, you've got
the required fields populated on the left,
making sure
that as this case record is created,
you're not missing out on populating
any required fields.
Last but not least is matching rules
within create elements.
This is going to help reduce the number
of duplicate records in your org,
and with flow you can also customize
the outcomes whenever there is
a match found.
With that, let me jump into a quick demo
of the automation app.
So this in set up is where are flow?
Users are used to creating
and managing their flows.
You're going to see something new
in the summer release,
which is the automation
lightning app banner.
The way to navigate to
it is by clicking on to the waffle
Autumn, the waffle icon for app switching
and search for automation.
Once you click automation, you're going
to land on the Automation home page.
You see your recently modified flows
quickly
getting to where you left off
and your errand flows.
On the flow list view,
you're going to have.
You're going to have list views,
and you're going to have the ability
to search these, these views.
Okay.
also as I call out
categories and subcategories.
So as you see, most
flows are now categorized by sales service
or whatever else I see fit.
And I also have the ability
to sub categorize my flow.
So some sales flows are three Salesforce
split sales flows
and some are for sales flows.
If I am running into the situation
where I have a lot of flows,
I can quickly search those flows.
And in a matter of seconds, I have
the exact flow that I'm looking for.
That's all.
There are time I had to demo today.
Julian, what do you think
about the automation app?
this is a game changer.
And on. Are you kidding me?
Being able to go into setup
and see everything you need to know
about all of your flows in one place?
Again, I'm hearing so many cheers
virtually through the chat.
That's incredible.
Congratulations. That's a huge innovation.
so we have a lot of questions
though, and people are excited.
As a reminder, please keep asking
your questions right here in the chat
on Salesforce Plus and also share
the things you're excited about.
in fact,
we have, Alex, one of our favorite,
flow champions, stone addicts
out there in the wild is saying
that she's taking an early lunch break
to watch Salesforce Flow.
So thank you, Alex,
for taking a lunch break to enjoy us,
and to enjoy all of these
great innovations with us.
okay. Another question.
talk about record types.
Are they supported for
the required fields feature?
Not today.
So today the the required fields
feature is going to surface
required fields for the core object
and not for architects okay okay.
That's fair.
people are very excited.
here we have a question
coming in from Mark on Salesforce.
Plus for the automation
app in future releases releases.
I'm getting so excited.
I want an app and everything
and future releases.
Can we expect to see enhancements
to what we can do with it?
For example, the ability to see a list of
when the flow has run.
It's like a roadmap. Questions? Yes.
So there is a lot planned around
the automation app.
We're going to announce more,
more like a roadmap
or three release roadmap at Dreamforce.
So yeah, stay tuned for for
more innovations in the automation app.
Release
after release teaser for Dreamforce.
Do you want more?
You got to come to Dreamforce.
Yeah okay. That's fair.
Well I mean your team is working on a lot
and this is something I know
that especially the admin community
has been asking for
and looking forward to for a very,
very long time.
And this is a huge innovation.
Can you tell us, you know, you give
a little hint of to the coming Dreamforce.
You're going to find out more.
But again, forward looking statement.
What are some of the things you're
most looking forward to bringing to life
with this automation app?
We want the automation
app to be the one place where you are
monitoring and debugging
and creating your flows.
So, being able
to look at your different flows,
how they are doing,
staying on top of the metrics that matter.
That's the intent of the automation
app going forward.
I love that your one stop shop
for everything automation.
Yes, that's.
And you have Einstein helped create
all the flows that you can manage
with the automation up.
I see we're on a theme here.
We're building, we're building.
okay,
we've got some more questions in here.
Oh, we've got somebody
who is very excited.
Connor,
this is more about what you showed
Eduardo in the chat is saying that he is.
He says Connor.
Awesome update on Einstein for flows.
It really does make it much easier
to create one or use it to get started.
So feeling some love.
I love that you love the love.
Yeah. That's good, that's good.
so keep the questions coming everyone.
We've got a lot more innovations
and flow coming up your way.
just we've got more love in the chat.
So again, we got Marc in here.
Marc?
Oh, he's asking all the good questions.
he's really dying for a flow of plushie
to be released someday.
Well, Marc, you might not be alone.
Put it in the idea exchange.
Maybe that's
how we can get some support for that.
and then let's talk a little bit more
about kind of how you're viewing you.
You mentioned visions for the future
roadmap, things that you're looking to
really make that automation not be a home
for admin to manage everything.
Automation style.
What's one of the things that your team
has just worked on
or is working on right now?
That is like getting in the weeds
a little bit and pretty exciting.
so I wouldn't be able to share
what we're working on right now.
But the trying I'm trying.
But at the same time,
I do want to open up this opportunity
to invite users when they are taking
the automation app for a spin.
Give us ideas.
Tell us what you would want to see
in the app.
Tell us what we can do better.
Tell us what can make it
the one stop shop for for flow.
So we have ideas, but we want to hear
what you have and then merge the two.
Okay. All right. So keep the ideas coming.
Wanting feedback.
And got to let all of the ideas
flow back and forth.
Yes okay.
Right. Sorry.
This is this is why I love the flow URL.
Because we can really just go to go to the
the nth degree when it comes to bad puns.
okay.
Well anon,
thank you so much for sharing all that.
And I'm sure we're going to have
a ton more questions coming in for you.
In the meantime, we're going to keep going
because there is so much more
to talk about.
So next up we've got Sam Reynard, senior
director of product management
and multiple repeat guest here on URL.
She is going to give us the latest
on how you can build a list of records
with only one screen, with repeaters
and so much more.
Sam, take it away. Thanks, Jillian.
All right, let's talk about repeaters.
I'm really excited to bring this to you
in summer 24 as a GA feature.
We introduced this at our last release
as a beta,
and I was really excited
to see the warm welcome from the community
and all of the feedback that everyone
who tried it out provided to us.
So thank you
to everyone who piped up about that.
If you're new to repeaters,
the idea is to make
the situation on the left not,
the way that you collect
lots of information
about multiple records in flow anymore.
so say goodbye to the.
Do you want to add another checkbox
with a manual
rerouting the user back to that screen
over and over again?
Instead, with repeaters,
we provide a container component for you
that manages
that add remove functionality.
and then allows you to keep
your user on the same screen.
As far
as what is new in summer 24,
we are not just taking what we baited
last released GA,
we are adding a ton of new functionality.
so we're adding support
for almost all components.
So if it is showing up in the components
tab, it is probably supported.
This is going to be any custom components
that you've installed from App Exchange,
unofficial SF or built custom in your org.
Things like look up toggle
email data table.
The only exception is the new action
buttons component
which is currently in beta.
so with that exception,
everything in the components
tab, you can put it inside of a repeater.
And then we didn't just
look at what components you can
add inside of it, but also the other
screen features available
and how that might apply to this, repeater
or sort of feature.
so we brought to you
conditional visibility.
You can apply that across the entire
container
or on individual components inside of it.
Any component that normally supports
help text and input validation
is now supported inside of repeaters.
And we have some reactivity support
specifically with the 1 to 1 field
binding, which was like the first start
that we had at reactivity a while ago.
And you can respond to a reactive formula
from that exist outside the repeater,
right now, you cannot build
a formula that references,
information from inside the repeater.
Yet that is something
that we are hoping to look at.
but I don't yet have a timeline for you.
The one thing I would love for everyone
to walk away from this, though, is,
a general best practice
to get your screen flows up
to runtime API version 58.
this is going to bring
the best performance possible
for your screen flows.
It is of particular importance
if you are using a repeater
that includes choice components,
especially if there are a lot of choice
options being displayed.
it's just a general performance update.
So that's my best practice.
And with that,
I am going to take this off into a demo so
we can actually see how this is working.
So here
I have a flow that I built as a lunchable
as a quick action
on our contact record for Lorena Boyle.
And I'm pulling up some,
contact information that is disabled.
This is another new enhancement for this
release that I'll talk about in a bit.
so just giving me the
context of who the policy holder is
and what state that person lives in.
And then we have two repeater components
that I built, one to capture each vehicle.
I want to add to the insurance policy
and one to capture all the drivers.
so for Lauren,
we want to add actually two cars.
So I'm going to quickly add in,
so this is a dependent picklist component.
but you'll notice that
as soon as I had selected a model,
we immediately saw a color year.
And then this is conditional visibility
at work.
I'll add in a date here.
And we also have text available
because I don't know about you,
but I never know where to find my Vin.
If it's not the
contract that is in my email.
right.
And then we're going to add a second
car here, a gray Subaru Impreza.
And it's like a 2000.
And we'll just use the same van
because I don't have another sample here.
And then for the drivers,
I was able to pull in those same last name
for each instance of the repeater
by using what the household name is.
This is just for ease of use,
but I could correct it if I want to
add in the license ID and then
really quick.
Wanted to show you our nice
input validation handling.
so I added an input validation
rule on this component
that says the year must be at least
16 years ago.
Because, you know,
we cannot insure drivers
who are younger than that,
at least in the US.
so I'll just come in
and correct this to a date.
That is correct.
I'll add the other two drivers I wanted.
So Lauren's partner
and their son,
who recently turned 16
and definitely needs to be insured,
for 2007.
Great. Right.
So I've collected all the information
that I need in a single screen.
I've added this review screen, manually.
You don't have to do this
in your own implementations,
but it's kind of a nice way
to see the overall context
of the insurance policy
I would create, including pulling,
you know,
the service address from the contact.
But the interesting part is
these two data tables are displaying
all the information that I collected
as part of each of those repeaters.
So these are the two vehicles that I added
and the three drivers.
And as I click submit,
we are running a local action
from Unofficial Assaf in the background
to take us to the insurance policy record
that was created.
And we see we have those vehicle IDs,
vehicles
and the three drivers that we had entered.
Now that's all I
have time to demo here today.
but I want to invite everybody to come
join me and Adam White
with Jen Lee at Automate This tomorrow
morning at 10:30 a.m. PT.
Here's the, URL, for you to join us.
And I'm going to be talking in-depth
about repeaters and giving
a, view into how that all is configured
in Flow Builder,
because it will have a lot more time.
And then you'll also hear from Adam White
about action buttons,
and we'll talk about
some of these other things that I'm about
to breeze through really, really
quickly, just in the interest of time
action buttons.
If you're not familiar with them,
are kind of the next big step
we're taking with reactivity today.
Reactivity allows you to take advantage
of a lot of all of the information
that is in your screen.
But sometimes you need to pull
additional information into the screen
that isn't already available.
So this animation on the side is showing.
Let's say you select an account
and then you need to display contacts.
But before the screen started,
you didn't know
which account was going to be selected.
With an action button, you can create
a flow that will pull those contacts in.
When the user clicks the button.
and then you
can buy reactivity
and take advantage of that new data
that is now available
inside of your screen.
and then last slide for today,
this is for other things that I don't
have time to go into a ton of detail
on, but are really exciting
improvements in screens this release.
One of them is read only as disabled
states for a lot more components.
so this is going to be our choice
components.
Text, text area, currency,
number, date, time,
all like the main basic ones
most people use all the time
and you can make it conditional.
So you can be conditionally
only conditionally disabled.
We also spent a lot of time on the address
component this release.
And this was largely due to the feedback
we received from the community.
So this is my usual patch to please,
please, please do use ID exchange.
We do look at it frequently
and it helps us to pull in small
but mighty enhancements like this one
key thing out of the list of address
enhancements was improving the integration
with state and country pick lists.
reactivity,
our secondary reactivity enhancement
besides action buttons,
which is very,
very exciting, is allowing you to build,
sorry, allowing you to take advantage of
the data that is affecting your choices.
So if you need a choice component
to have its options
be different based on something else,
that's happening earlier in the screen,
you can now do that with collection
choice sets, which can be made reactive.
And our last bit is a version change
that is pretty important.
such flows in screen flows are now
always going to run the active version.
If you upgrade to,
I believe it's version 61 for your runtime
API, the springs screen flows
back into alignment with the rest of flow,
where we try to make sure you are always
running the active version.
and not trying to run the latest version
when it will fail for your users.
So that is a version update
to keep your eye on.
And that I think is a wrap for screen
flows today.
What do you think, Julian?
pretty amazing.
I think people are already
losing their minds about lookup
and repeaters and it's GA so exciting.
We've been talking about this
for a while and it's so fun to see it
like really, really come full circle.
Teams have been working on it
for a couple of years,
so it's very exciting to finally
let it go out into the world.
I've had a problem,
and thank you for all this work
that you and your teams have done,
because I know this has been
like a passion project. A lot of reasons.
A lot of people have been looking forward
to this for so long, so really wonderful.
In fact,
we have some fun comments from the chat.
As a reminder,
please ask your questions in Salesforce
Plus chat right now,
because now we've got Sam in the hot seat.
And as in addition to an on the corner.
But we're going to focus on you
for a little bit.
but first of all, we're going to
just share that Liza is very excited.
She says, look up. Yes,
we heard loud
and clear that everybody want to look up.
Yeah, well, I'm excited that along with it
came a bunch of other really cool stuff.
Let's see.
It's good. Well, Liza,
I hope you feel seen.
and then of course, Mark,
because I feel like this is
sometimes it's a conversation
with, like, Mark and us in the chat.
but Mark said, got to say, the repeater
is probably within my top five updates.
Since I started using flow in 2020,
there was a lot to love and flow in
recent years, so I hopefully that you are
I appreciate that very.
That's a very big praise.
Thanks, Mark.
No I, I screenshot that later.
Oh yeah. Don't worry.
We'll get that for you okay.
But now we're going
to get into some questions. Sam.
So first question I'm going to ask you is
this is pretty pretty basic.
Are you going to support
multiple columns and repeaters.
Oh yeah.
We are have that is kind of the second
most frequent thing
I hear from the community is, you know,
you gave us this awesome thing,
multiple columns, and it allowed us
to build more compact screens years ago.
Where is it for this new thing?
we're we're looking at it right now.
yeah.
So I'm, I'm
not sure if we'll be able to release it
in the winter release,
but it is very high on my list.
Forward looking statement I like it.
Okay. So it's so it's on there.
And also if you still feel passionate
let Sam know because it gets
more,
more feel to the prioritization process.
okay. Another question for you.
Do you repeater support only CRM data?
Oh, so right now what is GA
is really focused
on taking in brand new data.
and so then it's up to you
to kind of massage
that into the appropriate data
structure downstream in your flow,
which you will see and automate this
tomorrow if you come with me.
but the magic of that is
you can massage it into a CRM structure,
or you can massage it into a apex
defined type,
which is how we handle external data
and then send it through HTP.
Call out to create records
in your external system,
just as you just as easily
as you could do, like create records
to create accounts or whatever.
And in Salesforce I love, I love it good.
Call it for Automate This Tomorrow, hosted
by one of my favorite people, John Lee.
So it's going to be going to be
a very good session.
So 10:30 a.m.
PT and that's on the Salesforce Admins
YouTube channel, I believe, right?
Yep. Okay. I have my own team.
okay.
one more question before we move on,
because we've got a yet more,
more flow goodness coming your way.
so the next question I have for you,
Sam, is what components are
now, what components now
support read only and disabled.
Ooh. I'm probably going to miss some
because it's a longer list
that don't support them now.
so the new ones with this release are,
I believe,
tax long text day, date time,
currency number,
and the choice components are like
radio button,
pick list, checkbox, group multipack list.
there is a whole matrix
because sometimes we use the ODBC
based components for everything.
And so if that doesn't support read
only we can't make it.
so that is generally
where the limitation is.
Some things only support disabled
for that reason.
Like it doesn't really make sense
to have a slider be read
only, or a toggle will be read only.
For example.
so that's
the only really discrepancy there.
But we have,
we have like a matrix and documentation
that lists out like these are the,
these are the components that have read
only these, the ones that have disabled.
okay.
So so you can do more than just read
only that documentation.
Okay. I told you like us for this show.
It just it's
it unleashes a new level of openness.
Okay.
Tyler is very excited in the chat.
He says love reactivity.
This really mature screen flows
and brings it in line with traditional
UI frameworks.
So thank you Tyler for the love
and very also sharing some love.
This is just like a love for happening,
saying loving the look of the repeaters.
It looks like it will help trim down flow
and the components.
So, and then one more piece of love for
Stephanie, and then we're going to move on
because we're going
to get more questions for you.
But I got to sprinkle the love in there.
Stephanie says I love those reaction
reactive actions reactions.
There you go.
Excellent. Thank you so much.
Tyler Berry and Stephanie for the love.
Thank you, Sam, for that great demo.
And we're going to come back
and ask more questions of all of you.
But before we do that,
we're going to keep going
because we have last but not least again,
repeat flow RL superstar
Henry Luu, Director of Product Management,
who is going to show
how you can optimize your data
with transform and actions.
Henry, take it away.
Thanks, Julian.
Yeah, so my name is Henry
and I'll be going through the latest
and greatest data
transformation and action improvements.
So I have a special announcement to make.
And that is data transformation
element is finally to.
So I've been working on this
for the last two years and I'm so excited.
It's finally to and huge huge
shout out to our awesome engineering team
for building
such a powerful and extendable feature.
And also our UX team for making something
so complex, easy to use,
so with with the GA, you still can do
everything that you're able to do in beta.
But now we added a guided
mapping experience
which also showed errors and context.
You can use your keyboard
and also you can now map to existing,
read only fields
like, record IDs and created dates.
So I'll show a demo after
I just going to fly through these slides.
the next surprise, release is, is blank
and is empty.
Operator.
We are able to squeeze this in
in this release.
so for those of you who are frustrated
with is null when checking
blank value or empty collection,
this is the best way to go.
Now, just like apex and, formulas use,
this is blank and is empty instead.
Next up, we have actions and stuff
flow improvements.
So we we have, revamped the user
experience to have first search approach.
So you can now search for your,
labels,
your API name and also description.
The description will show up in a tooltip.
And this action info card.
And this is actually from idea exchange.
And same thing with is blank and is empty
also from ideas exchange.
So yes we are listening
and keep your ideas coming.
And lastly for the action part,
we also added a way for you
to set your default value and also
the placeholder text in your action.
So without further ado,
let's just jump straight into it.
Demo.
So here I'm on the record Trigger Flow
and I'm going to show you
is blank in this empty first.
So in the decision
before you would use is no.
and also with some other check.
So whether is checking for empty string
or even some people are using formula.
So if you go into this, city is blank,
some people are using the length,
checking the length of the field.
So now
you don't have to do all these anymore.
All you have to do is replace that with
this blank operator, and you're good to go
for is empty.
before you have to create
a, number variable.
And then before the decision,
you have to use the assignment to,
basically use the equal count
which collects all the,
you know, number of elements
in your collection, assign it
to this variable,
then in the, decision, then use that.
And, and, you know, compare that 2 to 0.
So this is kind of,
you know, a workaround, to be honest.
And so we added a new way to do that.
So all you have to do
is just use this blank
and you don't have
to use any variables anymore.
So next
I'm going to go through the action part.
So if you go into existing action
you'll see that
there's this little card here.
And it tells you exactly what.
And you know
external service is coming from before
it was just only showing
like the operator.
But now it tells you
the external service name.
And if it's apex class and it'll also
tell you the apex class name.
If you hover over this little info bubble,
it'll tell you the descriptions.
Now, if you want to create a new one,
when you create a new action
now, this is a new experience that we have
to search both for, you know, the labels
API name and also the description.
So we actually have a new out of the box,
lock and unlock action.
And you see that
this is actually searching
for the description
thing on the bottom here.
And once you have that then you can say,
hey, I want to lock this writer
or unlock this record
and put in your, record ID
same thing for soft flows.
So if you are creating a new sub
flow, you can search as well.
And you'll search,
you know, all the all all of it.
So yeah.
Label API name also description.
Yeah.
So that's the force that flow now.
rest of the time
I'm going to spend and transform.
And this is basically a easy way for you
to transform your data.
and, and on the left hand side here,
the source data is coming from an action
that HTP action.
And you see this is a response
that's coming back.
I say, you know, complex data shape.
And what I'm doing here is mapping it
to the S
object, product
and this and the collection.
So basically all I'm doing is, mapping all
the data from this level of collection,
which is all these, fields here
into the collection of products here.
So one of the things that we've done
here is with the mapping tab,
when you click on a
socket to map to another feel, it'll
tell you what you can and can't map to.
And the explanation of why you can't do
that is directly
on, you know, on the field itself.
So you don't have to navigate a way to go
look at the docs.
It will tell you directly here
that these are the,
these are the fields you can map to,
and these are the other fields
that you can't map to
because you can't go from number to say,
you know, created date.
So one of the things we added
is you can, you know, map
the read only feels like ID
now if you have, errors.
This also shows you errors in context.
So let's say I'm going to add a formula.
And if I add a number
this is not going to be valid.
And when I go back you'll see that
there is actually a red line
that tells you, hey,
there's some problem here. And
and then
basically it'll explain the information
like why you can't do this,
or know what the errors are.
Now, if you go back and, edit
this say is a string
instead and this works.
And then when you go back,
the error should be gone.
And so one, one of the things that,
it's pretty confusing to do
and I get tripped up on this all the time
is, that when you're mapping collection,
you have to figure out what the collection
scoping is, and that's what this dotted
line is telling you.
So here on the left side, you see, like
there's two collection within each other.
And on the right side
there's only one level of collection.
So you can't go from in their collection
like second level into the first level.
So if you try to do that,
even though this is a string,
string
field, you'll see that it won't let you
and it will tell you
that you're basically, you know,
the level doesn't rule is not compatible.
so you can't go from deeper to shallower
collection, but you can do the opposite.
So if I go down to here, this
this is an object, right?
So this is a collection in the object.
I can actually go from level zero
for instance
in here to a collection field.
And here.
And what this is doing
is basically taking this information
put it as a constant
and then mapping it to
every single element in this collection.
So yeah.
So that's just something to keep in mind.
and I think yeah, that's it for my demo.
So basically the takeaway here is
if you're using, if you're working
with Collection or Apex, the, apex
defined type, complex
data type or with, with,
call outs,
then you want to start using the,
the, transform element instead of loop
because the,
because it's much easier to actually set
it up is easier to understand
on high level, like what's going on here
such so I can actually collapse all this.
Right.
And then so you can see a overview
of what's happening.
And also it performs
much better than loops.
Yeah. So that's it.
Back to you.
you think I'm
just going to have to tell you that the
the chat is very excited.
Jim, I think had the best quote
he said is blank and is empty.
Empty is a big deal.
Yes it is.
thank you Jim.
and, yeah,
we've got go transform from Keaton.
We have Stefanie saying, amazing.
This is so many less steps.
So you've made a lot of people
happy today.
So congratulations.
Transform the way you work with data back.
There we go. There we go. Henry's into it.
Okay.
well, we've got a lot of questions
now for you, Henry.
So here we go.
we are going to start off with, merging.
How do you merge two collections together
and one list?
Oh, yeah.
So that's a tough one.
So we can't
we don't support that today in transform.
so you still have to use, like,
you know, two different loops.
But we are looking
that as part of the roadmaps.
So there's a couple of ways to do that
is either join use join type of capability
or like flatten type of capability
just depends on the use case.
But that's something that we're looking to
okay.
Great. More for you Henry
because you are now in the hot seat.
So we're going to let those questions
flow right your way.
So this is a question from Heather.
She wants to know when an opportunity is
closed when we like to lock that record.
Can I do that with this apex action. Yes
that's a great answer okay.
There you go. You can get locked.
You can lock and unlock
using the same action.
Okay, well that's exciting.
unlocking new capabilities.
Okay. I'm not going to.
I'm just going to stop apologizing
and just let it happen.
all right.
And we've got another question from you
from the chat.
This is from Will on Salesforce Plus.
What are the most common ways
to connect to other data sources for data
transformation
connected other data sources.
Yeah.
So you can use Http action if you know,
if it's like a one off type of thing.
Or you can use external service.
So if you have API spec
you can use that to kind of,
you know, import
all of that in or real soft.
So MuleSoft is also another great way
to use, to basically have like,
you know, out of box connectors.
Excellent. Okay.
and all spells, custom apex action.
That's right. Hey, so many ways.
Code. Yes.
I mean, you know,
we got to have something for everyone.
lots of choices.
Henry, one more question for you,
and then I'm going to open it up
for everybody else
who's on the hot couch, so to speak.
okay.
This question Henry is coming from
Naveen on Salesforce Plus is blank
and is empty are really nice features,
but I saw that is
empty is not available for free.
Number of data type fields.
Is it specific to only numeric variables?
Yeah.
So you actually use displaying
for the primitive type fields
and then is empty is for collection
checking whether there's
anything in the collection.
So it's empty.
It's not available
because that's only for collection.
Got it.
Kind of like when Sam explained
that the because we're using either,
the lightning web components
that it only makes
sense for certain types of elements to be.
Yeah. Available or not available. So.
Okay. Got it.
This is good.
This is why we have two questions okay.
Now I'm opening it up to everyone.
And you guys there are a lot of questions
okay.
Surprise, surprise is okay.
We're going to go back to the top
of my question list here.
This was asked at the top of the show.
Sam or Henry.
I think this is kind of in your territory.
Paul wants to know,
can we build our own flow templates?
yeah.
So flow temporal.
What? Once you build it,
just check it as is a template
and then it'll become a template.
There you go. All right.
Easy peasy.
All right.
They're going to get harder, I promise.
All right, Connor,
we are coming back to you.
It's been a while since we chatted,
so I hope you got a little time to rest.
But here we go.
This question is from Kellen.
Does the AI create custom
formulas in the flow?
Yes. So right now
we have support for simple formulas.
So most simple use cases will work
for some of those more complex formulas.
It might not be able to do that.
But definitely does support formulas
right now.
so go and give it a shot at whatever you,
you want to try and see how it does.
That's excellent. That's exciting.
All right.
Give it a try.
Let's see how Einstein put it to the test.
Connor, I'm coming right back to you.
Joshua is wanting to know
if the AI can create an email template,
or is there other metadata
that it will create based on your prompt?
If so, does it provide you
with a list of all metadata created?
It can
create like, like chat or posts as well.
in terms of like metadata,
I'm a little unclear
on what he means with that.
So doing a send email action
or is creating building
an email template
that can be reused for multiple emails.
It will create
like a text template, in the flow.
Okay. So so yeah,
I think what GPT is doing is it's
using the regular send email,
which is like a one off email inflow.
And then there's the text template.
Yeah, inside the flow.
But it's not creating metadata
outside of the flow right.
Yes. Sorry. Yeah.
To clarify there, it's
creating a text template within the flow
which is then
used in the send email action.
So so you can use that text template
in like another flow or somewhere else.
Right.
No. Yeah.
Just within that one flow okay okay.
Good clarification. This is great.
and by the way, feel free everyone
to jump in on each other's answers.
This is why we have you all here together.
Connor, I'm going to come back to you.
and then I promise
we'll spread the love a little bit.
this question is from Rahul.
He wants to know,
we have multiple record trigger flows.
Can Einstein merge
all of them into a new flow?
Yeah. Not currently.
So right now it's just one off
flow generation, I think down the line,
obviously, as we, you know, think about
future use cases being able to have it,
you know, look across all your flows
or create actions across
all of your flows would be great.
But right now that is not supported.
Okay.
So Rahul idea exchange put it on there.
There we go. okay. And coming to you now.
All right.
So question here from Joe.
He wants to know in future releases
can we possibly get a flow
merge app that merges
two flows that work on the same object.
Yeah.
They're merging together a few.
Well okay. Go ahead.
Sorry a flow merge capability.
Pick two flows.
Good idea.
And put it on the idea exchange.
There you go. Okay.
But on the idea exchange.
All right.
But you're not getting off that easy.
You have more questions okay.
And then next question is from Tyler.
He wants to know
did the team consider the ability
to activate or deactivate flows via
the flow list instead of having to click
into the flow metadata?
Yes, that's on the roadmap.
So okay. It's happening I love that.
All right.
Forward looking statement. Yes.
okay Sam, we are going to come to you.
We have a question from Leah.
She wants to know are all flow components
available to use an experienced cloud?
Depends on which
experience cloud site
you're talking about.
Aura? Yes.
If it's a aura based experience.
Cloud site, I'm
pretty sure everything is supported.
again, we use base components
and like some of them don't work
particularly well or aren't supported.
And experience cloud,
which is documented in the lightning
Component library
and we also have a lot of teams
that build components
for like their specific cloud use cases.
And we push pretty hard to make sure
like it's going
to work in mobile, it's going to work
and experience cloud, all those things.
When you come to LWR based experience
cloud sites, however, there is
a rule of aura is not allowed.
And so we have a lot of,
the components that our team owns,
like the basic inputs.
Look up all those guys.
we worked really hard to make sure
that those are all compliant
with all the requirements.
The most basic one of which is
you can't be aura.
You must be able to see,
not all
of the components that are available
in Flow Builder have taken those steps.
one that we are really trying to advocate
to be brought over is file upload.
So that is probably the biggest one
that is still not supported
in all of you are most commonly used one
that's not supported in LWR but
okay, complicated answer as well.
And that's why we have you here,
so that we can understand all the details.
And thank you for kind of taking us
behind the scenes a little better
in terms of the infrastructure
and why things are the way they are.
okay, maybe a little bit of an easier
question. Sam.
this is from Steve.
Can the repeater be used to
edit an existing collection?
No, but that is what my team is working on
right now.
So roadmap
feature, blah blah, blah, safe harbor.
but yeah,
we are currently working on the ability
to take an existing collection of data
and pre
populating your, reviews with stuff.
So hopefully this time next release
I will be demoing to you
how to update an existing auto insurance
policy like adding a new vehicle,
removing a vehicle, all that kind of stuff
and then allowing you to handle like,
I don't want to delete those records,
I want to archive them.
And all that kind of goodies are
what we're thinking about right now.
I love this,
so we'll be talking about this
in that time when that happens to be
like, remember when we said,
I love it?
Okay. Henry, coming to you now.
I'm just working my way,
you know, down the couch.
this is a follow up question from Ann.
when is it recommended to use
the transform element over a loop?
So depends on the situation,
what scenario you have.
So if this support it and transform
I would always recommend transform
because it's actually it performs
actually much better than loop.
and a lot of our customers
are actually already transitioning
getting rid of loose data
to do those collection use cases.
So it depends.
But I would say like if, if the use case
is very simple, and transform can do it,
go ahead and remove and, you know,
try to switch it over to transform
if you can.
Okay. All right.
Well best practice suggestion in there.
That's good.
Thank you for clarifying that.
okay, Connor, we're coming to you.
So you just,
it's like one big loop.
all right,
I really I'm going to miss this.
Okay.
this is another question from Kellen.
they want to know,
can I create loops and assign variables?
Yes, it can currently do that right now.
So, it has support for loops
and it can create variables as well.
So both of those things right now
it should have the ability to do excellent
but not transform and not transform
okay. All right.
We'll get there.
Maybe someday you know one day.
One day Wednesday.
okay.
well, speaking of transform, Henry,
I'm coming back to you.
This is a question
from on call on Salesforce Plus,
is there a way to create debug logs
just for flows
to see a record journey
across all the flows it touches
all the flow it touches.
It's cool idea. Yeah.
I mean, yeah.
That's interesting. Yeah.
We don't really have something like that,
but I mean, debug log
does tell you like all the stuff flow
that it touches, but not like,
you know, in a transaction
you can turn the apex debug logs on.
If you turn on the work flow,
the workflow one to finer
or finance whatever the deep end,
all the others feel like a low level.
And that would give you
like more flow information,
but it wouldn't like remove
the other things out of the same order.
It is a really cool idea.
Yeah, and I would love to sanity check.
I love the idea exchange Sam looks like
she's really interested in building it,
so give me give her some.
Let's give her some fire to work
with there.
okay. anon, for coming to you now.
this question is from Stephanie.
Are we able to deactivate a flow
from the automation app?
Kind of similar to the earlier question.
Yeah. I mean, going into the flow detail.
Yes. Yeah.
You can't do it from that
on the function page,
but it is something that Kelly's team
is working on this once.
So it's in the works right now okay.
So in the works right now okay.
Well there we go.
All right
anon I'm still coming back to you.
so this question is from Liz.
When can we have an easy interface
to clear old flow versions in bulk.
so like a multi-select.
So versus having a soft chat about this.
Oh about that.
so when they say clear
I'm assuming delete.
And yeah.
So there's, there's use cases
where people do want to bulk
delete multiple flow versions.
so that's something that
on the packaging side, we're looking into,
I mean two G,
two GP can delete, but not on the UI.
So there are,
there are unofficial, SF, components
that allow you to do that to mass delete,
but we don't have it out of the box.
Okay.
All right.
So good idea again. Yes.
Maybe something on the on there.
Yeah.
because as we're thinking about as,
just thinking about of the future
of the automation app, it's going to be
really important for us to understand
what are the use cases
and like the reasons
why you want these things.
it's incredibly valuable part of the idea
exchange.
Excellent. Well, so,
there is, there's something
that we need to talk about as a team,
everyone, because,
there are so many comments
about flow costumes and flow,
flushes and flow love in general.
And I can't help
but notice that you all match.
do you have an
update for everyone
about these amazing shirts
and how might other fanatics
get them? Yes,
we are wearing almost all the same shirt
I got all the way.
Henry as a vintage one.
to celebrate that, there is a fanatic
shirt on the trailblazers store.
A major store right now.
Unfortunately, not on the impact in EMEA.
One forward looking statement where we're
trying to trying to at least get like,
a like I'm interested survey
or something on on there.
But I haven't heard back from them yet.
But I like
this came up at the last release.
I think that should come up
every single time
you've ever done a presentation
with a fanatic shirt,
but it came up with like a verb.
It's in time.
And we, looked more deeply into
it and they were like, okay,
so here we are.
So there is a there is a shirt,
you can go order your own fanatic shirt
on the Trailblazer Store.
And if you're not in America, maybe, find
a buddy in the chat to order one for you.
Do you know what I don't know is
whether Diana Jaffe will be wearing her
flow costume and admin URL tomorrow
or when whenever that session.
You're just gonna have
to tune in on Friday and find out.
I mean, it's so admins are going to have
a quite a day on Friday.
They've got, you know, admin URL.
We've got all kinds of great things
going on right there. So,
all right,
we're going to get back to some questions.
I'm sure people are very happy about that.
oh, but there's
one person I have to say
that is in the chat, Melissa.
after my own heart,
I'm so excited for these updates.
I'm afraid I might follow up, but.
I can see the collective groans
of the crew as I said that.
So, Good job Alyssa.
Excellent. Excellent job.
All right, we got more questions.
All right. We are going to come to.
Let's go to you.
Henry, this is a question from Daniel.
Are there situations other than ingesting
data where transform would be useful?
Ingesting data.
Yeah.
So, one of the use case
for external service
is how to squeeze certain data
into the body of the post call.
So, instead of just getting data from,
like, say no, get records or get, product
from like some service, you can
you can try to squeeze it
into like the body shapes
so you can do a call out after that.
So so basically it's transform is for,
you know, ingesting data and also
changing the data shape to something
that you need downstream with flow.
That makes sense. Transforming it.
Yeah, I got it.
Thanks.
We're gonna have to work
on, like, a transformer.
Like a little something. Yeah.
Okay.
Maybe flow is a transformer,
like, getting.
Really? Okay. Sorry.
Going down, going down a weird path there.
Okay, let's get back to some questions.
Sam, I think this one is for you.
Karthick wants to know why
action button supports only auto launched.
Closed.
we are thinking about in the future.
Which is not on a timeline I know of, but,
it could potentially support screen flows
or like I will be
using UI stuff in the future,
and we would love to hear
what kinds of use cases
you see coming forward.
we were really focused on the like,
we want people to be able to bring data.
And we saw a lot of success
with Josh Damon's, data Fetcher component
on Appexchange, and that really helped us
drive the priority of this work.
and so it's just we
felt it was more important to allow people
to, like, bring data
in, do additional processing.
but it's not that
we don't see value in screen.
It just didn't make it. So clearly.
You see a lot of value in screen for us
because we've invested a lot from flows.
Yeah. Right. Right. okay.
We are going to do, a couple
more questions here from the chat.
Connor, this one is coming to you.
this is from Kevin.
He wants to know, can Einstein edit a flow
or just initially create one?
So right now we only have support
for initially creating one.
But, it is on our roadmap
that we would have the ability to modify
flow with natural language.
So you can actually give a prompt
and it will modify the flow based off
of what you told it to change.
And we're also looking at edit
a prompt as well.
So that would be a little different
than using natural language
to modify the flow that would just be
you can go back in
instead of having to like start over
or reenter
the prompt with different wording.
You could actually just go in and edit
the prompt right there and resubmit it.
So there's sort of two ways
that you can potentially edit the flow.
They're both on our roadmap
and we're working on them.
Oh I love that.
This is again
I'm getting personally very excited
because if I inherit a flow and
I have no idea how to like, do the actual
individual changes to make it do what
I want it to do, I instead can help me.
I'm excited. Okay,
one more question, Sam, for you.
and then we're going to
I have a question for everybody.
this is from Jesse and Tori on Salesforce.
Plus, are there plans to add
rich text inputs to screen flows?
We would love to have.
It's just not very high on our roadmap
right now.
so yeah, like
check in like kind of a long term roadmap,
I would expect to see a rich text input,
but it's not on the top of our list.
Okay.
Well if you care that much about it
up on the area exchange.
okay.
A couple more pieces of love here.
we have Tyler saying
thank you for paying attention
to opportunities to implement search.
Those are needed quality of life
improvements.
Thank you.
and then we have some more.
Oh, Mark.
Mark, this is not Mark Jones.
This is another mark. Mark with a c.
he says please
splice that transform element demo
and publish it for my daily playlist.
That's the one other people want more.
And, one more piece of love here
I'm going to share is,
Leah says, thank you, Sam.
I really appreciate your insights
as we're eyeball deep
in requirements gathering
and scoping out an experience cloud build.
You are my slide.
All that's pretty good.
And Leah said that's for you Julian.
Thankfully I appreciate that.
okay.
I want to take a moment and kind of talk
about the future and kind of where
flow and automation overall kind of going,
because I know all of your teams
are really looking future forward, talking
about multiple releases in the future.
What's one thing
that really makes you excited and kind of
painting this vision
of where you see flow in general going,
you know, three releases out
again, forward looking statement.
This is more thinking
like what's your strategy?
Where are things headed?
How is how are your teams
thinking about what to build?
How do we all start with you? Yeah.
I think since I'm in a
data transfer space,
I think one of the cool things
I want to see is like, see more capability
to, like, bring, more powerful features
for admins to bill and,
and be able to kind of incorporate
I into it.
So one of the things that we want
to be able to do is in the future,
like if you can use
AI to do all these transformation,
then you can tell it what you want to do
and it'll show it in front of you.
Like, you know the things I did, Bill,
and you can customize it and can edit.
So it's kind of an interaction
between you and I.
I think that
that would be a super cool idea
and especially with like, you know, us
and MuleSoft, you also have like hundreds
of hours of box transformation.
If we can somehow like leverage that,
that would be amazing as well.
MuleSoft merged into all of the amazing
things that you can do with automation.
I like this, this is a good I like this
future picture you're painting for me.
Henry, this is this is exciting.
It's a module 11 there.
I'm going to have to think about
some good plans in that space,
but I'll get back to you.
excellent. Sam, what about you?
I think, like,
the big future,
I think, in our area and screen flows is
kind of two pronged.
Like,
how do we enable admins to build, like,
truly sophisticated experiences
without having to reach into code?
and then there is also a part of me
that is just like, what can we do
to make it so that you don't have to build
a custom component?
as much as possible.
And that's really like
reactivity was a huge part of that.
Repeaters is another big part of that.
Or previously,
if you wanted that experience is just
you had to build a component
that was capturing
exactly that information.
so that's kind of the two spaces of
then they're kind of related.
but how can we make screen flows,
like extremely sophisticated
while not making them impossible to build
right then?
Complexity. Yeah.
But simply, yeah, more functionality,
but also usability.
And that's been historically
a very tough thing for us to balance.
Well.
And it's the kind of a theme
that is emerging in general.
Right.
Like Connor, where you're talking about
like Einstein is intended to help
make it easier to build flows.
All of these components
are building for screen flows,
make it easier to build
beautiful reactive screen experiences.
And Henry, like your point to like
this is the intention is to make it easier
for people to manipulate
and work with data at a very large level.
That before would have been really hard.
so I kind of like this, this theme
that's emerging.
All right. And, and your turn.
two things I would want,
the two things that are exciting
and I and I have space,
first is making the automation app the
command and control center for automation.
So not just flow,
but bringing, process automation tool
orchestration along as well.
So that's one evolution of that app
is what we are focused on.
the second is, is complementing
what Connor and his team
are doing on the creation side.
So he's focused on the Einstein power
creation you're looking at
if you're starting manually,
if you're new to Salesforce, new to flow,
how do you
how do you onboard, how do you quickly
learn what type of flows there are?
How do you navigate your way around,
and get to the builder
with the right start element in there.
So and browse the right, templates
because the starting template
to begin with.
So if you're not starting with flow
you would want to start
with a new experience.
So those are the two things
we we think we emphasize
I love that and I got that
I mean I still can't get over just like
seeing that automation app is just like,
oh, this is so it's so powerful.
I mean, it's it kind of again, goes over
with a kind of a broader theme as well.
And I'm sure we'll talk about this
at the admin preview on Friday is,
you know, really making it easier
for everyone who manages the system
from an administrator level
to see everything
that's going on in one place
and make it easier for them
to use it as well. Right.
And you know, we we're seeing some of this
with some of the kind of user
permissions and access stuff
that's coming out.
And so it's very similarly aligned.
And it makes my
it makes my admin heart very happy.
So Connor, how about you?
I would say in the short term
we're we're more focused right now on
like editing a prompt and summarize
very excited about summarize a flow
I think longer term,
like an integration with copilot
is something that we're looking at.
So the ability to,
you know, use
copilot to have different actions
that relate to flows,
I think talked a little bit
about like earlier
about kind of summarizing, across
all of the flows in your org.
So being able to,
you know, ask questions about,
you know, not just one individual flow,
but also just, you know, what,
at a high level,
all of the different flows in your
org are doing,
I think, flow debugging has been
a big thing that a lot of our admins
have complained to us
about and need help with,
and then just best practices as well.
I think being able to enforce
best practices is something that
a lot of admins kind of struggle with,
to know the different flow best practices.
So being able to have Einstein actually,
you know, help you,
you know, by letting you know that, like,
you should, you know, modify your flow
to build it in this particular way
that, respects
those best practices is something else
that we're looking at as well.
So a lot of exciting things ahead.
But, yeah,
I love that idea of really using Einstein
as like a coach or an assistant, right?
To kind of help you get better at building
better things and better,
more scalable
and will last ever time and is.
That's great.
It's an exciting future.
I'm really looking forward
to letting it all flow.
a couple more shout outs
just before we kind of get to wrapping up.
Nicole.
So, Sam, you're the MVP,
so getting some love.
and, let's see.
Mark.
Mark is asking if Diana is secretly there
with her flow costume.
Diana is not so secretly in the Q
and A in the chat.
I'll helping you answer questions
along with the amazing Adam White.
So shout out to our amazing
PMS in the chat is at home with her lamp.
Diana love lamp.
She's with the lamp right now.
Yes, yes. That's true.
well, I wanted to thank you all
so much for joining us today.
It's been wonderful
to see all the innovations.
I'm personally very excited about getting
hands on and playing with a lot of us.
And thank you so much for all the work.
Your team is do.
I mean, it's really
I hope you feel the impact
of what you're building
and the payoff and the efficiency and the
the how much it's making it easier for
people to build really powerful solutions
that help everybody
in their organizations.
So feel the love, take it and take it in.
and again, if you are interested
in getting one of these
amazing fanatic shirts
that you see on display,
you can get your own,
if you're in America right now,
at the Trailblazer Store, so you can order
your own Flow Natick shirt there.
I thank you so much to our chat
moderators.
We had a ton of questions in the chat.
If we did not get to your question
live on the show, don't worry.
Pop on over the trailblazer community.
Ask it in the trailblazer community.
We'll make sure you get an expert
answer there.
If it's not by one of these lovely people,
or by Diana or by Adam here in the chat,
it'll be by somebody on their teams.
we've got a lot more great content
coming your way.
So tomorrow, the summer
24 release Readiness Love Continues.
We're going to be back
with our developer preview at 9 a.m.
Pacific, followed by our CRM
analytics session at 11 a.m..
Thank you so much for tuning
in. Appreciate you being here.
I appreciate you sharing the love
and getting your questions in.
And we'll catch
you next time in the cloud.
Resume AutoScroll
Link copied to clipboard
Salesforce Flow Summer '24
Discover a new way to manage flows with our latest innovation, the Automation Lightning App. And meet Repeaters, a new screen flow feature that lets you easily create multiple records on one screen.
Starring
- Anand RohraDirector, Product Management, Salesforce
- Connor TurcoAssociate Product Manager, Salesforce
- Henry LiuDirector, Product Management, Salesforce
- Sam ReynardSenior Director, Product Management, Salesforce
Up Next
Questions about Salesforce+? We have answers.
What is Salesforce+?
Salesforce+ is the free streaming service for business. It’s a place to watch live events that help you grow your career and company, on your own time. Salesforce+ is produced by Salesforce, so you’ll find our company’s big events like Dreamforce here — as well as virtual learning made for your role and industry. Everything is free and unlimited.
What can I watch on Salesforce+?
You can watch all kinds of helpful, entertaining, and inspiring videos on Salesforce+. One thing our members love is our events. Whether you catch them live or on demand, Salesforce+ gives you a free front-row seat to our biggest global events, like Dreamforce, TDX, Tableau Conference, and Connections. These entertaining business shows star people in roles and industries just like yours, giving you fresh ideas for how to grow your company and do better work. The best part is, it’s all free.
Do I have to pay for Salesforce+?
Salesforce+ is free. Watch any Salesforce+ events or series at no cost. To enjoy unlimited free access to our entire library of videos, become a member by signing up for Salesforce+ with a Trailblazer account. To join us for virtual events like Dreamforce or Connections, you need to create your own Trailblazer account (it’s free!).
What is a Trailblazer account?
Your Trailblazer account gives you access to a unified profile across the Salesforce ecosystem and allows you to manage your settings and access across multiple Salesforce sites.
How do I sign up to register for live and on-demand events, like Dreamforce?
Sign up or log in to your Trailblazer account and complete a few additional details to watch Salesforce+ events live and on demand. We recommend preregistering for all events on Salesforce+ to get your own personalized journey, reminders, recommendations, and more.
Do I need to be a Salesforce customer to watch Salesforce+?
You don’t need to be a Salesforce customer to watch Salesforce+. Our virtual learning is open to everyone.
