Play
Show Navigation
Show Transcript
00:00
Play
Seek 10 seconds backwards
Seek 10 seconds forward
00:00 / 01:31:45
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
from San Francisco.
I'm Gillian Bruce,
Principal Admin
Evangelist at Salesforce
and super nerd,
which means I am so
honored to bring you
Release Readiness
Live because this
is where we to get nerdy.
And we get to cover
new product innovations
coming your way in
the next release.
But before we get into
my happy nerd zone,
I need to take a moment
to remind you to only make
purchasing decisions
based on currently
available features
and functionality.
Now with that
covered, thank you.
Thank you so much
for joining us today.
Thanks for investing
your time with us
to learn about what's
coming in Winter '24.
And also thank you
for all the feedback
you provide us.
Your feedback is what
helps our technology
teams build
solutions centered
around your experience.
Now we've had an
amazing lineup
of Release Readiness
content for you.
We kicked off admin
and developer Release
Readiness Live at
Dreamforce just a couple
of weeks ago.
Even though it seems
like a little bit
farther ago than
that for me,
but it was just a
couple of weeks ago.
And this week,
yesterday, we
covered sales and
CRM analytics.
Just this morning,
we covered service.
And now, the show you've
all been waiting for,
flow.
That's what's coming
to you right now.
Now we're going to spend
the next hour together
with our product
managers in person
here in studio in
San Francisco, who
are going to be
giving us live demos
to highlight the top flow
features in the Winter
'24 release.
We're going to be talking
about flow orchestration,
HTTP Action and transform,
screen flows, triggers.
We're just going
to let it flow.
And it's not just about
us here in the studio,
it's about you.
We want to answer
your questions
about these new features.
And we've got a special
correspondent here
in the studio to ask
your questions live.
Waseem, how can people
ask their questions?
All right.
Thanks Gillian, and
what is up, flownatics?
I'm Waseem from the
Salesforce Social Media
team.
And today I'm here to help
you get all your burning
questions answered about
the new innovations
in the Winter '24
release, so you can
learn how to use them.
So what do you want to
ask our product experts
today?
You have three ways that
you can submit a question
and get it answered live
right here right now.
You can, one, head over
to the Release Readiness
Trailblazer Community
and ask your question
using the #SalesforceRRL.
Two, drop your
questions right here
on Salesforce Plus in our
new Q&A tab, or, three,
join the conversation
on X, formerly known
as Twitter, and
ask your question
using the #SalesforceRRL.
We'll be pulling questions
from all three sources.
And really, don't be
shy, don't hold back.
Ask all your
questions because we
want to know what
you're thinking about.
And also if you
have any memes,
GIFs, if you want to
take some fun screenshots
of silly moments or any
exciting innovations
that you see today
on our live stream,
share those too.
I want to see them.
All right, looking forward
to seeing your questions
Flownatics.
Over to you Gillian.
Thank you, Waseem.
Now for those of
you who turned
in this morning
for service,
you know that we had a
little bit of problem
with me seeing the
questions from the Q&A.
Don't worry, we fixed it.
So we will definitely
be answering
a lot of your questions
live here in the show.
So we're going to
go ahead and get
things kicked off.
We have a lot to
get through today.
So to start, we're
going to start
talking about HTTP
Action and transform
from our one and only
Henry Liu, Director
of Product Management.
Take it away Henry.
Thank you, Gillian.
Yeah, so I'll start
us off with the latest
and greatest
integration enhancement
in this release.
And I have two topics
today, HTTP Action
and also the
transform element.
So the first announcement
is that we now
are getting GAing the
right methods of our HTTP
Callout.
So now you can do
get POST, PUT, PATCH,
and DELETE.
So if you need to have
a quick and simple way
to integrate with
your external system,
now you can do so
directly within flow.
Second is our brand
new transform element.
So we're really
excited about this.
It works very well
with HTTP Callout.
Anytime that
you're working
with complex data or
hierarchical data,
you now can map
and visualize
and transform your data
all within one element.
Now since this
is the first time
that we're introducing
this element,
I do want to take a
quick second to go over
our roadmap with you
so you can see what
we have in store for you.
Next release will be
working on aggregation,
then we want to be able
to join two different data
sources together.
Next is that we want
to be able to do
multiple transform,
stack them together
so you can do
things like filter,
sort, and join then
aggregate or anything you
want.
And lastly, we
want also to be
able to have live
preview as you build
with your sample
data, so you
can have live feedback
of what you're building
and also be able to
create a custom data
shape on the fly.
So this will be one of
the most powerful element
in flow besides
the action.
So let's just dive
into it and see
what this is all about.
So let's go to the demo.
And here, I have a record
trigger on the product.
So what this
flow is doing,
and I want you
to just look
at the async path for
now, is that this--
is that any time that you
are creating a product
within Salesforce
is also going
to create the same product
in your external retail
system as well.
And here this is where
the magic happens.
This is the action itself
that is calling the API,
hitting this endpoint.
But let me go
through and start off
with a fresh
one to just let
you know how easy it
is to create a HTTP
Action from scratch.
So you go into
the Action click
the Create HTTP Callout,
name this thing,
name product, and then
choose a name credential.
And now you see all
the methods here
that you can use.
And I'm going
to choose POST
because I'm creating
this product
within the
external system.
And the URL, you can
either use the API spec
that you probably
are given too,
or you can use the Postman
to get that information.
So I'm going to
copy and paste.
And the next thing
that you want to do
is to specify your
POST body data shape.
And we make this
very easy for you.
All you have to do is copy
and paste a sample data,
and it will automatically
convert this data
into the data shape
that you need.
So same thing for
the response I'll
go into here.
Copied and paste.
And now you have
an HTTP Action.
Now I already
have this defined,
so I'm not going
to save this.
And let me get back.
But once you create that,
this is what you see.
And here, we need to
feed in the actual data
itself.
And before we have
the transform,
you would use the
assignment rule--
assignment
element for this.
And now we have
the transform that
does everything for you.
So here on the transform,
on the left side,
this is the
source data, which
is the dollar record, the
triggering record that's
happening.
And then on the
right-hand side
here, this is
the data shape
that you need to pass
into the actual action.
So it's pretty easy
to assign the fields.
All you have to do is
click on the socket.
So let me just delete
some since I already
did this to show you
what this looks like.
You can either go
from left to right
or right to left.
So here in the
description,
when you click
on the socket,
it will tell
you what fields
you can and can't map to.
So it gives you a little
bit of guardrail there.
So here I can map
a string to string.
And if I go from the
right, the price,
this is a number.
So you see it can't map
to any other fields except
for number field.
So I'm going to map
to the MSRP field.
And that's all
you have to do.
But if you want to
transform any data
in between the
mapping, you
can easily do that with
the Formula button here.
So if I click
into here, you'll
see the Formula Builder
that you all know.
And you can even
check syntax here
to see if this is valid.
And when you
come back, you'll
have this icon
telling that there's
some kind of
transformation going on.
So that's a really
quick example.
Let me just go back
and do all the things
that I just did.
So I can go through
debug without saving.
And I'm going to debug
the async path here,
and choosing the product.
So as this run,
one thing to note
is that HTTP
Action, you can only
do this if you're
using a record trigger.
You can only do this in
async path or schedule
path because we don't want
to hold the transaction
in the immediate path.
So here it has ran,
and it's completed.
And in the
transform, you'll
see the source data
with all its data.
And this is component.
So if you have nested
objects and collection,
you can actually
collapse and expand them
if you need to.
And then on the
bottom here, this
is the actual
data for the body.
So it's going to be
passed into the action.
And the action,
this is the result
of the action
with ID here.
So the next step,
what I'm doing
is basically taking that
response, grab the ID,
save it back into the
Salesforce product
records external ID.
Yeah.
So that's a very
simple use case working
with one single record.
But if you need to
work with collection,
we made this
even easier now.
So without this,
before, you
have to use the loop
elements with loop
variables and also
assignment within it
but now, this is exactly
the same experience
with a single record.
But now it's
with collection.
So the only difference
you see here
is that there's this
collection scoping
line that tells
you, you're
going with collection.
And you'll map
exactly the same.
And if you want
to do formula,
then we have this added
syntax with the bracket,
dollar sign each item,
and this basically
tells you that you're
working with a list.
So with those
two example is
working with
Salesforce data
to a custom data
shape, but you can also
flip them and work with
any kind of data shape.
So here if you
are grabbing data
from your external
service and you
want to save it into
a Salesforce record,
you can do so
with the SObject
on the right-hand
side as a target.
And if you want to save
that, all you have to do
is just pass the
automatic output
of the transform into
the Create Record.
And that's how easy it is.
So this is the first
time that we're
announcing transform.
We will love to
get your feedback.
Let us know
what you think.
Back to you Gillian.
Thank you so much, Henry.
Wow!
That was a lot.
And I think it's
really, really wonderful
to see all these new
opportunities that
open up with HTTP
Callouts and transform.
It's amazing.
And I bet the chat is
also pretty amazed.
So Waseem, what's
happening in the chat?
Wow is right.
The chat is popping
off over Henry's demo.
People are chiming in.
Flownatics are here from
India, France, Sweden,
Chile, Germany,
Texas, Hawaii.
The list goes on and on.
And they got their
questions, comments,
and support.
One question I'm
seeing pop up
is, does HTTP
Action or transform
support XML format?
Yeah, that's a
good question.
So we are looking into it.
So it's actually not
on a roadmap for flow
since this is part of
the external service.
But if you want
that capability,
let us know and
we'll look into it.
OK.
Great.
Henry, you got a
lot of questions.
We're not going to get
through them all right
now, but we're going to
go through a few of them.
Here's probably
an easy one.
Hannah wants to
know, where can we
find documentation on
how to use HTTP Callouts?
Yeah, so we
have help docs.
And we most
likely are also
working on a
Trailhead around this.
So, yes, online
is the best way
to look into that.
Documentation Trailhead
coming soon, forward
looking statement.
OK.
We've got
another one here.
This is also about
HTTP Callouts.
Is HTTP Callout and flow
is intended to replace
outbound messages?
No.
So outbound messages
are still supported,
so you still can use that.
But you can have a
little bit more variety
and different support
with HTTP Callout.
Similar connected
question.
This is actually
from Angela.
Will HTTP Actions
have an impact
on API call limits?
Yes, so it is
using API limit.
OK.
See.
Good to know.
This is why we ask
questions here.
OK.
I'm going to ask you
one more before we move
on to our next section.
And don't worry,
we're going
to continue asking Henry
all of the questions.
So stay tuned.
We just have a lot
to get through.
OK.
Last question before
we move on here.
This is a question
from Tara.
Tara asks, can
you transform
between custom objects?
Yes.
So if you're talking
about custom object
as in like Salesforce
custom object,
yes, you can
go from SObject
to SObject or
custom data shape.
So it's Apex-defined
type basically,
Apex-define type to
Apex-defined type or any
of the combination
you want.
OK.
I like it.
OK.
We're going to ask
you more questions.
But for right
now, we're going
to keep moving on
to our next section
because we have a
lot to get through.
So now we're going to
get into screen flows.
I know it's a
Flownatic favorite.
And to do that, we have
a brand new product
manager joining us for
the first time on Release
Readiness Live, Rubin
Roy, Associate Product
Manager.
Take it away Rubin.
Gillian, thank
you so much.
I am incredibly
excited to get
to interact with
our Flownatics
for the first time.
I am so grateful
for this opportunity
and to get to learn more
about what each of you
are feeling for our
upcoming release.
I'm specifically
focusing on screen flow,
and I'm really
looking forward
to talking about a
couple of the upcoming
demonstrations and
features that we're
going to provide.
And I'll be giving a demo
of quite a few of them
in a single experience.
So let's get started.
First off, I guess I'll
inform you about what
we're doing with forms.
This is really exciting.
We have reactive
screen components now
generally available.
And from a
layperson's language
that basically means
different components
can now talk to each
other reactively
on a single screen.
Forms are a
fantastic example
of where this comes up.
So you have in a
traditional setup,
or I guess prior to this
release, a setup where
you would need to click
from one set of questions
that you answer to
another to make sure
that the people in
your organization
are completing that
flow in the order that
is sequential.
You don't have to worry
about that anymore.
That process introduces
a lot of friction.
It can involve
additional time,
and it can just generally
be seen as cumbersome.
We've taken that
feedback to heart.
And the way we've
worked to address it
is by allowing for
flows to include
different portions
of the form answering
on the same screen, which
means once you complete
the first part, the
next part of that form
renders immediately.
That also means
that you're still
retaining the same
sequential completion,
but you don't
have to click
between different
screens anymore.
It's all rendered
on one screen.
This allows you to
complete forms faster
and make fewer mistakes
because you're not
switching between
different screens
for the same form.
This also unlocks a
lot of new use cases
for our Flownatics,
for example, building
longer and more
interactive forms
that might address key
use cases on the more
application side.
Now that we've talked a
little bit about forms
though, I want to
talk a little bit
about formulas.
The next area that we've
done a ton of great work
is in reactive formulas.
This is super exciting.
We're moving
away from having
to enter and then click
or do these calculations
manually.
Now you can incorporate
reactive formulas
within a screen
flow, for example,
utilizing a
reactive formula
to dictate how
display text might
change with respect
to a user action.
The way that changes
can be dictated
by a dynamic formula.
Furthermore, these
can now reference
global variables, for
example, custom labels,
custom settings,
what have you.
Notably, we've also
introduced a couple
of new functions, for
example, SUBSTITUTE
and ADDMONTHS.
This is designed,
again, to streamline
a lot of the complexity
that we saw earlier
and remove a lot
of friction that
tends to add time
and lose revenue
for teams that
really, really
depend on this stuff.
But here on the
screen flow team
and the reactivity
team, we
care about all subjects.
So we've talked
about the formulas,
which are for math.
Next let's do some
reading and writing.
Reactive display text
is the next big area
that we've done
a ton of changes
for this upcoming
246 release.
Generally available
now is the ability
to have display text that
now reacts to changes
on the same screen.
So you can see a
classic example
of that on the slide
you're viewing right now.
A couple of considerations
to make sure that this
does work for your org.
First off, make sure
that your API version
is updated to 59 plus.
We're going to
talk a little bit
about what that looks
like in a second.
And just a general note
is reactive references
can occur for a pretty
big litany of data types.
So that's numbers, dates,
date times, and currency
on the same screen.
Those might look
a little bit
different than what
you're seeing on the slide
right now though.
In order to opt
into this, you're
going to want to go to
Setup followed by Process
Automation
settings, and then
proceed to Check Reactive
Display Cases, which
is like a checkbox to
opt in to this beta.
Next, just a quick
tip especially for all
of our amazing
admins out there,
be sure to upgrade
your API version now
so that you can
get access to a lot
of these incredible
features.
All of these
Flownatics features
are going to be available
with a single click
change, and that's to
go to your flows version
property screen
and change your API
version to number 59.
We're also
foreshadowing something
that I'm super excited
to talk about, which
is that screen flows will
now remember for you,
and they're going to
retain user values.
So let's talk a
little bit more
about what that
looks like.
The next big area that
we've done a ton of work
is being able to
recall features
when going backward.
I think we've all had the
incredibly frustrating
experience of having to
maybe incorrectly entered
a password.
And then when I go
back to enter it again,
this time the right
way, my entire password
has been erased.
That's so frustrating
and introduces
a ton of friction,
a ton of time,
and just generally a lot
of frustration for users
no matter what the
software suite is.
It's something we've
gotten a ton of feedback
on and we are committed
to addressing,
and now we have.
We are now able
to retain values
that a user enters when
they navigate backward
to another page.
This is incredibly
important too
because it's not just a
matter of convenience,
this prevents pretty
serious data validation
errors from occurring
where maybe you
originally
entered something
that you wanted
the flow to retain
and subsequently
it's not there,
which could introduce the
probability of an error.
Now if your data is
validated on one screen,
it is retained so that you
can go back to it later,
which is designed not only
to make convenience more
likely for you but
also error less likely
for your organization.
This has a pretty
substantial impact.
We're looking at input
validation occurring
and retained values, which
is what I just mentioned,
along with flows
that resume
after a pause with the
previously entered values
retained within
the screens that
are displayed.
Super exciting
stuff, and again
driven by all of the
incredible administrators
that we're getting to talk
to, super exciting stuff.
Lastly, I just
want to call out
a couple of more
additions that we're
happy to give a little
bit more insight on.
The first is that we
are able to update
reactive components
the first time you
load a screen.
This is pretty
distinct from what
happened before, which
is the requirement
that in order to load
reactive components,
a user would first need
to run the screen-- would
have to basically enter
the screen that was
visited or make a
change to the screen
for the flow or for
the screen to update.
Now you see the
changes the first time
you load it.
There's no incumbent
task on the user
to make that
type of change.
Second is that choice
selections are now
reactive.
We're going to see a
great example of this
in our demo.
But basically that
means that the same type
of reactivity that we
talked about with display
text can basically
function similarly
when it comes to choices.
So choices include things
like radio buttons where
you have or a
pick list where
you have a set of options
that are enumerated
and you have to pick one.
Now those things
can react,
those features can
react based off
of the information that a
user inputted, so, again,
really exciting stuff.
And lastly, I'm
sure that you've
heard a lot
about the values
that Salesforce holds
as an organization.
One of the biggest
ones is trust.
For us at flow, trust
is part and parcel
with accessibility.
In order to make sure
that our flows are
as accessible as
possible, we've
now announced that
screen readers
will be able to announce
reactive changes.
This is incredibly
important for us
to make sure that
our flows don't just
work powerfully but
work for everybody.
Let's take a look at
some more reactivity
resources.
And now I'm going
to go take a look
at our incredible demo.
So what I'm going
to start with
is taking a look
at what the flow
itself looks like
and then going
through what
the old version
and the new version
with lots of reactivity
provides us.
So what we have here
is a screen flow.
And the idea is we're
going to get records.
So we're going to be
getting the records
about what stage
a deal might be in
and the first screen that
the user is going to see
is basically for an
account opportunity.
They're going to want
to select a given price
range or a price
book basically.
Let's x out real quick.
Then after that,
we're going
to get the records
corresponding
to that price book.
And then on the
next screen,
we're going to be able
to calculate the service
package.
But what's going
to be exciting
is that the way that
experience looks like
for users is
drastically different
now than it
ever was before.
Then after that,
we're going
to proceed to a
decision element which
is whether or
not the request
for the account
size that the sales
representative is
hoping to engage with
is approved or not.
So either it
will be submitted
for approval, in which
case, a line item
is created.
And again, a success
screen might be shown.
Once again though the
way that this looks like,
old versus new is going
to be super different.
So I like to go
over this first just
to give a framework for
the type of functionality
we're going to be seeing.
And then we can blow
each other's minds
with an idea of
how different
it is now than
ever before.
So with that
being said, let's
get on to the cool stuff.
So first we're
going to start
with what was
originally there
prior to this release.
So I'm going to
launch my very
creatively named flow
Reactive Discount
Calculator.
And we're going to
start with nothing,
so no reactivity at all.
So we want it boring.
So let's select our
boring flow and so.
Let's see.
We're loading.
Cool.
So we have open
account opportunities.
In this case, I think
I want an elite package
deal.
Maybe I have a
really cool customer.
And I'm going to call
them an MVP, so a really
valuable customer.
From a user perspective
though, this also
puts a couple of
incumbents on me.
If it's a
valuable customer,
I want to move fast.
I want to move
efficiently.
I want to get
the store out
as-- this deal out the
door as soon as possible.
Let's see a couple
of obstacles that
might come in my way.
So first, I got to go
back and forth a lot.
So now I have to
select my discount.
And if they're a
great customer,
maybe I want to turn that
discount pretty high.
And so we have
the discount.
We have what we selected.
So we have an issue there.
So, again, these
types of things
are coming up a lot.
And we want to make sure
that we can address them
as soon as possible.
So maybe I have
to go back again.
I need to
relaunch the flow.
Basically when I
have this none,
I want it boring stuff.
I pick elite package
deal or maybe
big deal for tech synergy.
I go to MVP customer.
I turn the discount
up to the max.
And again we're
not getting
the functionality that we
need or what could happen
is I get to this
screen and it says, no,
you actually
have an error.
That's a really,
really big problem.
And we need to make
sure that doesn't
occur because that's
a ton of friction.
Even right now, I'm
going back and forth
between different
screens, and that's
a pretty big
obstacle when it
comes to getting this
deal out the door really
quickly.
So let's take
a look at how
reactivity in this
flow can streamline
the process a lot.
So we are now going
to turn reactivity up
to the max and make it as
quick as possible for me.
So watch what happens.
So we have the
same screen.
Nothing's different
except now
instead of having
to navigate
from screen to screen,
the next part of my user
experience renders for
me within this screen,
making things a
whole lot easier.
So now I select
this and immediately
the number of
packages that I have
available are enumerated.
So maybe I have premium
service packages,
et cetera, et
cetera, and I
want to calculate
the discount.
And look at that
instead of having
to go between
screens to see
whether this discount
was too high or not,
I'm able to see
within this screen
that it's too high and
adjust it accordingly.
In a real life
situation, this
could involve
basically streamlining
an experience
that would have
me going to my manager
or having my manager see
something that was just
too high originally
and going back and forth.
That's a lot of annoying
iteration for me
as someone who's just
demonstrating this.
But imagine how
many hours of
lost revenue that
means for a team that's
depending on
this for sales?
All that is
streamlined now.
So instead you're able
to adjust this slider
and immediately see if
that discount is viable
or not.
We see that it's viable.
We click Next
and bingo, we've
been successful in
adding the package
to the opportunity
which now we're
going to finish.
All of that
was streamlined
by the incredible power
that we have through
reactivity in
flows and I'm
so excited to hear about
your questions, thoughts,
and insights when it
comes to how this can work
for your organization.
Gillian, back to you.
Wow!
Rubin for your first time
on Release Readiness Live
and as being a
brand new product
manager, that
was phenomenal,
really well done.
Now I bet everyone
is going crazy
because there was a
lot of Flownatics love
for screen flows that I
remember from Dreamforce.
And now I imagine there's
even more in the chat.
Waseem, what's going
on in the chat.
All right.
Flownatics are in a
frenzy over that demo.
I can't even keep up with
all the questions and all
the love that you're
getting for that demo.
Deidre says that
demo was fire.
Armand says, I
appreciate this compare
and contrasting demo.
Daniel, says good job
on the accessibility,
so important to
be accessible.
And Stuart on X,
Stuart, you've
been riding with
us all week.
I appreciate you.
He says, reactive
screen components
being demonstrated on
Salesforce RRL, forms
updating on the same
screen, reactive formulas
to calculate based
on user input.
This stuff deserves
a bunch of applause.
And then there's a GIF
of the rock clapping.
I like that.
And then Michael
Farrington
says, man, these
flow enhancements
are transformative.
Get it?
I like the puns.
If y'all got puns,
share the puns.
Now let's get technical.
Here's a question for you.
How can I learn more
about reactivity?
That's a really, really
great question, Waseem.
In order to do
that, there's
a couple of
resources that we're
going to want to
take a look at.
The first is our
incredible Trailhead
modules, which have been
made by a lot of members
of our team
specifically designed
to inform both new
users and experienced
administrators about a lot
of the new functionality
that's going to be
involved with this.
The other opportunity
is to look
at our administrator and
architect blogs, which
feature a lot of
sources of truth
from members
who have created
these technologies as
far as best practices
for implementing them
in whatever organization
you might be dealing with.
That's always great.
We got lots of good
resources, maybe
some even on my
favorite website
adminsalesforce.com.
Just shameless plug there.
OK.
Rubin, we got a lot
of questions for you.
Got a lot of answers.
Not surprising.
OK.
So the first question
I'm going to ask
is from Talia.
Are reactive components
automatically turned
on in our orgs, or do
we need to do something?
So that's a question
that for the specifics
of your organization,
you're definitely
going to want to
refer to IdeaExchange
or the Administrator
Blogs in order
to get more insight for
what applies to you.
But, like I mentioned
in the presentation,
you are going to want
to opt in to the latest
version of the
API for a couple
of the beta features
that we talked about.
Thanks Talia.
OK.
So speaking on that,
Leonard actually
had a very good
follow-up question.
So what happens to your
existing screen flows
and reactive forms once
you turn on an update
to that API?
That's again a question
that you're probably
going to want
to get answered
through IdeaExchange
just because that
can vary potentially
from org to org.
And you know what?
We've got some live
people, product managers
standing by right here
to help us answer.
So I have an
answer for you
for that as well
because, Rubin,
we're going to take it
a little easy on you.
I think you've been
in your job what
like a month?
Thereabout.
OK.
All right.
So we're going to give
you a little pass.
We have some of our
experts standing
by online giving
us some answers.
So the answer for
this is actually,
so for this very reason
we added reactivity
as a new runtime
API version.
So it's in your control.
If your screen flows
become reactive or not,
your existing
flows continue
to work just as
they did before.
So there you go Leonard.
We got you.
We're just answering
all the questions.
We're tapping into the--
There you go.
--huge team behind all
of this flow innovation.
Now we're going to
come back to you.
And Henry we've
got more questions
coming in for you.
I see them right now.
But we're going to keep
moving because we still
have so much
more to cover.
So for our next
section, we
are going to be talking
about flow orchestration.
And to do that
we are joined
by the one and only
Abhishek Sharma
to cover that.
Take it away Abhi.
Thank you so much Gillian.
I'm really excited to be
here to show all of you
the one very
powerful enhancement
that we're bringing
to flow orchestration
in our Winter release, and
that's custom conditions
for steps and stages.
It's been very
exciting to see
all of the amazing
enhancements
that our teams are
bringing to both screen
flows and
integration, and we
couldn't be more
thrilled at the idea
of the amazing experiences
that our customers are
going to build not
only on their screens
but with the ability
to manipulate
data more flexibly.
With flow orchestration,
our customers
will be able
to build on top
of all of these
features to automate
their entire end
to end processes
and make sure that they're
able to manage everything
from end to end in one
single orchestration that
can be shared with other
members of your team,
reported on, and logged
for each instance
of your orchestration run.
And in our Winter
release, our team
is building on top of
the amazing features
that we've been
hard at work
delivering over
the past few years
to bring you custom
conditions for stages
and steps.
With these custom
conditions,
your orchestrations
are now
going to automatically
respond to the data
changes in your org.
You will be able to set
entry and exit conditions
for your orchestration
stages and steps based
on changes to values
on record variables
within your
Salesforce org.
And the easy configuration
for these custom
conditions is going to be
no different from the way
that you've been
configuring conditions
on the start for
your record trigger
orchestrations and flows.
So it should be a
walk in the park
for our Flownatics
who have been
doing this for a while.
Now we've talked a little
bit about these custom
conditions, let's actually
see them in action.
What we have here is
a sample orchestration
for Electron Motors.
Electron Motors
is a car company
that wants to be able
to manage their end
to end selling process all
the way from a customer
walking into their
store to the few years
after the customer
has purchased and been
delivered their vehicle.
And so what we
have here is
a record triggered
orchestration
that is going to
start any time
a sales rep in
Electron Motors
creates a record of
the object vehicle.
After that, we move into
the test drive stage
where the customer comes
into the store, goes
for a test drive.
We have the sales rep
generate a price quote
for them, go all the way
through the processing
of the payment
itself, whether it's
loan or cash.
The vehicle is then
ordered and delivered
to the customer.
And we've even got a
few post-sale items
like getting feedback
from the customer,
identifying and upselling
any potential add-ons,
and even doing a warranty
check over the two years.
Now one problem that the
admin at Electron Motors
has identified with
this orchestration
is that when the vehicle
delivery stage is kicked
off and the steps
are completed,
the delivery can take
anywhere from two
to four weeks.
So it's being processed
as an asynchronous action.
And what the rep
wants to be able to do
is wait until the
vehicle has actually
been delivered
to the customer
before reaching out
to them for feedback
in the customer
follow-up stage.
This is a perfect
opportunity
for our custom conditions.
And the way that
we can configure
this is by going to the
vehicle delivery stage
clicking Edit element and
changing the condition
to when all the specified
requirements are met,
the stage is
marked completed.
We will now type in the
record for the vehicle
that we want to look
at and make sure
that we're checking
that the status
for this vehicle is
marked as delivered
before exiting the stage.
Once we've set
this condition,
any subsequent
running orchestrations
will make sure not to move
on from vehicle delivery
to customer follow-up
until that vehicle has
been marked as delivered.
And let's actually take
a look at what this would
look like in action.
We've got here a sample
running orchestration.
And as you can see,
it's in progress.
And the current stage
that's in progress
is vehicle delivery.
If we go into the
vehicle delivery stage
and look at the
associated step runs,
we'll see that all of the
steps within the stage
have been completed.
But because we set that
custom exit condition,
the orchestration
stage will not
move on to the next
stage until the vehicle
is marked as delivered.
So let's do that.
Let's go to the
associated vehicle,
click on the
delivery stage
and mark it as the
current status.
Once we've done
that, we can go back
to the orchestration,
click on all the stages,
and as you can see, the
vehicle delivery stage
has now been
marked as complete
and the orchestration has
moved on to the customer
follow-up stage.
With the power of custom
conditions for steps
and stages, your
orchestrations will now
be even more in sync with
the data within your org,
and we're super
excited to see
how this helps all of our
customers going forward.
That's all I've got
for now, Gillian.
Happy to open it up
to some questions.
Well, Abhi don't you
worry there are going
to be a lot of questions.
Great job.
Thank you for sharing
that demo with us.
Waseem, speaking of
questions, come on.
Give us the questions.
I know the Flownatics are
going wild in the chat.
What do you have?
You are right.
The Flownatics are
going wild in the chat.
I'm sweating
just keeping up
with all the innovation
and all the questions
that we have coming
in after that demo.
All right.
Abhi, I got a
question for you.
What's the difference
between flow and flow
orchestration?
It's an excellent
question, Waseem.
And it's something
that you're not
the first person
to ask me this.
So the way that we like
to describe the difference
between flow and flow
orchestration really
comes down to the use
case for which you're
automating.
And you saw in the
sample orchestration
that we've got a lot
of different stages.
And within those
stages, we've
got a lot of
different steps.
And each of those
steps would correspond
to a very
specific task, one
of them being
getting the sales
person to generate a price
quote for the customer.
Another one being having
the sales person reach
out to the customer
to get feedback
after the vehicle
has been delivered.
And we think that those
smaller tasks correspond
very well to flows.
And we've got so many
different types of flows
that you can use
really to automate
any task at that level.
But when it comes to
then chaining those tasks
together to create an
entire automated end
to end business
process, that's
where orchestration
really comes in handy.
And we've got a lot of
specific orchestration
features that are
really useful for this,
things like assigning
specific steps to users.
And we take care of all
of the task management
related to that.
We've got things
like reporting
on the orchestration.
So when your
orchestrations
are running, you
can get a lot
of detailed information
on where things are at,
who's doing what.
And we've just got a
suite of other features
like managing the order of
execution for your flows,
whether you want to
run them in parallel
or run them sequentially
or now with custom
conditions, run them
when a data change is
made in your org.
We're continuing to add
more and more features
to make sure that entire
end to end business
process can be automated
using Orchestrator.
And if that's a bit
of a mouthful, too
much to remember we've
got a saying that our very
own Diana Jaffe
has coined,
which is, if you've
got a process that
can be completed in
the same amount of time
as it takes to make a cup
of coffee, use a flow.
If it's any
longer than that,
use an orchestration.
Oh the one and only,
the sage advice
of Diana Jaffe,
who I think we're
going to hear
from very soon.
That's great.
Thank you for
that explanation.
I think it really
helps when we're
creating these processes
and figuring out
which tool to use
for which solution,
it's really
helpful to have
that strategy in mind.
So thank you for
sharing that.
More questions for
you because you're now
in the hottest seat
of this situation.
So do does flow
orchestration provide
logs of every execution?
Another great question.
And yes, we absolutely do.
So the way you can
access these logs is
once your
orchestration starts
to run after
being activated,
you just need to search
for orchestration runs
in the app launcher
in Salesforce.
And what you'll
be taken to
is a list view of
every single instance
of your
orchestrations that
has been executed
in your org.
You can click
on each of them
to get more
detailed information
on the different
stages that ran
as well as the
steps which we
saw a little bit
of in the demo.
But there's a
third section
in that list view that is
called orchestration run
logs and that gives you
a really detailed step
by step breakdown
of every single step
whether it was a flow or
a MuleSoft action that
took place in your
orchestration.
And you can see
advanced details
like how long each
of those steps took,
when it started, who
it was assigned to
as well as who
completed it.
Those two can be
different in cases
where you assign
something to a group
and a member of that
group completes the step.
So we absolutely provide
very detailed logs
of every instance
of orchestration
that was run in
your Salesforce org.
I think that's great
because the whole reason
we create orchestrations
and flows is
to drive more efficiency
in our organizations,
make it easier and
faster for people
to get their jobs done.
And those audits are going
to be-- those records
are going to be so
critical because you can
really show the impact
of the orchestrations
that you built.
100%.
So I love that.
OK.
We're going to have way
more questions for you,
but we have one more
section to get through.
You teased it.
It's one and
only Diana Jaffe,
star of flow RRL,
also senior director
of product management.
But really she's
flow RRL star.
And she's going
to highlight
even more features
coming in Winter '24
because there
are so much more.
Diana, let it flow.
Thank you Gillian.
I'm so excited to be
in studio for RRL.
And I am going to take
it home with us today.
So I'm going to cover
triggered automation
as well as just a
smattering of new things
coming in flow,
or as I like
to call it Flow-Potpourri
or Flow-Pourri
because we can't have an
RRL without a flow pun.
So let's take a look.
The first feature
is the one
that is nearest and
dearest to my heart.
We now support custom
error messages in record
triggered flows.
This means that you
can intentionally
flag an error
for your users
and block them from
making a specific record
change similar to
validation rules
and to Apex add error.
Now I want to
talk a little bit
about the Community
with this one.
This was filed on
the IdeaExchange
about 18 months ago.
And it had almost
19,000 points
by the time we closed it.
So this really came
from all of you.
We heard you.
We're shipping
it, and we're
super excited to see
what you can do with it.
But what this
means, if you're not
familiar with that
IdeaExchange item,
is that errors that used
to look like this, this
is the exact
one, I took this
from that IdeaExchange,
can now look something
like this instead.
And you can put it
on either the field
or on the overall page,
super, super exciting.
Next up we're going bigger
with triggers than just
record triggered flows.
If you're a Data
Cloud customer,
in this release,
we now are
going to support Data
Cloud triggered flows.
And these are a lot like
the record-triggered
flows that you might
already be familiar with.
It's just that it's
looking for changes
to your data in Data
Cloud rather than
in your traditional
CRM data.
We also support
basically the equivalent
of a get records for
getting Data Cloud
data in any flow type.
So really you're
just starting
to see us merge together
Data Cloud using flow
in a really
seamless way that's
just like you would use
it if you were using CRM
data.
So I think that's
really nice,
and you're going
to see us continue
to merge these
going forward,
which really makes
flow the glue that
can connect all
your different data
systems together.
We're also always focusing
on these little things
on usability, on
hearing from you what
you find easy or
difficult to configure
in flow today.
So one of the other new
things we have is we
have new Wait elements.
So you might be familiar
with our traditional Wait
element, and that
didn't go anywhere.
It's just now called
Wait for Conditions.
But we also took some of
the most commonly used
ways that you
might pause it
flow like waiting
for a specific date
or waiting for a
specific length of time,
and we made custom
flow elements
that just configured
that to make
it a little bit easier
and a little bit more
transparent.
So again, we're
always thinking
both about the
usability of flow
as well as all this power
and new functionality
that you've seen today.
And on that note
another big change
that you're going
to see start coming
in this release
but we're not done
is adding our
elements into panels.
So you'll start
to see some
of those element
editors right aligned
on the screen.
But what this
also means is
that you're going to be
able to navigate around
your flow while also
having the editor open,
so you maintain
that context.
This also allows for
continuous editing
and the ability to
close and open panels
when you have
validation errors.
So maybe you're just
sketching out a flow
and you're like,
I know I want
to put a create
records element here,
but I don't want to fill
it all out right now.
I don't know
my fields yet.
You can create
that element
and not finish
it and still
have it save
on your screen.
So this is a really
exciting way,
and this is where
we're moving to.
So in the Winter
release, there
is going to be a little
bit of back and forth
because some elements
have moved to panels
and some haven't yet, but
stay tuned and get used
to it because I
think it's going
to be really powerful
once you get that muscle
memory going.
So let's take a look at
what that looks like.
So here I have a
triggered flow,
and this is one that one
of our very favorite MVP
admins told me about
that he's going
to use custom error for.
So we're triggering when
an opportunity product
gets deleted.
And we're going to check
to see if the parent
opportunities stage is
already closed as one.
And we want to
prevent them
from deleting that product
if the opportunity has
already been one because
we've already maybe sent
it off using our
new transform
and Callout like
Henry showed.
So if I go here,
you'll see,
and I pull up our new
custom error element,
you'll see that
it's now in a panel.
And I'm going to go
ahead and configure this.
And if I put this in here,
I can also then go in,
and I can use
our merge fields.
So I can go in and find
that parent opportunity,
find the name, and
put that in there
so I can put a lot
of detail and context
into my message.
But remember what
I said about panels
and that
continuous saving.
So one of the
things you're
going to want to
pay attention to
is this undo button.
Now in the past if
I change my mind,
I don't want this
error message,
I would hit Cancel.
But I don't have
that anymore.
I just have the X button
to close the window.
Instead, however, I
have this undo button,
which you'll see as
it undos and redos.
It changes just those
individual changes.
So we made the undo
a lot more specific,
so you can go through and
undo individual things,
and then you'll see that
validation happening
on screen, but
you could still
say close this
out and keep
going with your flow.
So that's definitely
going to be something new
for some of
our Flownatics,
but I think it's going
to be really powerful.
So definitely take it out.
Get a little used to it.
Get comfortable with
that undo button,
and let us know
what else you want
to see with panels.
And with that, I'm
going to throw it
back to Gillian
for what I'm
sure is a lot
of questions.
Thank you so much,
Diana, amazing.
Yeah, there are a
ton of questions.
I've got like multiple
scrolling things
happening over here.
But to get to some
of your questions,
we're going to go ahead
and start with checking
in with Waseem.
Waseem, what's going
on in the chat?
We got a lot going
on in the chat.
I'm scrolling and
scrolling and scrolling
through tons of
questions and also
a lot of love
for that demo.
We have Danica who
loves these changes.
Sagar says, continuous
editing is a lifesaver.
Myra also loves the
continuous editing
feature.
And Jean is
saying that this
is a huge step forward on
error handling feature.
And thank you for
delivering this
so quickly.
And Joseph is saying
that this is a really
nice instead of just
having a generic editor.
And Ty, my guy, says,
who says flow can't
get any more awesome.
Now let's get technical
and into the questions.
Here's a question for you.
Any updates on
AI for flow?
That is a great question
because I think if anyone
tuned into
Dreamforce, they
heard the letters
AI together.
Are you sure?
Are you sure?
Maybe once or twice.
We do have some
really exciting stuff
coming for FlowGPT,
Einstein, FlowGPT.
I'm not sure what the
latest naming is but--
We like to keep
that spicy.
You probably saw some
demos in Dreamforce,
and those are available
in pilot in this release.
But we've had so
much excitement
we were going
to come on RRL
and say sign up
for the pilot.
But I think we have
customers backed up
waiting in legal to get
approved for the pilot.
So at this point, if
you aren't in the pilot
yet, sit tight and come
to the next release
where there's definitely
going to be more
but we are absolutely
working on some really
exciting things like
writing in a description,
that error message thing
flow that I just showed.
What if you
could just type
that in as a sentence
and FlowGPT would
make that for you?
So that is in the works.
We're super excited.
I'm personally very
excited about that too.
I know we showed it
in the admin keynote.
Absolutely.
Admins love flow.
But, yeah, it's
going to be really,
really game changing.
But there's also all
this amazing other stuff.
Speaking of other things,
Diana, what is this?
So we've been
doing RRL from home
for a couple of years
now, and I've been on them
more than once.
And a little birdie
told me at Dreamforce
that some of you
out there are
really interested
in the background,
and what's going on.
And I'm told,
in particular,
I think there's two
admins out there named
Renata and Bethany,
who just really loved
my table lamp.
So I brought
it just in case
you were going
to miss it now
that we're back
in the studio,
and we don't have all
the touches of home.
So the lamp is here
for the two of you
as well as Steve.
Bringing that realness
to the studio--
The real comforts of home.
I'm just going to put
that right there Diana--
Hangout with us.
Yes.
All right.
We have a lot of questions
every, so get ready,
sit tight.
Here we go.
OK.
We are going to start--
Diana, we're going to
ask you one more question
before we move on to some
of our other folks here.
All right.
Are there plans to bring
custom error messages
to screen flows?
That's from Patrick.
It's a great question.
I think that's
one of the things.
It would be a
different set of work
because what we're doing
is tied into that record
change.
It's the same thing Apex
and validation rules.
But I know our folks
on screen flows
would really like
to have it as well.
So we've already
been talking
about how we
could potentially
use it or adapt it.
But I think they also
have a ton going on
with reactivity right now.
So if this is something
you want to see,
that's the kind
of thing that
would be good to have
IdeaExchange votes
on because we are just
brimming with great ideas
on things we want to
do in screen flows.
So I know it's
been something
we've talked
about, but I think
we have a lot of things.
OK.
Patrick posted on
IdeaExchange vote
on it have a campaign
because literally I
mean I don't know if you
paid attention to all
of your presentations.
But that is how
features get made.
Yes.
So good, good callout.
Henry, we're going
to come back to you.
Question is from Daniel.
He asks do the
transform action store
intermediate data in
temporary or permanent
tables.
Will this data count
against record limits
or database limits.
So not yet.
Stepping back,
if you're not
using the output
for something else,
then it is storing
intermediate.
So any Salesforce
even action and stuff
have automatic
output, those
are all intermediate
variables.
Now we have roadmaps
in the future
to be able to use
intermediate and stack
them together
in the future
as I showed in the
slides and that's
going to get even
more powerful,
so stay tuned for that.
Oh, I like it,
little teaser.
Also a reminder of our
forward looking statement
to only make purchasing
decisions based
on currently
available features
and functionality.
We are going to
go, move on down.
Rubin, I have a
question for you.
All right.
With reactive
forms and formulas,
does this work for
all field types
pick-list, text boxes,
number fields, et cetera.
So there will be
some variants away
from what I had shown
in that slide based off
of the type that you have.
So I think I
had mentioned,
for example
currencies will
have a different type
of functionality.
If you want a more
extensive enumeration
of exactly what each type
will have as far as what
it looks like for
reactive formulas, that's
something you can
post on IdeaExchange
or take a look
at the more blog
the architecture
blog to keep
track of a more
comprehensive listing
of that.
I love it.
Good answer.
All right.
Let's see.
We are going to go here.
Abhi, I've got a
question for you.
Just going right
on down the line.
Look at that, how
this is working out.
This is from Kirsten.
She asks, so
custom conditions
replaces the evolution
flows, correct?
That's a great
question, Kristen.
And I believe the
evaluation flows is what
Kirsten is referring to.
And our intention is that
these custom conditions
can be used for a lot
of the use cases, which
customers might
previously have been using
evaluation flows for.
There may be a few
one-off cases where
your condition
is so complicated
that a simple sort
of Boolean statement
might not make the cut,
so you have to use a flow
and do something
more fancy.
If that's the
case, you may
need to continue using
evaluation flows.
But the custom conditions
are great because they're
simple.
You edit them in the
orchestration editor,
don't need to create
a new flow for them.
They can do simple
record variable checks,
and they're going to
continuously listen
to the record in question.
So as soon as that
change is made,
the updates come back
to your orchestration.
OK.
Thank you.
Thank you for the answer.
Thank you for
correcting me.
I even asked the
question wrong.
You understood what
Kristen was saying.
OK.
Diana-- so this is one
that was actually-- it's
a pretty detailed one.
But I think
it's a good one.
So this is from Andrew.
He asks, will
we finally be
able to make REST Callouts
for both new records
and changed records in a
single record triggered
flow?
Currently, the
entry criteria
don't allow both
because there
is a mandatory
asynchronous
path for Callouts
so we have
to make two flows that
do the same thing.
So I might get this
wrong depending
on how I'm understanding
the question.
So you can set up a flow
that's create or update
and then has one
asynchronous path that
could do that Callout.
But that does require
entry conditions
because we
limit the number
of asynchronous things
that you can do.
So I'm wondering if he's
talking about that, which
is something we're
looking at if we could get
rid of that restriction
eventually because we
know more and more people
are using asynchronicity
for all of these
things that came over
from scheduled paths
where we didn't want you
queuing up 100 schedules
anytime anything changed.
So if that's the
answer, I would
say that's something we're
looking at in the future.
Instead, if he's asking
for some other things
or for us to not have
the after save flow
next to the async, I
think that's probably
a little further out,
but we can absolutely
have that conversation
in the Community
later on if I
misunderstood
the question.
OK.
So if we screwed
that question up,
please make sure you ask
it in the Trailblazer
Community.
And again any of
the questions,
we're not-- there's
no way we're
going to be able to
answer all of them.
We're going to
do our best.
But also if
you're watching
this, your question in
the Trailblazer Community
because that is where
we will make sure
you get an expert provided
answer to your question.
OK.
I'm going to ask one
more question here
and then we're
going to check back
in with Waseem.
Henry, we're
coming back to you.
All right.
This is a question for--
oh this is a
question from Stuart.
Hi, Stuart.
So glad you're
tuning in today.
OK.
For transform
formulas, is there
a way to easily use
transforms in other flows
so that you are
using standard labels
and calculations
throughout your different
integrations?
Other flows?
I'm not sure exactly what
it means by other flows,
so like sub
flows or like--
so we support screen
flow, auto-launch flow,
and record trigger flows.
So those are the three
types that we support.
So if that's what
Stuart's is asking,
that's the answer.
But if not, let me
know and I'll answer it
on the Trailblazer.
I know Stuart's
a Flownatics,
so he might be really
getting into a corner
there.
But, yes, Stuart
keep asking it
on the Trailblazer
Community.
And if we didn't answer
it, ask Henry again.
OK.
We are now going to
check back in with Waseem
because I know
that there's
a lot of Flownatics
love, and we
want to feel the love
over here in the studio,
on the stage.
So Waseem, what's
going on in the chat?
All right.
The chat is lit with
not just tech questions
but some fashion flow
questions as well.
Gillian, people are
wondering, where
did you get that jacket.
And I'm wondering
the same thing too.
I might need to borrow it.
You're getting
a lot of love
on the fashion front.
Steve says Gillian
rocking the ensemble.
Chad says, OK, new
sparkly jacket.
We're just getting a
lot of love for you.
This isn't just tech,
it's also fashion.
But let's see.
The features are also
causing a lot of buzz.
Squire saying the
HTTP flow roadmap
is game changing, and
he's looking forward
to doing all the
things in all caps.
Mansukh says,
loved the beta
for the reactive
screen so far.
This is super exciting.
And Mark on X
or Twitter says,
Salesforce flow
Orchestrator
will have the ability
to set custom conditions
across various parts
of the orchestration.
This could actually
be a great step
for the Orchestrator.
And he's got a little
the Office GIF with Pam.
And I love it.
Keep the GIFs
coming y'all.
I want to see
them, and the puns.
Now let's get back
to being technical.
Here's a question
from Emilly Salesforce
Plus in the Q&A tab.
Is allowing
additional objects
to kick off record change
flows in the roadmap,
for example, agent, work?
That's to you
Diana I believe.
That would be me.
We don't have any
particular plans.
So generally what
we do in flow
is work with the
individual teams
that own say that agent
record or that object.
So usually, it would
require collaboration
with that team and
making sure it's
on their roadmap as well
because they can light it
up.
But they need to
be able to support
all of the things
that go behind that.
So generally,
that's not something
we keep on our roadmap.
Well, we are a
very big platform
with a lot of different
teams and features
and capabilities.
So that is one
where, I think,
if something comes up
through us enough times,
we'll go to that team and
talk with them about it.
But often those
end up being a lot
of small little pieces.
And usually, they have
a better connection
with those users and
customers to start with.
But if there's one that
you think we're really
all missing and that we
could all get together
cross platform to do, then
definitely let me know,
and we can reach out
to the right team
and coordinate that.
All right.
Let Diana know
Trailblazer Community.
Give her just lay out all
of your flow problems.
Everything just
bring them on.
Veraflo Therapy hour.
Well, that is a
different show.
But I'm sure it would
be a popular one.
We're going to go back to
some of these questions.
Also before we move
on, the jacket,
I had to bust out,
the sparkly fun
because this is
the most fun.
Doing flow RRL
is literally
one of my favorite things.
And there is
so many things
happening in the
future of flow.
The future is bright.
It's sparkly.
Flownatics
deserve some love,
so I have some
fun with it.
And if you want
information
on where I got it,
ask on the Trailblazer
Community.
I'm kidding.
It's a secret I
can't tell you.
We are going to go back
to some questions here.
Abhi, I got a
question for you,
and Diana you could
back him up on this.
When will there
be a search field
on the list of flows?
Another great question.
And the answer is
very, very soon.
This is actually
something that's
on our roadmap for the
not the release that's
out right now but
the release after.
And we're very excited.
We've already heard a
lot of initial excitement
over this.
And all I can say is
keep your fingers,
not your fingers crossed
but just keep posted
because it's coming
out in our spring
release of next year.
Forward looking statement.
[INTERPOSING VOICES]
Statement
Only some flow
types to start,
so there's going to be--
there's going to be a
rollout process I think.
That's happening.
We know, and
it's happening
we're very excited.
Well, it was
bolded in here.
So I think
[INTERPOSING VOICES]
They really
wanted me to ask.
We're all very
excited, obviously
working very hard
on it, so we're all
very excited.
Excellent.
Excellent.
We have a question
here for Henry.
Henry, the question is,
this is from, oh, OK,
here we go.
This is from Craig,
is the data shape
the JSON payload
for the HTTP Callout
functionality in flow?
Sorry.
Repeat that.
The HTTP shape?
Is the data
shape, the JSON
payload for HTTP Callout
functionality in flow?
Oh, OK.
Yeah, so that's
directly in flow.
So when you're creating
the HTTP Callout,
you can basically paste
in the JSON shape,
and then it will
create a data shape
from that JSON payload.
So that's the
data transforming
into a data type.
So, yeah, you can do
that directly in flow.
And if you need
to edit, you
can go into the
external service
and edit over there.
OK.
Great.
Thank you for answering
that question.
We've got some more.
Surprise, surprise.
Henry, I'm actually
going to come right back
to you.
You were first
so people had
a lot of time
to ask questions
about your section.
This is from
Minhaj, and you
might have already
answered this,
but I just want
to elucidate it.
So is that transform
element just
for HTTP Callouts?
No.
The transform you
can think of it
as the latest update
of assignment.
You can do anything
you want with it.
It can be SObject
to SObject,
Apex type to Apex type,
SObject to Apex type.
You can just use it
for anything else.
So it's most
powerful when you're
working with external data
because the external data
most likely have
hierarchical data
shape with it and that's
what is built for.
Excellent.
Thank you for
answering the question.
There's a lot of
questions here.
I'm going to ask one
more, and then we're
going to check
in with Waseem.
So let's go.
Diana, you're going to
be on the hot seat a lot.
This is normal for you.
I got it.
This is just the way--
this is what it means
to be Diana Jaffe.
There we go.
Diana, the question
is, this is from Bow,
when will
record-triggered flows
be able to trigger flows
with pause elements?
Process Builder was
able to do this.
So we are not planning to
support the pause element
in record-triggered flows.
What we found
is most people
were using that to
basically launch
an asynchronous path.
And so we're moving more
to doing asynchronous.
We also have scheduled
paths for things
that we're going
out further.
So right now, the plan
is to not include pause
or wait going
forward but instead
to focus on those
things being separate.
And that has to do with
data storage and a lot
of other things.
I do think there's some
use cases where people
are missing things
or want to store
some context in that
asynchronous path
and pass that along.
So we are looking at if
we can support things
like ISCHANGED in prior
record in asynchronous,
which I think
will complete
a lot of the bulk of use
cases that are involved.
I think there's still
a few out there.
There's an IdeaExchange
item already on this
that I've had some
conversations with people
to try to make sure we're
getting everybody's use
cases.
But overall,
that's where we're
going architecturally.
I appreciate that.
Well, Bow, if you
have more feedback
reach out to Diana.
We are now going
to go check
back in with Waseem.
Waseem, do you
have any more fun
gifts to share with us?
I'm sure you've got
more questions too,
but go ahead and
tell us what's
going on in the chat.
There's a lot of
love in the chat
and also on social media.
We have a lot
of people asking
questions about
your fabulous
#Flownaticsshirts.
And I'm going to need
to get my hands on those
too.
Let's see Christy
Campbell, Christy Force
on Twitter is
saying, she's
got a lot of excitement
about that lamp.
Not only did Diana
round things out
with some #floppery,
new hashtag alert,
but she even brought
out her lamp from home.
Now that we're
back in the studio.
Loving it and
loving seeing
all these other rockstar
PMs That I got to follow.
Let's see.
We also have a lot
of love for all
these new enhancements.
Bow says, oh my,
field search on flow
is going to
help me so much.
And Jessica
says, ooh hooray!
Search feature, yes!
Hey, I'm liking
the energy.
And I want to see more
puns, more energy,
and questions from
all y'all on social
and in the Q&A.
All right.
Now let's get back
to getting technical.
I'm seeing some questions
about emails and error
messages.
Bethany is asking, when
a custom error message
is triggered for
a flow will also
send a flow error email
or it will adjust display
on the screen?
Diana, take that one.
It will not send a
flow error email.
So generally, error
emails are when something
goes wrong in the flow.
And even though
this is an error,
it's an intentional error.
So the point is
that the error
was supposed to happen.
So we don't want to mix
that in with the error
emails that are
something went wrong.
On behalf of
admins, everyone
are going to
thank you for that
because the last thing
we need is more emails.
More error emails
is not what we often
get asked for.
That is very helpful.
Rubin, we're going to
come back to you to talk--
Let's do it.
--about reactivity.
Let's do it.
Interested to see how you
react to this question.
All right.
It's the flow
RRL, puns galore.
What are some of
the biggest gotchas
or considerations when
it comes to reactivity?
So one of the biggest
things that you're going
to want to keep an eye
out is for a comprehensive
list of which components
can and cannot be
reactive.
That's an upcoming
list that we're
going to be providing
through some
of the avenues that I
talked about earlier.
And so that's
definitely going
to affect the
way that a lot
of our incredible
administrators
use our cool new feature.
I love that.
All right.
Good reaction.
Henry, we're
coming back to you.
This is a fun question
and again forward looking
statement.
I'm just reminding
everyone.
When is transform
going to go GA?
Yeah, so we're
planning on it.
It's definitely within
the next two releases,
but no promises,
of course.
We're working on it.
All right.
Thank you Karine
for putting him
on the spot for that.
That's good forward
looking statement
to be remembered
at all times
when we talk about future
product enhancements.
We are going to
now, let's see,
there's so many
questions I have
to do all this scrolling.
All right.
Abhi, we're coming to you.
Can a flow Orchestration
help integrate
external systems?
We talked about
HTTP Callouts
but orchestrations are
a little different.
Can you talk about that.
Absolutely.
Orchestrations
support integration
with external systems
in a couple of ways.
The first, and this has
been the original way
for us, is if you have an
auto-launch flow, which
is making a Callout
to an external system,
you're absolutely
able to put that
in your orchestration.
And we have a
specific checkbox
that we like our admins
to check whenever
that auto-launch flow has
that external Callout.
And this just
makes sure that
from a backend perspective
for orchestration,
we're properly making
sure it's compatible
when it's running with
that external Callout.
The other way and
the more recent way
that we're supporting
this integration
with external systems
is through our MuleSoft
steps.
So historically,
we've had steps
where you can
add screen flows
and auto-launch flows
into your orchestrations.
But now you can add
MuleSoft actions.
So side by side with
your screen flow
is your auto-launch
flows which
are doing the human
based and the background
processes.
You now can also add in
your MuleSoft actions
to do those, do
even more Callouts
to external
systems directly
within your orchestration.
And I think that's
again really thinking
about which tools to use
to solve, which problems.
I think is interesting
because we do.
MuleSoft can do
a lot as well.
We've got HTTP Callouts.
We've got Data
Cloud integrations.
There's all
kinds of avenues
to work with
external system data.
So I think it's
really important
to think about when to
use the right feature.
That's great.
Exactly.
So we've got
more questions,
more questions.
The next question here
looks like we've got--
here we go.
I'm scrolling.
I'm scrolling.
Keep asking the
questions everybody.
And by the way,
if we don't
get to your question,
we will make
sure it gets answered.
Make sure you ask it in
the Trailblazer Community
because this live chat in
Salesforce Plus is great.
But if you want to make
sure your question gets
answered after
this live session,
you have to ask it in the
Trailblazer Community.
That's also we've
got product managers
on the backend here
secretly feeding
me answers to some
of these questions,
and they are hanging
out in those communities
as well.
So make sure that you
ask your question there.
So we have a
question here,
speaking of product
managers working
in the back end providing
me answers, so there's
a question from Dave.
Dave asks, are
reactive screens
intended to replace
conditional visibility
for screen components?
And I'm not going to put
any of you on the spot
because we have an
amazing PM on the backend.
It's probably either
Sam or Adam who
have provided an answer.
And the answer is yes.
Reactivity works both
in Lightning pages
for and Experience
Cloud sites.
Oops, I'm reading
the wrong answer.
This is what happens
when you look up.
[INAUDIBLE] question.
It is a good question.
That's because they
already marked it
as I answered it.
I believe-- yes,
there we go.
So the answer to
your question,
Dave, is that no
they're intended
to be used together.
You can think of it as
conditional visibility
controls whether
the component is
visible to the
user, so you
can build in
progressive disclosure.
And reactivity enables
conditional values.
So there you go, some
detailed answers.
It's like when you see
it and then what you see.
There you go.
Yes.
Just like when
I see the right
question and answer--
Question--
--in front of me.
And what the answer is.
Yeah.
Yeah, that's good.
So actually let's ask
one more question then
we're going to check in
with Waseem again here.
So this is a question--
try not to ask myself
a question here.
This is a question
from Ralph.
Diana, I think
this is for you.
Will these other
wait scenarios
require the user that
made the update, that
created them to still be
active at the time they
are set to complete?
I don't think so.
No.
I know there were
some issues with that
in Process Builder,
but we have--
I do believe you have to
have the default workflow
user set.
So sometimes if you
don't have that default
workflow user or
process automation
user set to fall
back to but make sure
you have that configured.
And it's possible
I'm wrong.
And one of those PMs on
the backend will send me
a strongly worded
Slack message,
but I think it won't.
I like that
forward-looking statement
just for that statement.
That statement.
Henry, do you think?
I don't know.
We're live so we're doing
the best we can here.
Since I already read
the answer to this,
I'm going to officially
ask the question
that Nancy asked.
And this is a
question that,
will react to screen flows
work on Experience Cloud
Community sites?
I have a professionally
provided answer,
but if you would
like to go ahead
because it sounded
like you were like,
that's a good question.
The answer is yes.
They work with Lightning
and with Experience
Cloud.
That's an easy one.
There you go.
We like those questions.
There you go.
Good questions.
All right.
Waseem, I want to
check back in with you
to see what is going
on in the chat.
All right.
The chat's popping
off with questions
and social media is too.
I'm on X. I'm lurking all
your accounts right now,
and I'm seeing
some fun stuff.
Diana, good news your
lamp has become a meme.
Thank you to Steve Moe
for creating an "I heart
lamp" meme.
It's really become
a star on the show.
We also have Squire
who's dropping
a GIF of the Family Guy,
dog doing a jaw drop.
He says flow transform
does all those things.
Yeah, same here.
And then Sarah is excited
about less error message.
She's saying, Yay!
Less error messages.
Awesome admins
everywhere are rejoicing.
Now let's see we have
more questions coming in.
This one is coming from
Kothy on Salesforce Plus.
Can we embed reactive
flows in LWCs?
Well, that's a
good question.
Diana.
I'm pretty sure you use
a lightning or the flow
lightning component,
but you probably
should ask that on
the Community and Adam
will answer that for you.
We'll confirm,
but I think--
I've actually got a
professionally provided
answer here from
our remote PM.
Yes, you definitely can.
Great.
I don't know when
that happens.
Yeah, it's like magic.
I wish I had this
power all the time
where people just provide
me answers to everything.
OK.
We're going to
continue on.
Rubin, I'm actually going
to come to you here.
When will long text
area be reactive?
So definitely
forward-looking statement
obviously.
Definitely keep an eye out
for that in the upcoming
releases.
But as of right
now, we've mostly
been focusing
on display text
like we talked about
with the intention
forward-looking of
incorporating that along
with long text in
a future release.
Awesome.
Thank you.
Forward-looking
statement, all the things.
Should just wear a
stamp forward-looking
statement.
This is a question
for you Henry.
This is from Ralph
from Salesforce Plus.
Can you connect to
different data types
if you transform the value
to its destination data
type?
To transform value data,
like two input sources
into one?
If that's a question, then
that is on the roadmap,
and we're working on it.
It actually works
in the backend.
It just doesn't support
it in the front end.
So next release we're
doing that right now.
OK.
Good to know.
I'm coming right
back to you
because this is
a follow-up-ish.
We're like an ish.
Can you call
out to any ERP?
I couldn't tell
you exactly any.
So the Callout is
actually backend is
the external services.
So whatever it
supports, then it will--
you can call it.
But I'm sure there are
other prototypes that
are not supported.
I just don't know
what those are.
OK.
Great.
Well, hey, I
appreciate it.
And also I'm sure
we'll have kinds
of documentation
and people will
be sharing all of that.
Goodness there.
We've got more questions,
more and more questions.
Diana, I'm coming
back to you.
Surprised.
This is a
question from Ty.
We're going back to talk
about pause elements.
Do these additional
wait elements
mean that the pause
element will no longer
be available?
No.
So that is just now called
wait until conditions,
but it's the exact
same pause element.
We just renamed it
to make sure there
wasn't as much confusion
with the new ones.
So it's still all the
stuff you know and love.
We're just adding to the
wait, pause universe.
We like using lots
of different terms
for the same things
here at Salesforce.
So I appreciate
the clarity there.
Just a little modifiers
on everything.
All right.
We've got,
let's see, Abhi,
I feel like you're
getting off light here.
Let's make sure you
get a question here.
Let's see.
You're not getting
called out specifically
right now, but
we will-- if you
get questions for Abhi,
ask them in the chat.
I'm going to make me
spread the love here.
This is a question.
We're going to go
back to you Henry.
And this is actually
a really interesting
question.
I think it's actually
a strategy question
probably for the crew.
Why would any admin
run an API version
that is not up to date?
Oh right.
Yeah.
So there's a
couple reasons
for that really is because
you don't want to--
if you use the
latest one every time
we change new release, you
have to retest everything
again.
So sometimes you
want to make sure,
hey, I'm staying
with this API
because I know
everything works,
and I don't want to retest
everything all the time.
So that's why you would
use the previous one.
And sometimes we do have
changes on the latest
one that will break
certain aspects
of the old one,
so you have
to definitely test those.
You got to watch
out for those.
I know there's some
admins out there who
go in every
release and upgrade
every version of flow,
and we love that.
But we also
know that that's
not realistic for every
admin on every flow
all the time.
Our release
notes also always
specify every
change that's
made specific to
that new version.
So you can use that
to guide your testing.
But I think, to
Rubin's point,
this release of
screen flows,
it might be worth it.
If you're not doing
that on the regular
even just to get that
backwards and forwards--
Exactly.
--thing even and then to
go ahead with reactivity
as well.
So we like to
call that out when
it's extra special.
When it's so awesome.
If you want to use
the shiny new stuff--
And when it's
extra sparkly,
you got it you got to
upgrade your version.
I love that.
Should I just
be, what is it?
API 52.
Is that what we're--
59.
59.
Excuse me.
Yeah.
59, the jacket.
It's obviously a
reactive jacket.
One more question
here that apparently I
am going to answer, and
then we will check back
in with Waseem.
So this is a question from
Chris on Salesforce Plus.
If you expose a
flow to the web,
can you use a reCAPTCHA?
And Chris, the expert
answer I've been provided
is that yes, you'll need
a custom component either
from AppExchange or
you built it yourself
for the reCAPTCHA.
So it's possible, but
you've got to build it.
I am going to throw
it back to Waseem now.
Waseem, we're
coming back to you.
I still see more questions
and everything coming in.
Let us know what is
going on in the chat.
All right.
We got questions.
We got love.
We also have some more
GIFs on social media.
Stuart, my guy, he
says watching the flow
#SalesforceRRL
is like watching
an advanced class from
the honors program
in automation.
These speakers
have been amazing.
And now we love
Diana's demo.
My brain's exploding.
And he's got a
Gordon Ramsay GIF.
I like it.
And Mark says, reactive
screen flows are awesome.
Really looking
forward to some
of these future additions
such as reactive display
text.
Now, let's get technical.
I got a question for you.
This one's coming
from Chase.
This is, is the
ability to categorize
flows in folders
anywhere on the roadmap
rather than just a
single massive list?
It sounds like it
might be yours, Abhi.
You want to take it?
Yeah, it's another
great question.
And like my
previous answer,
I think we have to start
with the safe harbor
statement.
Don't make any
purchasing decisions
based on things that
aren't already available.
And this is
another feature
that is on our roadmap.
It's on our very
immediate roadmap,
so it may not be out
right now to you.
But next year, you
will definitely
be able to safe harbor,
enjoy the ability
to categorize and
sub-categorize
your flows.
I love it.
We got more questions,
keep them coming.
And again,
we've got, what?
About 10 minutes or so
left on this broadcast.
If we don't get your
question, wow, we have--
there's so much
awesome in flow
that we're literally
melting the lights
in the set.
So that's exciting.
Anyway, if you do not get
your question answered
in this segment, make
sure that you ask them
on the Trailblazer
Community
so we can get you
an expert answer.
And actually we're
going to take--
I'm going to--
Waseem, I hope
you're ready because
I'm going to throw it
back to you for
a minute while we
see if we can actually
fix this real quick.
So Waseem, give us a
little update of what's
happening in the chat.
All right.
Lots of love in the
chat like always.
Let's see what's going on.
People, we're seeing a lot
of yes, a lot of yeses,
a lot of emojis.
Let's see.
Adam is saying
I'll put that
in my piggy bank of
future blog post ideas
just from reading all
these new insights
on automation.
So, yeah, if
this inspires you
to write a blog on
automation, please,
I welcome that.
Now let's get back into--
let's see.
We have a lot of love
for reactive screen flows
are awesome.
Thank you, Mark.
You've been very
engaged with us.
Let's see.
What else do we got?
Oh, I'm actually
getting a lot of love
from all of you.
James, my biggest
fan, no question just
got to say you're
awesome Waseem.
We appreciate you.
Somebody said
#WaseemForPresident.
I love you.
Thank you for that.
See, it's not
just technical.
We're all fans.
All right.
Let's see.
Adam has a fun
fact, I'm a big fan
of fun facts for
the Flownatics.
Fun fact, reactivity
makes capture components
much more powerful.
Now, we can get back
to the questions.
So this one's coming from
Andrew Russo, our guy.
When will flow
Trigger Explorer
work for managed
package flows?
Diana, you want
to take this one.
It should already
display managed
package-triggered flows.
So if it's not, that
might be a support case.
It doesn't allow
for editing them.
You can't edit the
order, and that's
very intentional
and we're not
planning to change that.
But they should show up.
So if they're not, there
may be a bug or maybe
first gen, second
gen packaging.
There may be some
oddities there
that I'm not aware of.
But in general,
we actually added.
We didn't have a
chance to show it,
but we added a filter
in this release.
So that might
be something.
There's a little
filter button,
and you can show either
all of your flows
or just your managed
package flows.
So maybe check
that filter out
if something isn't
showing up or not.
But they should be there.
And there's a
feature that we
didn't have time to
cover but filters
in flow trigger--
Explorer also
in Winter '24.
Hey, hey.
Thanks Andrew
for exposing--
Thank you Andrew for
giving that up for me.
Yeah, Diana, one could
say we're overflowing.
We're overflowing
perhaps with features.
We don't have time
for all of them.
I love it Rubin.
New to the team,
not new to the puns.
Seriously, you're
fitting in just fine.
There we go.
Really, really settling
into the flow of things.
We have another
question here.
Diana, this is probably
your territory.
This is from Brian Taylor
on Salesforce Plus.
Can we get ISNEW
as a flow entry
criteria without formulas?
That's a great idea.
I don't have
that necessarily
at the top of my list.
It is available in the
formula as was mentioned.
But I think that's
a really good idea
and also might be useful
later on in the flow too.
So a lot of times
we put something
like that in
entry conditions.
We also try to put it
in the record filter
later on in the
decision and things.
So it might be a little
more work to do that.
So let me know if you
just want it in criteria,
but that's a
great one to add
the list of good ideas.
IdeaExchange.
Brian, thank you for
the contribution.
Make sure you put it
on the IdeaExchange.
The next question I
have here, let's see,
we have a question for--
Henry, I'm going to
come back to you.
All right.
Can you transform
values in collections?
Yes, you can.
You use the same
formula, but then you
have to add that little
bracket dollar sign
each item syntax in there
to let the system know
that you're working with
a list instead of just
a single record.
Thank you for that.
All right.
We've got more questions.
There's a question
that apparently I'm
supposed to answer.
So this will be fun.
Is there any roadmap
for rich text input
in screen flows?
We're not allowed to add
unofficial SF components
in our environment.
This is from Court Malone.
And the expert answer, I
can provide you, Court,
is that a rich text
component is on the radar
but not on the
immediate roadmap.
Post it on the
IdeaExchange.
And I have one more
of these, speaking
of IdeaExchange,
Steve you also
asked a question
about when
will reactive
screen flows react
to record field changes?
And the expert
answer is not yet,
but put it on
the IdeaExchange.
I don't know
about these are
expert answers
at this point,
but I appreciate
the context.
I'm going to pivot
for just a second.
As we're getting to the
last few minutes here,
we are going to answer
some more questions.
But I wanted to ask you
more as product managers
about the future.
How you're feeling about
where the products are
going with the
advent of AI,
everything is really
shifted this year.
And so in all the
exciting innovations
that you've developed
for Winter '24.
How are you feeling?
What are you most
looking forward to,
and where do you
see it all heading?
What makes you re
really excited?
Henry, I'm going
to start with you.
Yeah, that's a
tough question.
But I think I'm really
excited about where
it's going.
And I think even for
my own product area,
I think in the future
people can ask questions
or ask things like, hey,
I want this data shape
into this data shape.
Can you just do it for me.
So then basically
just take out
the whole entire
complex area of formulas
and transform,
join, which one
do I choose,
all of those can
be taken care of by AI.
And I think that's
really exciting.
That is making it
easier to build.
I love it.
Now Rubin, you've
only been with us
a little over a month.
Yeah.
Actually from a
newbie perspective,
I'd really be
interested to hear about
what are you most
looking forward
to as these products
continue to develop?
I'm honestly I'd say,
they're two things.
The first is all of you.
I'm so, so grateful
to get to interact
with people that care this
much about what we do.
As a new
graduate, I always
hear that one of
the biggest things
to be mindful of is
creating Community,
and it's incredible
to imagine
that the work that I
do cultivates something
so powerful.
And then I guess more
product related actually,
this is something I
touched on a little bit,
but accessibility.
It's really, really
gratifying and important
to me to make sure
that what we do here
is really reliable
for everybody.
And I think it
speaks a lot
to our incredible
Community that
is an absolute priority
with, for example,
screen flow, so
I'm excited to see
how that continues
to permeate
what we build here.
I love that.
I feel like
accessibility should
be a new value added.
I guess it's
built into trust
but yes, that's great
Thank you for that.
Abhi, your turn.
Sure.
So Gillian you
mentioned AI.
And one of the
things that I
was able to do when
ChatGPT first came out,
and I'm going off
on a tangent here
but I promise it pays off.
We're on the
journey with you.
When ChatGPT came out,
it made it a lot easier
for me to write code
to do small things here
and there.
And when I
realized how good
it was at doing this, I
thought to myself, well,
wait a second
flows consist
of a lot of
metadata, what if I
could feed ChatGPT all
of the components that
make up a flow and have
it create that for me?
And that's exactly what
our Einstein GPT for flow
teams are doing now,
or whatever name
they've chosen to
take at this point.
You're right.
And so I'm very
excited at the prospect
of making it much easier
to build automation.
And what that means
for the audience
that we're now
building features for,
historically, we've had a
very technical developer
persona who
works on flows.
And it's for
good reason flows
can do so many things.
There are so
many things you
need to be able
to just not put
in the hands of every user
in your Salesforce org.
But now that
we're introducing
AI to make the process
a lot simpler, easier
to both execute
on and understand,
I'm very excited at
seeing just how many more
users we can now bring
into the automation
world, maybe at a
more controlled level
and a safer level,
but just being
able to really empower
more and more users
because flow is
amazing, and I
want as many
people to safely
use it as possible.
Would you say that
the future is bright
for us declarative
users now
with building in
the age of AI?
I'll say yes,
the future is
fabulous for the future.
Diana, round us out.
Yeah, I kind of follows
on what Abhi said.
I really think
what flow did
with taking stuff that had
traditionally been done
in code and making
it much easier
and broadening
it to people,
I see AI is doing
that again at even
a bigger scale.
And one of the things
that always hits home
for me is it's not just
the ability to do it,
but it's also knowing
what to build.
And that's where our
admins are so important.
We've seen in flows is
figuring out not just,
I can build something
really cool,
but what do my
users need, what's
going to make my business
process more efficient?
And so I really
see that skill
set in our admin team
that they've used in flow.
And I think that's going
to become even more
important because
we can build
a cool tool to build
your flow for you using
all this AI.
But what you're putting
into that prompt, what
you're putting in,
I think that really
comes from the expertise,
the admins have
on the ground in their
companies, in their orgs.
And I think that is
even more crucial
as we step forward
and go ahead.
So I'm super
excited for that
to be part of our
admin toolkit.
I love that.
Well, you got to
put the humans
in the center of
it, and the humans
are the builders
in this case.
Exactly.
And so now all
of these tools
are going to make it so
much easier for us humans
to build really
amazing things
and powerful solutions.
I want to thank
you all so much.
We were just having
you in the hot seat
for like 90 minutes here.
So I appreciate you.
Waseem, I so
appreciate you
for joining us and
representing the chat.
Thank you all of you
so much for tuning in.
It's been so fun to
see the reactions.
We answered a
ton of questions,
but there's also
a ton of questions
we did not get to answer.
So please, please,
please post your question
in the Trailblazer
Community.
We'll make sure
that an expert
follows up and answers
your question there.
Now if you missed
any of our shows
for Winter '24 Release
Readiness Live,
you can get
those on demand
right here on
Salesforce Plus.
Admin, developer, sales,
CRM, service, flow,
all of that's going to
be available on demand
Thank you so much
for tuning in,
and we'll catch you
next time in the cloud.
[MUSIC PLAYING]
Resume AutoScroll
Link copied to clipboard
Salesforce Flow Winter '24
Discover the top features in the Winter 24 release. Learn about screen flows, the new transform element, extensible flow orchestration objects, HTTP post-action and more.
Starring
- Rubin RoyAssociate Product Manager, Salesforce
- Abhishek SharmaProduct Manager, Salesforce
- Diana JaffeSenior Director, Product Management, Salesforce
- Henry LiuDirector, Product Management, Salesforce
- Gillian BruceSenior Director, Developer Marketing, 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.
