Play
Show Navigation
Show Transcript
00:00
Play
Seek 10 seconds backwards
Seek 10 seconds forward
00:00 / 01:04:06
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,
as Salesforce developers
and admins are 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.
I'm Caroline Barth, our senior customer
and product evangelist.
I'm excited and honored
to be your new host.
I love RL,
this is where we get to geek out
and cover
the new product innovations
coming your way in the next release.
We have an amazing team of Salesforce
Flow experts here in the studio
with me, and joining virtually
to walk you through
some of the top new features
in Winter 25.
And you've probably heard
of Agentforce,
the autonomous agent platform
for building
and deploying
agents across all customer
360 applications.
Well, good news for our flow fans.
Agentforce
allows you to build
agents using existing flows,
apex classes, and prompts.
But just wait until you see
Einstein drafted flows and formulas.
But before we dive
in, I need to remind you
to only make purchasing decisions
on existing features and functionality.
So with that covered,
I want to thank you
for investing your time with us today
and for all the feedback
that you provide.
Your feedback is what
helps our technology teams build
solutions centered
around your experience
and helps make this broadcast better.
So here is the agenda
over the next hour.
Our product managers will give
live demos highlighting
the top flow features
in the Winter 25 release
that is going to help you
automate enhanced
performance and build processes
more efficiently.
So come back tomorrow on day two
for Developer Preview Service Cloud.
In a bonus episode featuring
what's new without Cloud.
And then day
three wraps us up with CRM,
analytics and Admin Preview.
As always,
all of our episodes
will also be available
on demand on Salesforce Plus.
And along the way,
we want to hear from you
and answer your questions
about these new features.
While we have these experts with us.
So join the chat on Salesforce
Plus and drop your questions
in the Q&A tab.
We've got a team of product experts
standing by with answers,
and we'll also take
some of your questions live
and if you still have questions
after the show,
you can post them
in the trailblazer community
using the hashtag Salesforce RL.
So let's go.
First up, it's a legend.
Diana Jaffe,
Senior Director of Product management,
is here to cover new enhancements
in data management and actions and flow.
So welcome Diana.
Show us what's new.
Thanks so much, Carolyn. Hi everyone.
I am super excited to be back here
at RL
and talking about all things
data and actions and flow.
So to kick us off,
we have
really big exciting new enhancements
to the send email action.
This is something
a lot of you have been asking us
for a long time.
You can now send those emails
not just to five people,
which is what it was
before, but 150 people.
So that's, you know,
a 30 times improvement.
We've also added in options to CC
and BCC, your recipients,
as well as just put them in the to line.
Now a little
I know
we're talking about the future in AI,
but a little tech
trivia comment in the chat
if you know why it's called CC and CC.
My, what that stands for.
For a little bit of a
history lesson as well.
So all right, that's
what's coming in the send email.
But I'm going to actually jump
right into the demo now
because I want to show you
what's going on inside flow.
So to start off
we have a couple familiar
friends here that you'll see,
some of our characters.
And we're going to do
some automation around that.
So if I go over to my flow,
I have a pretty simple screen flow
to let me go through and edit
all of those characters.
And now this is using
our new repeater element.
But Sam is going to tell you
about that later.
I'm not going to get too much into it,
but we're going to look through
our different characters
and we're going to make some updates.
We have a lot of new stuff coming.
So Albert Einstein,
we're going to call him a genius.
And I think Astro Guide and Astro,
in addition to being a trail guide,
we're also going to call him an agent.
We got a lot of new agents coming.
And to celebrate the ten year
anniversary of awesome admins,
we're going to say
that cloudy is awesome.
But we have some other characters here,
maybe a new one
that we want to add to that list.
This flow.
So we're going to add flow in as well.
So if I was doing this in the past
and wanted to build this out
as an experience
and then put it behind
the scenes here in flow,
I would have had to split this out.
So I'm making updates
to some of my original, characters,
and I'm also adding new ones,
so I would have had to
take this collection and split it out
between the new ones
to do create records on that
and the old ones
to do an update records.
But you'll notice
I only have one item there,
and when I hit next and go over and
refresh my screen,
you'll see
flows added and
we've got all of our updates
all using one element.
So let's go check that our element out
and see what happened.
So we've added in the winter 25 release
something that
if you're familiar with apex
we often call Upsert.
But here you'll find it in flow
under your Create Records
as an additional option
to update existing records.
So when you go in here
and you have your record collection,
you can enable this.
And what that's going to let you do
is take a whole collection,
say, of characters, objects, whatever.
And if you make changes to it
and you add things to it,
all of those
are going to be committed
in one element
in one database transaction.
So importantly, when you're doing this,
you need to figure out
how are we going to identify
is this an existing one
or is this a new character.
And by default you can do that
just using the record ID
and Salesforce
will handle all that for you.
But let's say I'm getting information
in from a new system,
and I want to compare on something
like the email field
that's going to be available
on your standard objects
for certain fields to compare against,
like email and contacts.
Also,
if you want to do this on a custom field
so you're like,
I know I'm going to store, say,
an ID from an external system.
And that's what I want to use to compare
whether this is a creator, an update,
you can set a custom field
and then use this option to do
external ID as well.
So all of that together,
we often call it upsert.
If you're a little more techie
or create an update,
if you're new to this,
but I think this is going
to be super powerful
for those of you out there
who really obsess about your limits,
this is also really cool
because this is one DML call.
This isn't one for create
and one for update.
So that's also going to save you
a little bit
of processing power and count
against your limits
a little less as well.
So a huge efficiency improvement.
And the
last thing that I want to show
you is updates to transform.
Now if you've been keeping up
with transform, I'm impressed
because it has new stuff
coming out every single release.
But we have one that I think
is going to be pretty cool
for a lot of you in this release.
So if I go in and I get my contacts
that I just had on the left hand side,
and then I want to define my target.
So what am I transforming
my source data into
when I go over to my target?
If you clicked this before,
you would have just
seen the apex defined and the record.
Now we have a lot more options
that you're able
to do
to transform into different
things like a collection of dates,
a collection of numbers,
or in this case, I'm
going to do a collection of text.
So let's say
I want to send all those emails.
I want to get all those emails
out of that contact.
I can do a text collection,
and with one click,
I can map my emails
and just have those
as a separate collection
just of my text, emails.
If, say,
I want to use that
new send email action,
but also
unrelated to
this scenario,
but a pro tip and something somebody
I don't remember who it was,
complained to me
about directly at Dreamforce
and said, this is such a pain.
If you use the in operator
and you're
looking for record
A and Record Collection B,
you still had to go do a loop
to convert those IDs
from that record collection
into a tax collection,
if you know what I'm talking about.
You know, this is annoying.
If you don't, don't worry about it.
But,
now I can do that
with one click and transform
so I can take this ID field and also
map it to the text collection.
And that's going to save you
time in one of those little extra loops
that really don't need to do so.
That's what's new.
And data
and actions for the winter 25 release.
Back to you Carolyn. Great job.
Okay,
so can we just say
you're the one that's helping us
get a little less loopy?
Is that.
I think I'm getting a little more loopy.
Yeah, yeah, I'm just in, I love it.
So we've got some shadows
here, especially since, you know,
what is carbon copy?
Most people said
carbon copy, blind carbon
copy as the definition.
But Kim said, remember
back when he used carbon
paper to make copies?
So you remember.
Yeah.
You gotta remember the actual
physical carbon paper. Yes. Absolutely.
So that's great.
And I think the other comment here,
which I think is
really, really important,
Squyres said there's a lot of tech debt
that's resolved
by your first enhancement,
and I think that's really important.
We're constantly
looking for those improvements
as we talk about efficiency,
efficiency, efficiency with these flows.
And so great. That's wonderful.
All right.
So let's get to your questions.
You're in the hotseat.
So transform
is it going to replace loops.
I think it completely replacing
loops is a long ways away.
But I think our goal is we've heard,
from a lot of customers
that loops can be sort of onerous.
It's a lot of extra clicks.
It's extra
elements again, for simple things like,
I just want to get some
ideas out of there.
And we're also able to and transform
to do some things more efficiently,
because we kind of know exactly
what you're trying to do in advance.
So what we're doing
is looking for those use cases
that could be in loops
and trying to pull them out
into transform
kind of use case by use case.
So this is just an evolution
use case based.
So sharing those use cases
we aren't going away.
We just have heard from many of you
that they can be kind of overkill.
Say for some things not just transform
but like you brought up the
in operator that right.
That was another big thing
you always had to use loops for.
So we're always on the lookout
for things
that you could make a lot
easier for you.
Like loops
make everything possible,
and then things like transform
and operators
and some other stuff we have on
the roadmap is like these very,
very common use cases.
We want to be much easier
for you to accomplish. Absolutely.
That's great.
And so going back to the emails,
because that was that lit up, our chat.
So, when should I use
the send email action
and when should I use email alerts?
That's a great question.
And it's,
I think kind of a personal preference.
I've talked to a lot of admins
who prefer one or the other,
and there isn't necessarily
a right answer.
For those of you who aren't familiar,
email alerts are available
as a separate thing and set up
so you would go outside of flow.
Go to your email alerts,
set up and configure your email,
and then you can call that as an invoke
action from flow.
We also have an invoke
action called Send Email inside Flow,
and that you would configure
all the things
like two
cc, DCC, the content all inside of flow.
And I've heard from some admins
that they really like it being separate
because maybe they have people
on their team
who aren't comfortable in flow,
but they do a lot of, email updates.
Others are like,
I'm a solo admin,
I want to stay in flow and write
that email as fast as possible.
So I really think it should be more
about how you work.
And again,
we're always trying to make sure,
to kind of match up the feature set.
So you're not having to choose
based on, again,
some of these limitations,
like the five people to send to.
But great.
And so
trying to help
cover a lot of different work styles
and use cases just in the work.
Yeah, exactly. Yeah. Okay.
You meant you also mentioned,
some of the enhancements
don't count twice against limits.
There's more processing power.
But then there's the question
is the 150
email limit separate
for the two cc and BCC or is it all one.
That's all one. Okay.
So 150 recipients.
You can choose how to split that up
between two cc and BCC. Great.
Well you will be joining us in
just a bit for more questions.
So stick around.
If you have more questions for Diana,
keep them coming.
She's going to
be here at the end for more Q&A.
So make sure you put those in the chat.
And up next we have Antoine Cobo,
senior director of product management,
and he's here to show us the automation
app and builder experience.
Antoine, take it away.
Absolutely. Thank you. Carolyn.
All right,
so let me quickly tell you
about our amazing,
amazing new capabilities
that we're bringing into the automation
app and our builder experience.
And then they will show you,
all of that in, in life demo.
All right.
So first is our brand new flow
validation experience.
Doesn't look like super exciting,
but you really see the difference.
Now, when you save or activate
a flow,
you are going to see errors
and warning in a brand new panel.
So I'll bring you a new panel
in the builder on the left side.
And not only you will be able
to separate errors from warning,
but we also give you and the links
that point to the right elements.
So super easy to debug your flow
to make sure
that you can easily identify,
you know, the errors that you're making.
You know, this is really cool.
This is really helpful.
I've been using that for for months now,
and it's really,
it really helps me build
better flows over time.
Next one is the
addition of orchestrations
in the automation app.
So for some of you
who have already used the automation
app to renew lightning app,
that all, all of you
awesome admins can actually use
to monitor
and manage your automated processes
outside of setup.
So it's in one single place
for everything. Automation.
So all your flows are in there,
all your orchestration down in there.
So you can really dig into,
all those assets,
in a lightning experience.
All the things are very important
as well.
Some usability improvements,
for orchestrations
like drag and drop
capabilities for steps, within a stage.
You can't imagine
how many people came to me at Dreamforce
saying how painful it is to add steps
and all of them in an orchestration.
So we're fixing this
in the winter release,
which is really, really cool.
You can now
copy paste steps across stages as well,
which is also a very nice improvement.
And last but not least,
you can now customize the word guide.
So for people
who don't know on this call,
the word guide
is this lightning components
that you can put on your records page
that will actually display
action items
generated by an orchestration
and assigned to a specific user.
One of the cool additions to this
is that you cannot hide
either the word guide from the page
if there is no work item available.
So very cool
to save some space on your record page.
All right, let's see them.
Let's see all of that in action.
So here I start from,
you know, the home
page inside of source.
Very, very handy.
I can quickly search for the automation
app through the app launcher.
And that's going to open this brand new,
automation
app where
I can see the list of all the flows
that I've recently modified.
And I have some, quick
links into the flow community,
trailblazer, Community
trailhead, etc., etc..
We have one tab here for flows
so I can quickly see all my flows.
I can also search for them,
which is something that has been asked
for years, I believe,
from, from you guys.
So now you can search within your flows
and you can define
also your own, list views.
So you can create those list
view here like arrow
and then define your filters.
Everything you know about list
views is not available
for your list of flows.
So really really cool.
One thing I want to really show
you today
is that we are adding orchestrations,
in a separate tab.
So that's where you start,
looking at your,
you know, automated processes
as a reminder.
And orchestration
is basically a combination
of multiple flows,
with some logic,
between the execution of those flows
so you can create your entire project.
Open one of them here.
That I built, a few months ago, Wiz,
which is a very cool orchestration.
And I'm going to show you
this on the canvas right after.
But what I want to show you here
is this very nice,
detail page
where I can see
some of the key metrics
that I care about,
like the average runtime,
the completion rate.
I can see
all those runs for this process below.
I can see versions.
And I can also click on View
Viewing Flow Builder.
And that's going to open
my orchestration in the builder.
So I can very quickly
see everything in here
from here.
I have this stage called Test Drive,
and I realized that I need to move
those steps around.
I really want to assign the sales
agent later in this process.
So what I'm going to do here
is just drag and drop that step.
And that's as easy as it is.
Like it is super, super simple.
And eventually if I want,
I can also
copy that step and, you know,
paste it into a different stage,
add in here
and then we're going to save
all the configuration,
everything you have set in
terms of input parameters,
the flow itself, etc.
everything is copied over into this new,
stage.
Very, very cool to to have that.
All right.
So now I'm going
to navigate back into our work guide.
So what I want to show you here
is when you take the flow
orchestration will guide in lightning
a builder
before
you didn't have any configuration
available.
So now you can
not only rename the components,
you know, who knows
if you don't like the word guide term,
you are welcome to rename it.
And you can also decide
to show some specific
orchestration details
like the run name, the stage
name, the step name.
And what is really,
really cool
is that you can now
hide this for a guide
when there is no work item
waiting for you.
So these components
we ought to make it disappear
from the page.
If there is nothing assigned
currently to the user.
Switching back to our automation
app, I want to show you this, flow,
this new flow experience here.
So I'm going to open one of,
the latest flow I've built,
which is a nice,
so you can see the detail
page for a given flow.
And then from here
I can open the latest version.
And,
what the reason why I was building
this flow is to create some neat suites.
Integration.
And we have a pilot running right now
using this connector
available in flow to connect to his.
Net suite. Really cool to see.
Now I can have, like,
one single action
that get information from that suite.
Getting the creating or says order in.
That's with one single action.
But what I realize is that I need
I probably need default path, right?
Because if anything goes wrong,
I would certainly need,
you know, to take actions from there.
So I'm going to add a false path.
And then from here
I would probably use the amazing use
and email action that, Diana.
Discussed before
and just say, okay, send me an email.
And that's the only
thing I'm going to provide.
I'm just like, okay, I'm kind of lazy.
I don't want to provide
any additional information.
So I'm just going to save this.
And what is going to happen is
we were going to see our brand new
panel here appearing on the left
that shows you errors and warning.
So here you can see that
I can separate errors from warning.
Welling would not block me.
But here, in that case,
I want to jump into the errors.
And I have a link here
that say, hey, send me an email.
It's probably not properly configured.
So that's going to show me
where the error is.
And that's also going to show me
what are the required value.
And obviously I need to have a body,
to send that email.
So let's make sure I provide that.
So just to show you
a quick example here of the the
side panel configuration.
And with that I'm going
to, leave it back to, Kelvin.
Thank you.
Thank you so much, Antoine,
for showing that,
I just have to say,
I think Amol summed it up perfectly.
Just. Wow.
So that was that was the comment.
So great job.
We have a few questions for you.
So thank you for sticking around.
Help us understand,
can a regular Salesforce user
see my flows in the automation app?
So yes and no.
It's basically up to you
admins to decide
what is available
in the automation apps,
but we will never expose those flows
if you haven't given the right
permission, to your users.
So you will have to give them permission
to see flows, to see orchestrations,
to see connections later on.
So all of that is based on
admin permissions. Great.
Thank you for that.
And then following up a little bit to
that is
can I create a flow
from the automation app.
You can absolutely create a flow
from the automation app if you can.
If you still see my screen,
you just have a new button here.
Right now
we are redirecting the user,
to the setup,
which is the current experience,
but expects,
you know, a new experience
coming in our next release.
I say far more on this.
I love that, given, people a preview.
It's awesome.
So you covered this a little bit,
talking about hiding work guides
when there's nothing for the user to do.
And we know you can, but what are the
some of the benefits to doing that?
So the main benefit is
basically saving some real estate.
We have many customers
who have used that component in the past
that complains
that the word guide
is taking a lot of space
on the record page,
and if there is nothing
assigned to the user,
if there is nothing to do,
the word guide basically show
there is no work for you to do.
So it's kind of weird.
So we realize that we better hide
that component
entirely when,
there is no work,
waiting for the user.
So it's it's a bit
it's a bit
surprising for related component
to kind of disappear sometimes,
but I think, you know,
you would get used to it.
And I think it's a lot of,
it's a lot of benefits for the end user
because they,
they have some more space
to see relevant information
instead of a big block,
that shows no work,
no work item for you. Yeah.
And it helps
keep it cleaner for the user,
making sure that their attention
is directed to you.
The things they do need to do.
So, and then it's also
that indicator for them
if it does appear that
they've got some work to do.
So Antoine,
thank you so much for joining us.
To everybody at home,
if you have more questions for Antoine,
make sure you put them in the chat
and we will get them answered.
Thank you again.
So now we're coming back to this studio
and we're going to go to Sam Reynolds,
senior director of product management.
And she's here to set
she is here to share some amazing screen
flow enhancements
and a legend in your own right.
So welcome.
Take it away.
Oh, thanks. Hi, everybody.
My name is Sam.
I'm here to talk to you
about
Screenflow awesomeness
from this release.
So let's see if we got our slides up.
Yeah.
Unless you have been living under a rock
the past year
and a half,
I hope that you have heard
the gospel of reactivity.
It is basically the new foundation
for everything that is going to happen.
Screen flows in perpetuity forever.
We consider it basically
the new platform.
Over the past year
or so, we've been really focused on
enabling you to take advantage
of what you already have in your screen.
You know, so
like components can pass their values
back and forth
and can respond to each other.
So that was general reactivity
and formulas.
What we have moved on to
think about more is like, okay,
but what if
you need to react to something
but you just don't
have that information yet?
You need to reach out
to the Salesforce database,
to some external system,
or you need to perform
some additional logic
that just isn't possible
within the screen.
That is where
we have been working on
something called Action Buttons.
We're really excited to announce
this as generally available.
You might have heard about it
last release,
running this live as a beta.
Basically,
you can put a button on your screen.
That button is going to run
an auto flow
that you
or someone else from your team
has built.
And you basically get all the power
of auto launch flows.
That is just supercharging
any interactivity
that you're
trying to build into your screens.
So for those of you
who have been paying attention
to action buttons,
we do have a few changes from
this release.
One is you have more control
over the button interactions,
so you can actually
conditionally disable the button
so that, you know,
people aren't like running this flow
over and over
when you're not actually ready
for them to run out.
You don't have the right inputs yet.
And similarly, we have, an in progress
loading handler.
So when the action is running,
they can't just like bang the button
and make that flow run 70 times,
which we do not want.
And then the one last thing
that the PM Adam White
snuck in for this
release is a bit of, like, build time,
quality of life enhancement,
if you will.
But it's basically
if you are building the auto launch flow
in another tab
while you're actually adding it
to your screen flow,
you can, have the inputs and outputs
be updated
with a nice little refresh button,
which is super exciting.
I don't have time
to dig into a demo today,
but you are in luck
because on Friday Adam
White is going to be on Admin Release
Readiness Live
and he is going to go into so much depth
on action buttons
you don't even know
to do your
won't know what to do with yourself.
And if you just can't wait
until then, please
check out our trail mix,
which is the second QR code.
Adam has a great blog post,
that's linked from there
that goes into depth on
I think it is about
the beta state of action buttons,
but all of that information
should be enough to get you started.
The second big thing
I want to talk to you about today
is enhancements to repeaters.
Last release,
I was here talking to you
about repeaters being GA.
It's a way to help
speed up your data entry.
Diana gave you a little sneak
preview of the ways
that repeaters can help.
Just generating lists of data without,
you know, having to repeat over,
not having to revisit the same screen
over and over and over again
this release.
We're really excited
to show you a demo of,
how to use existing data
with your repeater.
So with that, I'm actually going to
move us on into my demo.
All right.
So, I'm actually
showing you the exact same flow
I showed you last release,
but enhanced with these new features.
So again, we have,
we are working through an auto
insurance policy.
Last release,
it was creation
only because repeaters
could only create new data.
But now, as you can see,
I have started out with
Lauren Boyles
existing insurance policy,
and we already have
some vehicles created.
So I have a Subaru and Audi
and then three drivers
attached to this policy.
But Lauren has called in and told us
that she actually wants to,
make a change.
She's treated in her Subaru
for another vehicle,
and Carolyn's going to help me.
Ooh, I think she's going big.
Do you have a GMC in there?
We do have a GMC.
All right.
And then we have a bunch
of models in here. So I guess we'll do.
Oh, she's being good
with the environment.
We'll do the Sierra gravy,
grab the black one
and then assume it's a brand new guy.
And then I don't have a Vin handy.
So we'll just cheat with this one.
Right.
And then there,
she has no other changes.
She just wanted to switch out
those vehicles.
So we're going to keep
all the same drivers attached
when I click next.
I have this summary screen I built,
and this is just showing me,
after I submit the
this is the state of things
that will be in the insurance policy.
So I'll have these two vehicles
and then the three drivers still.
So after I submit the
was doing its magic
and if I come over to
the app, I will see
we still have the super record in place.
And that was my choice
to not delete the record, but instead
instead to mark it. Archived.
And we have the Audi
that was there before
and the new GMC Sierra.
Evie. Thanks, Caroline.
Let's get into actually
how this was built though.
So, since last release,
some things have changed in this flow.
The main first bit
is that we have to,
get records for the vehicles
and the drivers
that are associated
with the insurance policy
if the policy already exists.
The real meat of this is in the screen.
So let's focus on the vehicles.
Repeater.
We've added this, new configure data
source section.
So this is how you're going to provide
data to be populated into the repeater.
So we have
the vehicles that were queried from
that got records earlier.
You'll notice
we have this unique identifier
for items.
If you are later going to be taking
the results of this repeater
and trying to update or delete things,
you need an ID,
we are passing that
through for you automatically
so that you don't have to like
expose that ID to your customers
on the repeater. Visually.
That just seems silly to us.
So, how you get the data
from the collection
that you brought in actually mapped into
the components
is going to be very similar
to the regular ways
that you would set your values.
But we tried to make it
a little bit more obvious
which one it is.
So if you're
if you know the name of the collection,
you can just type it as usual.
But if you are not sure,
look for repeater pre-populated items
in the resource picker.
And this is
the collection
that belongs to the repeater.
And then I have access
to all of the fields directly.
So if I'm setting you're at this point
I can map it into the your fields.
Yeah.
So then
at runtime,
as you saw in the demo earlier,
for each item
that exists in the collection,
that would for each vehicle
that was grabbed from the database,
we are going to generate
one instance of the repeater,
and then we are going to use
whatever mappings
you supplied in the components
to say which fields should go where.
The other major change with
this enhancements is
we are still unfortunately
using loops for repeaters.
I'm sorry we couldn't
quite get transform support yet.
It is on my list.
It's going to be so much easier
to deal with this once
you have that, but.
So we're still looping within loops.
You'll see,
instead of just one sub collection
where previously we had,
I think, added
items or items last release,
I can't remember.
Now we have four removed items,
hopefully pretty self-explanatory.
This is going to be the list
of all the things
that your user removed
that were pre-populated
or were existing,
and then the other three
are more focused on
like what was on the screen.
So if you want to do
the old school way,
you can work with added items
and go to a create,
and you can work with
pre-populated items
and go and do an update.
But we would highly recommend that.
Instead you do all items,
which is going to be
the combination of those two.
And then you use
what Diana just demoed earlier.
Sorry would be so nice
if we had scrolling, wouldn't that?
But yeah, so and using our Upsert
or our create and update
at the same time, let flow figure out
which things need to be updated
out of this collection.
So I've used all items
for both vehicles and drivers.
And so I'm just supplying
all of the things,
to this create records.
And based on the record ID
which we
the repeater was passing down for us,
we can tell
which ones needs to be created
and which ones updated.
And you just have one node
and one DML operation, which we love.
Love saving limits.
Right.
That's a wrap on my repeaters demo.
And so I have one more slide
because there are a couple of things
I want to leave you with.
As like kind of nice little bits
in the release.
The first thing is
if you're using choice lookup
or like lookup components
in flow in general, just
we have added multi-select
support to the choice lookup component.
It is actually going to be
the first choice component
that you can choose to make it
single or multi-select,
which I think is very cool,
and I want to do more of that
with more choice
components in the future.
But generally it's
going to look much like
how our other lookup component does
when you put in a multi-select.
Mode.
Second thing is an enhancement
to how custom components
get rendered in the screen editor.
From a preview point of view,
we heard a lot of feedback
from the community
that it just what we had wasn't enough.
All it was telling me
was, oh, this is a toggle
or this is a quick choice,
or this is a data table,
but I have six of them
in the same screen
and I can't tell
which job each of them is doing,
especially if I didn't
build the screen myself
or I built it six months ago.
So now we are exposing the label
or the API
name of that specific component
that you or your team member built
so you can better understand.
Hopefully it's,
the label, an API name or well done.
Which job that it's doing for you.
And that is a wrap for me.
Wow.
Okay, so
I have to take a beat
because the chat is going crazy
with the love of the new features.
And I knew this would happen,
but as my first flow show,
I feel like
I have to give you
all the props that are coming in.
So here's some of my favorites.
Squire says feeding repeater
elements with query data is so amazing.
Every enhancement to
this base makes my life as an admin
so much better.
So that is amazing.
And then this other one,
already excited
with all the new flow features,
all the pain points
have been addressed in
flows of Winter 25.
So you can take vacation?
Yeah. Okay.
And then this one's great.
David says sections in repeaters
will be mint when it happens, so vote it
then you got to put it up.
Yeah, absolutely.
So, as you can
tell, we are in San Francisco.
We are in the tower.
So if you do hear noises,
those are live.
We're not piping them in.
So, and Andrew wants to know,
where's your lamp?
Still at home.
So you can't bring the lamp every time.
You guys, it's not special.
So it is serving its purpose.
I love the land, I love it.
Oh, right.
I mean, nothing like, get a little lamp
and we'll get you a lamp. T shirt.
Yeah, he's got a t shirt on.
Mini lamp.
That's a little easier to carry on here.
Just something.
Maybe a
little less unwieldy,
but the lamp is still very much
in use, so. Great lamp.
Yeah, I've heard
Andrew is good at t shirts.
Okay, so last but not least,
product Manager
Vidya Ravindra is here
to show us Einstein for flow.
You. You can't wait for this one.
How you can build processes
quickly using AI props.
So over to you Vidya.
Thanks Carolyn
and thank you so much Dianna.
Antoine. Sam.
Those were three really hard acts
to follow.
Really three legends.
So hoping that this goes just as well.
But super excited everyone
to share our brand new updates
to Einstein drafted SLOs,
which help
you quickly build flows
with just the aid of
natural language prompts.
So plain English,
we're trying to make flow building
simpler than it's ever been before.
So all you need to do
is describe the flow
that you'd like to build.
And Einstein
will use our in-house LM,
which quick aside here
I want to mention it's
trained on best practices.
Never touches customer data.
This is so important to us.
Feel free
to ask more questions about that
to create a fully editable draft flow.
So we've heard from both experienced
and newer admins
that Einstein for flow helps
with the ramping
up on how to build flows,
and also ensures
that you're not starting from scratch.
Which I don't know about you,
but for me, that's super,
super important.
And yeah, we're just really,
really excited
about the positive reception
that we've already seen
with the beta program so far.
And we can't wait to make this product
generally available in the spring.
We've already shipped the ability
for customers to build flows
with both standard and custom objects.
I hope folks have been trying it out
and giving us feedback on it.
And most recently
we made improvements to our AI model,
making it more performant
and more accurate.
And we're going to be
shipping our brand new edit,
a prompt feature,
which I'm going to be doubling
a little bit.
And I love this feature.
I hope you guys do too.
We're also on the cusp
of releasing a much awaited,
much requested feature
in the next release,
which is Flow Summarization.
So that's coming up around the horizon.
Feel free to ask
more questions about it.
That's going to be really,
really cool and a game changer.
But before I move on,
I just want to make sure to point out
this really awesome customer quote
that made me really happy
on what we have so far.
So no matter how skilled
you are at flow,
it's easier
to have something to start with
than to start from scratch.
So that was a lot.
That was a lot of descriptions
of the new features that we have.
But that's not all.
To top it all off, we're also releasing
Einstein Drafted formulas
in beta this release.
So when you're in Flow Builder
and you're editing
or creating an element
and you need a formula,
we now have the capability
to type in a prompt
and have Einstein handle
the actual formula
building part for you.
So with this improvement,
what we see is fewer mistakes,
less context.
Switching to second guessing.
And I think this future
is really awesome.
I'll be demoing this as well.
But super quick aside,
before I get into demoing,
if you want to get your hands on this
or Einstein drafted flows,
please make sure you have the Einstein
one license. Talk to your years.
We would love for you to try this out
and give us as much feedback
as possible.
Okay, so now for the fun part.
I'm going to go ahead
and hop
into our first demo
of Einstein for flow.
So the first thing we do
is we create a new flow.
And you can see here we have the option
to let Einstein help you build.
So I'm going to go ahead
and select that.
So you can see here that we can get
started with some sample prompts
and try these out.
So these also give you
some really great examples
of how to write a good prompt
and a major key of this product.
And making sure
that you're leveraging it
well is making sure that you're
writing a really awesome prompt.
So feel free
to ask more questions about that.
But it is something that really is
a game changer
when using Einstein for flow.
But I pasted in my own prompt,
which is using some interesting
custom objects,
create a flow that sets the bike
build mSRP to 3000
when the category is equal to cyclocross
and gruppo is equal to reinforce.
And if you don't know what this means,
this is a prompt for the bike
enthusiasts
who are potentially in the audience.
So shout out to you guys.
All right.
So we create that draft flow.
Watch it generate it.
Once our draft flow has been created,
what we should be able to do
is go ahead and click
into each element
to see that they do, in fact match
the description that we provided.
So starting with the start element,
what we see here
is that category is cyclocross
and Gruppo is Sram force.
So perfect.
Exactly what
we stipulated in our prompt.
Now we should be able to click into
our update record
and see that mSRP is in fact 3000.
So literally perfect
exactly what we wanted.
But
what if we wanted
to edit our instructions
and maybe change things up a bit?
So let's try setting mSRP
to like 6000, for example.
And for those of you
who don't know mSRP suggested price.
So this is quite the expensive bike,
but we're going to go ahead
and create this flow anyway
and just make sure that it does,
in fact do what we expect it to.
This is the real test.
Clicking into the element
and seeing that mSRP 6000
will tell us that this feature did work.
So fingers crossed everyone.
And yes, it's 6000.
Exactly what we wanted.
But if for some reason
you wanted to switch back,
you can always
just use the arrows over here
and your previous flow
will go ahead and generate it.
So you can see I verify
by going into the update element
and see that it's once again 3000.
So perfect.
That is a very quick
overview of editing.
But I wanted to point out
a couple of other things here as well.
You can give us feedback
with the thumbs up and thumbs down.
If Einstein, for whatever
reason, didn't quite meet your needs,
you can click on the thumbs down
and go ahead and explain why
here, tell us a little bit
more and give us feedback
so we can improve the experience.
This is so important to me
as we work on
developing towards
GA, so please, please do this.
You can also go ahead and
copy the prompt and save it.
Safe Harbor.
We're working on
some more sophisticated ways
to save a prompt
and save it in your description.
But just a little sneak peek.
We can talk about that later.
If folks have questions.
And of course,
if for some reason you want to redesign,
feel free to just go ahead
and start over.
And that was the power of Einstein
for flow
and our brand new editor prompt feature.
And that's not all though.
I have one more demo
and this one is also pretty quick
but very powerful.
So what we're doing here
is starting with the sample record
triggered flow.
And this is triggered
whenever a new contact is created.
So what we want to do in this example
case is grab
the email of the contact
and save only
the domain under the description.
So in order to do this
we need a formula.
So I'm going to create
a resource right here.
Data type is text.
Let's call it something simple like
get domain okay.
So this is where Einstein drafted
formulas really comes into play
and does the work for me.
So I can go ahead
and just click on the sparkle
icon on the right hand
side of the formula builder
and enter a natural language
just description
to tell you exactly what I just said.
So that is in this case, return
what is in.
Insert
a resource email
after the
bat symbol.
Cool.
Okay, so I can go
ahead and click create.
And that should pop up in this box
over there okay I see it right here.
We have to make sure to check the syntax
to make sure it's valid okay.
Looks good.
So we can go ahead and click done.
And last but not least we can
go ahead and use this formula
as the value for our description.
And that's exactly
what we want it to do.
That was our awesome
new Einstein Drafted Formulas feature
coming to you very soon.
And now I can go ahead
and pass it back to you.
Carolyn I hope that was helpful.
That was awesome.
Thank you. Vidya.
As we new, viewers have questions,
if you do have more,
please go ahead and post them.
In Salesforce Plus.
But let's talk a little bit
about maximizing
chances of Einstein producing
a relevant usable flow.
How do I write a good prompt?
That is such a good question
and something that I think about a lot
as well.
Writing a really great prompt starts
often with the words
things like create or generate.
Being really specific
about the type of flow
that you want to build.
And you saw with the prompt
that I just put together for the demo,
if you have custom objects,
make sure to really like
include all of those.
Be as detailed as you possibly can.
Specify names.
Also,
another thing I'll note
is it's always really helpful
to have a human in the loop
to review your flows
for correctness,
especially if you're touching
customer org data.
It's just always
Lmms can always hallucinate.
That's just the nature of how they work.
So it's just always,
I think, good to have that extra layer
of protection in there. Yeah.
So being very specific,
it sounds like the
first piece of advice,
making sure you're placing guardrails
is the second piece of advice.
And then having a human in the loop
and checking is the third thing.
So those in combination,
should help you
produce relevant and usable flows.
Okay.
So we always have questions around,
data, data and model.
So what kind of data do you use
and how was the model built
and how is it trained?
This is also a great question.
I also would be curious about this.
When we have well,
first of all, we use an in-house model
that was created
and tested entirely by our awesome
AI research team.
The backbone of the model is
Mistral, Nemo,
and it's fully trained on data
that we also create in-house as well.
And we remain very firmly committed
to never training our labs
on our customer's data, as I mentioned,
which means that this is quite
the iterative process.
So for things like flow
generation, flow summarization,
things like that,
we make sure to create our own use
cases, our own prompts,
our own, resulting flows,
and make sure to test against those
in a very thorough way.
So that all happens in-house.
We never use customer's data for that.
Zero copy is super important
when it comes to this because you are
you're taking actions, and automations
around that data.
So your trusted protected data
within Salesforce.
So that helps to
I actually
I have an online question for you.
Sarita wants to know how complex
can Einstein for flow get.
That's a great question.
So we're definitely,
as I mentioned like training process
a little bit.
We're working on more
and more sophisticated use cases.
So I mentioned already that you can use
standard and custom objects.
There's actually no element limit.
The last time we presented RL
I think we did have an element limit.
So it's cool
that we're able to expand beyond that.
Now that's super awesome.
You can use things like formula
sub flows.
So there's all sorts of things
that you can do.
There are also things
that folks have suggested that.
And by the way, please feel free
to keep
adding things to the ID exchange.
So we get more
and more of this feedback.
But we hear you there
definitely things
that you guys want to be able to do that
we don't have the capacity
to do quite yet,
but we're absolutely working on
training our model
with more and more sophisticated
use cases.
And yeah, feel free
to give us more suggestions
as we get towards GA. Great.
And I think we also love
to hear from customers
on what they're doing
and what's working, what their
what they're testing.
So how can people
give you that feedback.
So I love to see customers
playing with these new features
and then giving us ways
that we can tell everybody else
what they're doing.
So how would you like them to connect
with you?
Yeah, absolutely.
Idea exchange is
absolutely the best way.
Also, for those of you
who are already using these features
that thumbs up, thumbs down,
especially the thumbs down, I,
I actually like to see the areas
where we can really improve.
And if you give us more
detail around that,
we would love to see it too.
And for those of you
who don't yet have it,
like I said,
please make sure to get the Einstein
once you and try it out for us. Yes.
All right, I'm going to give you
a little bit of feedback
from online, Dan,
and I'm going to try and get this right.
He just says love with lots of letters.
So, he absolutely loves it.
And then Mitch
also said
Einstein drafts
and flows is made for Mitch.
So get in there.
Tell us all about that.
Can't wait to hear.
So final question for you.
Since you're new to the team,
which I never would have guessed,
what has been
the coolest thing about
working on Einstein for flow?
I love this question.
First of all, obviously
having amazing colleagues
like Diana, Sam, and Antoine,
the flow team is amazing,
but also being able to interact
with the flow.
Now, I was at Dreamforce
and while I was new to the team
then just hearing about
how much you all love the platform,
how much, you're so dedicated
to the different features
and the feedback that I got on
the new product that I'm on
has just been amazing.
So please keep it up.
Please feel free to give me feedback.
And yeah,
we want to put out the best product
possible in GA.
Yes. Great.
Actually, there's one more question.
I'm not going to let you off that easily
because Naveen
has a really good question.
Can we create orchestrations
and other flow types
using Einstein for flows?
Right now we can't use orchestrator
with Einstein for flow,
and that's something
that we can absolutely
think about a little bit more.
We, like I mentioned,
we want to add more sophisticated
use cases to the roadmap,
but it is quite
the iterative process
in terms of training.
But please do I will note that down.
And please do add that to the idea
exchange as well.
Great, Vidya, thank you so much.
We will turn you loose.
Really, really appreciative
of all of your work
and sharing that with the audience.
So thank you. Thank you.
All right.
We've been getting a lot of questions.
So I'm going to navigate this iPad.
We want to welcome back
Diana and Sam
to get some of these questions answered.
So I'm going to start with Sam.
Because
repeaters came up a lot in the phone
would you say came up repeatedly.
Oh, okay. You I love it.
Yeah I always fun
so given a
little preview,
what's next for repeaters?
What is next for repeaters?
So a couple of things
that I really want to deliver.
One of them,
as I mentioned in the demo, is,
adding support
for the repeater outputs in transform
because I think it's
going to make it so much easier
to deal with those outputs.
And we all hate loops
with their parts and,
they are sometimes necessary.
We could make them less necessary.
And then the other thing
is actually something
that was mentioned.
And another question,
which is allowing sections
and repeaters to interplay
with each other.
One of the biggest requests
that I've, well,
the most frequent requests
I've heard since launching repeaters
is that you all want the ability
to do multi-column
layouts inside of repeaters.
Diana asked me that yesterday
in my demo the other day. Yeah.
When you're building or demo.
So requests
don't always come from the community.
Sometimes they'll
come from inside the house.
Yes, yes.
So those are kind of like
two really big top of mind things.
Some other things
further out
that I'm thinking more about is,
you know, adding support
with prefilled for external data.
So right now
it only supports, Salesforce
based collections.
Things like,
I really want to get to make, repeater
support reactivity more fully.
So adding support for reactive formulas
actually requires
that we basically
create
this idea of a resources contextual.
So in order for us to make,
make it so
that you can have a reactive formula
inside of a repeater
that's responding to other things
inside the repeater,
the formula has to know
that it belongs to the repeater
and can't be used in other places.
And so this thing
that sounds like so
straightforward is actually a whole,
like, infrastructure mess that we have.
For me
and being a user for so long,
I sit on the other side of it going,
this is so awesome. It's like magic.
I see what you all do to build it
and then what
our admins and devs
do to make it a reality.
It's pretty funny
because I just did them
like this is so easy. So so it's great.
All right.
We are going to shift gears
and I'm coming
to the other side of the table.
Any plans to allow
entry horizontal like editing in?
Oh, that's for Sam. Sorry.
Any plans to allow entry horizontal?
Like editing the table
for data table?
You can,
if this is about, inline
edit for data table
is something we do want to do.
We are.
And I'm trying to remember
if the reason we haven't done that is it
might be because of like some base
component support issues we have.
We use the data table
lightning base component.
So some of the things like having
pick list
and I think lookup field support.
Because you know,
data table doesn't support it.
And others are it just
we haven't had time to prioritize it.
And I cannot remember which one.
That should be honest.
But it it is absolutely like,
on Adams white
Adam White's list for things
that we want to do to data table.
So I'll bookmark that conversation
right away. Awesome.
Has to send that question
to the next time you add that to it.
Okay. Diana, over to you.
Is there only one comparator
or could we do last name
and external ID?
There is only one,
so otherwise
you would have to do the logic of
if one's there, one's not there.
What if they're different there?
You get into a lot of
sounds like another loopy issue loop.
Olivia. Yeah, okay.
So is the up
upsert functionality
available only for Screenflow
or for other types as well?
No.
It's available
for all the core major flow types.
I think
there's probably not
field service available,
but everything else we can expect.
Yeah. Great.
Okay.
Now we're going back to say,
you know, there's only two of you here,
so I just get existing. Yes.
These are always
my favorite best practices
or tips you can share about
how do you use repeaters
without creating duplicates,
duplicate sets of data.
So if someone decides to move back
and forth
between a screen flow multiple times,
how does that oh, I
so that's a really interesting question.
I mean, I think that.
Using Upsert or this like
try and have flow
figure out
which things need to be updated
based on like
is there a matching
record is a really good starting point.
If you are,
I wouldn't be so worried
about like backwards
and forwards navigation
if like we had filled in some stuff
and we moved forward,
and then you go back
and make a change to that data again.
It's just like you're still making it.
We're still working with like,
what is the latest data
that said,
generally
in our overall like Screenflow
best practices is after you have
data operations happening,
after you have like a creator update
or delete happening, we highly recommend
not allowing the user
to go back over that.
So if I have like a screen
where I'm taking stuff in
and I'm creating a record
and then I have a confirmation screen,
I want to turn off the back
button on that confirmation screen
because I am telling you
what has been created.
The way that I built the repeater
demo was
I put the confirmation screen
before the DML happened.
So it's it's a chance to like,
that's why I left the back button on,
because then I could go back and like,
oh, I didn't mean the GMC Sierra EV.
I meant, like, the regular Sierra.
That's not an EV or something.
And I can make the change,
but it is in our
like screenflow best practices set.
Like after
you do a create or an update
like don't let your user go back
because you are going to end up
in this situation
where you have duplicate data
or you're deleting the
wrong things, or you're
okay.
Great.
We are coming back to use,
Diana here recommendation.
Squire wants to know what's
a recommendation
for a team's first opportunity
to convert a loop to a transform.
So where should they start?
Everyone should start here.
Response is what we're looking for.
That's a good one.
That's a really good one.
Now,
I think there's a lot of people
in the chat
who might have some ideas too.
That might be even better.
I, I mean, that idea, I'd one I think
if you're using an operator already,
that's a really simple one.
You probably have a dedicated loop
that's just doing that.
So that's why I really like that tip.
And it's pretty straightforward.
It's, it applies to most.
Yeah, yeah.
Also, I would say sort of like record
if you're kind of
record collection
mapping between the same
object, that can be really, manual.
And you have to go through
each assignment and remember,
make sure you have
all the fields, things like that.
So that would be another one
where I would say it's just really nice
visually
to get all those lines in there,
and you can kind of scan
and know what things are happening.
I think those are
two places
where I would start with transform.
Great.
Do you have any other for
loop, specifically
the thing that's coming to mind
is an assignment replacement,
not a loop replacement.
But like we actually have done
some performance testing and transform
was like
ten x more performant than a loop was.
And so even if you're
doing like really basic
things inside of your loop,
it's worth considering.
Like transform is capable of handling
this use case.
It may be worth it
just for the efficiency efficiency gains
and like cleaning up your canvas.
Yeah, both of those
helps with the scroll.
Really?
I'm getting there.
All right, let's stay with you, Diana.
Jeff Green, said I'm glad.
Flow validation is looking
a little easier to use.
Is there any plan
to specifically add
unit testing for flows,
or is it still going to be roll,
roll your own on that?
Well, that sounds familiar to a question
that was asked a few weeks ago
at, true to the core,
at Dreamforce that I think
was a broader question than this one.
But,
I would definitely tell people
to check that out.
It's a mystery to the core.
Because I think
Alex Edelstein gave a more broad answer,
but I would say,
we have heard
loud and clear
from the community
that even more than just unit testing,
but the entire kind of life cycle,
we're putting all this really powerful
new capabilities into flow.
You can automate more and more
and you do need to be able
to test
more and more to make sure
that that automation is high
quality, isn't going to break,
isn't breaking each other,
all of those things.
So that is absolutely an area of focus.
I can tell you.
Sam and I are we're
passing around sticky notes
last week talking about this.
So it is an active,
topic of conversation.
Great, great great, great.
Okay.
Sam, coming back to you.
Well, look up component.
Be available for mobile
soon in Screenflow.
Are they not?
Now, that's,
I'll have to look into that about why
it isn't working.
So we'll check.
Yeah. So available.
And we will.
I will look into that,
for the trouble
is that we have three lookup components.
There is kind of
the one that is just called lookup.
And it is based on like
a relationship field, that one.
I think as far as I understand,
it does work in mobile.
And if it doesn't, it's
something to do with whatever
the underlying base component
is that we're using.
And that is generally
going to be the problem
with most of our like,
responses to mobile questions is like,
not all of it's in our control.
Then there is the choice
lookup component,
which also should be
supported in mobile.
And yeah,
so my general answer is like
I am confused
by this question,
I need to look entirely into it,
but I want them to work.
And we will mark that one
and we will make sure we get that answer
because it sounds like
we need a little bit of research.
So that's, not a problem at all.
Diana, lots of questions
about email limits.
I think it's exciting for people
or the email limits
for how many emails
we can send via automations
increasing as well.
They are not.
That's the short answer.
I would say
the longer answer is
generally we're calling into
email capabilities
that exists on the platform
that are maintained by other teams
and used in multiple places.
So generally
an idea
exchange item for that,
we would recommend
filing on, email and not on.
Sometimes it gets a little confusing.
Sometimes we find things in other parts.
So that's why I just like to tell folks.
Yeah.
So an increase in limits like that,
we should probably go
to an email team
is why it's very valuable
for ideas to be granular.
Yes.
Rather than like a,
like a list of, like,
5 to 10 items
that you wish
were better about flow email
like a very specific idea about like,
I want to have higher limits
for this very specific thing.
And then we can route
that to the correct team or like
get it merged in with an idea
that is relevant to like
actually how
we would solve that problem. Exactly.
That is great advice.
Sam,
I think we're gonna come to you
with the final question I see.
Is there a plan to help
prevent duplicates on the repeater?
If a user attempts to add
a duplicate in the single transaction?
So different than the back button.
But going back to the insurance example,
what if the user attempts
to add the same Cierra twice
at the same time? Yes.
So that's a very interesting question.
I don't have current plans for it,
but I definitely understand
the use case and well,
think about it.
Yeah, I can, I can see like
in particular,
we have talked in the past
about like a product return scenario.
And I can definitely see
something like this
that like,
you have a list of all the products
that are returnable.
And once you select it for one repeater,
it shouldn't be selectable in the other.
And I'm guessing
in order to do that
we need
significantly more reactivity
to be supported in repeaters.
And also something
like a unique identifier.
A Vin number in your example
is a unique identifier
and doesn't repeat itself.
So having those things will also help.
So so
I just have to say
it has been a pleasure
and I am so excited,
that you all like I just
I see the reactions from the audience.
There's a reason why you all are
the favorites of time.
So, even though we are wrapping up
this particular show,
you can still ask your questions
in the trailblazer community.
Hashtag Salesforce RL.
We'll make sure
you get an expert answer.
And thank you so much for watching.
As always,
we look forward to your feedback.
It helps us improve
and create the content that you want.
So scan
the QR link on this screen
to take a short survey.
As a thank you.
You'll be entered into our sweepstakes
to win
one of five Salesforce
certification vouchers.
And we've got more on Winter 25.
Tomorrow
we'll be back with our Developer
Preview at 9 a.m.
Pacific Time,
followed by service Cloud at 11.
And we'll round out the day
with our bonus episode
featuring Health Cloud at 1:30 p.m.
Pacific,
and then come back on day
three for CRM analytics
and our admin preview.
Or catch
all of RL on Salesforce
Plus coming up later this month.
Discover Agentforce
what I was meant to be.
You don't want to miss this, so
scan the QR code on your screen
to register now.
The live launch event
kicks off on Salesforce
Plus on October 29th at 9 a.m. Pacific.
Here from companies
that are using autonomous
agents to take action
and drive results 24 over seven
and get ready to build your own,
you won't want to miss it.
I'm Carolyn Bathauer
and we'll catch you
next time in the cloud.
Resume AutoScroll
Link copied to clipboard
Salesforce Flow Winter '25
Discover a new way to manage and validate flows with the new Flow validation experience. Gain insights into the performance of your automated processes with orchestrations in the Automation app.
Starring
- Antoine CabotSenior Director, Product Management, Salesforce
- Diana JaffeSenior Director, Product Management, Salesforce
- Vidya RaghvendraProduct Manager, Salesforce
- Sam ReynardSenior Director, Product Management, Salesforce
Developer Preview Winter '25
Learn about the latest developer features including how to capture more events with new Data Cloud integration upgrades. See how you can improve developer productivity and code quality with new Lightning Web Components and TypeScript. Plus discover our top innovations in Prompt Builder, Agentforce, and more.
Health Cloud Winter '25
Discover how you can improve productivity and effectively manage patients with the latest Einstein for Health Cloud innovations. Learn how to enhance your CRM Analytics dashboards with interactive, engaging, and actionable content by incorporating Widget Flow Interactions. Find out how to build dashboards and calculate insights with Health Cloud’s Connected Ecosystem.
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.
