Play
Show Navigation
Show Transcript
00:00
Play
Seek 10 seconds backwards
Seek 10 seconds forward
00:00 / 01:07:15
Mute
Disable Captions
Settings
Picture in picture
Fullscreen
Search in video
You can search the video captions for specific words or phrases.
Popout transcript
Hide Transcript
Skip transcript
Welcome to Release Readiness Live.
It is important to watch Release
Readiness Live,
so that you get a snippet
of the coming attractions
of the functionality
that's coming from Salesforce.
We really focus on the features
that are going to be most useful
and impactful with release readiness.
Why have you got the great opportunity
to actually hear it
from the mouths of the people
who spend a lot of time
thinking about what exactly you all are?
Salesforce developers and admins
are actually wanting to see
your feedback is so important.
I think that's
one of the most amazing things
actually about the Salesforce
ecosystem, is how involved
trailblazers are with
evolution of our products
is really about to start.
Let's get started.
Welcome to Release Readiness Live.
I'm Carolyn Bathauer,
our senior customer
and product evangelist
and sometimes also known
as Salesforce Sparkle Pony
and your new host of RL.
I love bringing you
all of the great new release
readiness content,
and this week has been
nothing short of amazing.
We have one final episode for you.
It is the admin preview.
Over the next hour,
our amazing
product managers
will give us live demos
highlighting the top admin features
in the Winter 25 release
and making a special appearance.
Angela Lee,
Director of Product
Management of Agentforce,
is here with us.
But before we dive into
what's new for admins,
I do need to remind you
to only make
purchasing decisions
on existing features and functionality.
And here at Salesforce,
we always like to start with a
thank you
for investing your time with us today
and for all the feedback
that you provide.
We're listening
and it makes our product better.
You can find today's episode
and all of our
our our
our RL content on demand on Salesforce.
Plus check out Sales Flow,
Developer Service, Health Cloud and CRM.
And as you watch,
join the chat on Salesforce Plus,
we have product experts
standing by to answer your questions.
So go ahead and drop them in the Q&A.
And we'll also take
some of your questions live.
And if you still have questions
after the show,
you can post them in the Release
Readiness Trailblazer Community
hashtag Salesforce RL.
All right, let's get into it.
First up,
Ben Sklar,
Director of Product Management.
And he's here to show us the latest
in user access enhancements.
Ben take it away.
Thank you Carolyn.
Hey everyone.
My name is Ben Sklar.
I'm a director of product management
on the Salesforce platform,
and I manage our back end data services
like the user interface API,
the GraphQL API, and the setup platform.
And I'm so excited today
to talk about the new user
access enhancements
coming in winter of 25.
Up first
we are modernizing the user list views.
We are bringing the same list
view that you all know and love
from Salesforce
into the admin experience.
And with that,
you'll be able to customize the user
list view
and select the fields
that you want to see in that list view.
You'll also be able to pin
your most useless view
for easy access later.
And we're finally
bringing inline editing,
which I know you
admins are so excited about.
You'll be able to edit fields
directly from the list.
This was over 12,000 ID change points.
Please know that this must be turned
on in the user management
settings in the winter release.
And that's because there's a few fields
that are not yet supported,
but we're working very hard
to get those fields out
for a future release
so that this can be on by default.
But for now,
please turn it on
in the user management settings.
Now we've also enhanced the user access
summary
and to let you all in
on a little secret.
The User Access
summary is going to become
the new User Record page.
Now in the winter release,
we can now
edit key,
standard and custom fields
right from the summary.
And we have a new row
level action
called access granted
by where you can see
where a user is getting access
from right in the summary.
And we're going to see that soon.
We're also
launching our brand new object
Access summary.
So you can see how access is granted
right in the object manager.
This was over 10,000 idea
exchange points.
And we're excited to show it to you live
very soon.
We've also enhanced the public group
access summary
and to let you all in on another secret,
the public group summary
is going to become
the new public group page.
And so we have an all new experience
for managing public group membership.
You can add
and remove members
right from the summary.
Now, a few of you admins came up to us
earlier this year at trailblazer D,
and you asked us
why is there no description
field on public groups and queues?
And we didn't have a good answer for you
because we really should have had it.
So we do now as of the winter release
and this was 2000 ID
exchange points, we could retire.
All right.
It's time to see
some of these features live in action.
So let's go right to the demo.
So I am going to go now inside of setup.
And I'm going to go to the user
management settings.
And I am going to enable
the new enhanced User list view.
Now that that's turned on
I'm going to go to users.
And as an admin
there's a few things
I need to do on my plate.
There is a user named Jenny
who's in sales
and she had a great quarter.
It's time to give her a promotion.
So let's go ahead and create a new list.
View.
We're going to call it my list view.
And we are going to save.
And there it is.
And what I'm going to do
I am going to add a new field.
I'm going to add
the title field to the visible fields.
And I'm going to move that up.
All right.
Now we're going to search for
Jenny Sales who is getting promoted.
And we can see she's
currently a sales rep.
We're going to make her
a senior sales rep.
And I'm doing this inline
right in the user list view.
And if I wanted to
I could edit the title of other users
all at once.
I'm going to go ahead and hit save.
And there it is.
How much easier is that? Wow.
I'm going to click on Jenny
now and I'm just going to confirm.
There she is.
She's a senior sales rep.
Now, I've been told that
Jenny can delete accounts
and we don't want that.
So I'm going to confirm that first.
I'm going to go to the summary.
I'm going to go to Object Permissions.
And I'm confirming here
that for the account
object
she in fact can delete accounts
which we don't want.
So why is that the case.
Well we're going to look at that
new row level action
called access granted by.
And inside
we can see
all of the permissions sets,
the permissions set groups
and the profiles
that grant access
to the account object for Jenny.
We can see it's not a permissions set
but it's actually a permissions
set group.
It's the sales rep and also her profile
the sales reps profile
that lets Jenny
delete the account object.
So now that I know that
I can go into that profile
and into that permission and set group
and make the necessary changes.
The last thing we need to
do on our plates,
we need to check for the contact object.
How are we getting access to this across
all permissions, sets?
Permissions, set groups and profiles.
So I'm going to go
into the object manager for contact.
And then going to go to Object Access.
And wow
in just one click
I can see all of my permissions sets.
And in a few more I can see
all the permissions, set groups
and profiles
that are granting access
to the contact object
and the level of access,
all in just a few clicks.
This is going to save me so many hours,
and I know it's going
to save all of you admins
so many hours of time as well.
We don't need to click
into every permissions
set one by one, or permission set, group
or profile to find out
how we're getting access.
It's all right here.
And that concludes the demo.
Let's talk about our plan
and roadmap
and vision
for user management
over the next 6 to 18 months.
We've got a lot of awesome new features
we have planned.
We're going to add more summaries.
We're going to have more list views.
We're going to start adding
troubleshooting with AI and Agentforce.
We're going to be able to clone.
Users will be able to compare access
between users
and between permission sets,
and will even be able to export the data
you see in the summary as well.
However,
we want to hear from all of you
admins out there.
So let's keep the conversation
going on the new Roadmap exchange,
which is now available in beta on here
you can share with us your use cases.
You can check out
all the latest features,
you can comment on our plan features,
and even post new exchange ideas.
So head over to SFD Eco Slash
User Access Roadmap
and let's keep the conversation going.
Your feedback is so valuable to us
and we want to hear from you.
With that, thank you all so much.
I'm going to pass it back to Carolyn.
Awesome. Great job.
This chat is on fire.
There are a few, it's like Christmas.
Jamie says this one.
I do love Steve.
User lists are finally getting off
the eight bit Nintendo UX.
And then also, user
list is
the update of my dreams,
according to Julia.
So thank you all for tuning in.
If you do have questions for Ben,
please post them in the Q&A chat
because we do have some coming up.
But we have people tuning in
from all over the world.
Mark Jones he says, hi everyone.
Happy to be joining you
all from Northeast England.
So we've got quite the crew out there.
They are excited.
So let's dive into some questions.
I am going to Brendan, who is asking,
can you change things like user profile
or role with inline editing?
With inline editing.
You should be able to edit
a lot of the fields
inside the user list view.
However,
there are some fields that you cannot.
This is a great question
and I don't want to
give the wrong answer.
So we're going to give
get back to you on that on the,
trailblazer.
Yeah, great.
We will absolutely do that.
We'll make sure we mark that.
We have another question about,
how do I find out how a user
is getting access
to a permission or object
or field in the summary?
Yeah. Do they get it?
Yeah, it's a great question.
So if you go to our user access summary,
this was the new, access granted by row
level action.
So when you're in that summary
and you're looking at either
user permissions or object
permissions and custom permissions
on the right hand side,
you'll see that row level action
click Access granted by.
Then you'll see
all the permissions,
sets, permissions,
set groups and profiles,
and the level of access for all of those
for whether it's a permission or,
an object permission.
That's awesome.
The comments are still coming
in, and we'll get to those.
Someone said,
I can't
if I can't see the new user list view,
how do I turn it on?
Yeah. Yeah.
So right now in winter,
you would go to the user
management settings
and you would turn on the enhanced user
list view.
And in the future
we hope to just have this on by default.
But for now you have to
turn it on there. Great.
One more question
Keira is asking do permissions
set groups?
Factor in, muting permissions?
That's a great question as well.
I will have to give. Okay.
We'll mark that one too. Okay great.
Ben is going to be here
at the end of the show
for a panel Q&A,
so make sure you keep
those questions coming.
Thank you again.
And now next up to cover a fan favorite
flow enhancement in winter 25
is Adam White,
director of product management.
And we're going to talk automation.
Make sure you're posting your questions
now in the Q&A.
Because we are going to follow up
this demo with questions for Adam.
So Adam over to you.
Right.
Thank you.
So I am so excited
because this is actually my first admin.
I've been on quite a few flow URLs,
but I've been actually chomping
at the bit
to to take the reins from Diana.
And by the way,
I came prepared, as you can see,
I did buy them on a very popular
marketplace online.
So if you're curious where I got them,
that's where I got them.
Now let's dive right in.
So a lot of
you know that I am very excited
about all the awesome things
that we're doing.
And screen flows
like screen flow reactivity.
Now we're going to use a
very common use case
used by screen flows
quickly creating records. Right.
So I've created a little demo here
to highlight our brand new component
the action button.
Now a lot of times you need to quickly
let users create contacts.
But if you're like me,
you got to worry about
duplicate records.
So how are we going to solve this?
Well,
usually users
will type in the results here
and they might actually be creating
a duplicate unknowingly.
So I've created an action button here.
The action button allows you to trigger
auto launched flows
and bring the results
back into the same screen.
So what this is doing
is fetching potential duplicate
records, right?
But you may not have enough information
in a three column
data table to determine
if something is actually a duplicate.
So I've actually added
another action button
to return more information
about that contact record.
And I'm
pretty familiar with this person,
so I can actually see that
they have recent cases with us.
And they matched the other accounts
that I'm expecting. So
like a
good citizen,
I'm not going to create that
duplicate record.
So hooray for clean data, right?
Now another thing
I want to call out on the screen here
is we've actually enhanced
the data table component.
So if you have your
components in single select mode
we no longer show radio buttons.
This lets you deselect single records.
Now if you miss those radio buttons,
we didn't get rid of them.
If you mark your date
your data table component as required,
you'll still see those radio buttons.
All right.
Now let's see how this was built.
All right.
So here we are in a screen.
Now I dragged over the action
button here.
And you can see that
we've got a few different things
that we can do at the button level.
We can set it input for the label.
And we can even disable it
so that if we can take advantage
of all the cool reactive formulas
that we released last year.
So if you don't want
that button to be clicked,
you can set a formula to disable it
until all the expected
inputs are completed.
So if I drill in here,
you can see that
we're launching this auto launch flow
that is designed to search for context.
And this looks pretty similar,
if not identical to sub flow.
So if you've set up a sub flow before,
you're going to feel right at home.
So this flow expects a few things.
The email address
and last name fields
first and last name fields,
which are just screen components.
And down below something else cool
that we've added
is that you can actually easily
view the outputs of that record.
So you can see error messages,
the matching contacts,
and even a handy dandy number
for how many contacts we found.
Like if you wanted
to put it in display text
or drive things
like conditional visibility
based off the number of records
that you found.
So over
here is the actual flow that we've run
pretty easy.
Now, the glorious thing about
this is it
can be as simple
or as complex as you need it to be.
So you can use things
like invoke actions
to trigger like cycle or SASl
or like in this case
a pretty basic get records.
So we pass in the first name,
last name email,
and if we find matches off
of any of those things,
we provide the results to the screen.
And just like a sub flow
we have to then provide the output.
So we set the results
from our get records
to an output of matching contacts.
And we have our equals count here
to provide the number
of matching contacts
to a number variable.
And because we're good citizens here
we're having good CamelCase.
Good naming conventions.
So we don't confuse anyone that happens
to look at our flow later.
So if you go back over, you
can see this other action button here.
Now, this one I built generically.
So this can actually take
a single contact
ID or multiple contact IDs.
Now the important thing is here
when you're building these action flows,
you want to think about
how you can reuse them
across multiple flows. Right.
Because you're probably going
to have a lot of flows
in your org
that try to get contact data.
Now this one can do
a whole lot of things.
It can provide,
other account contact
relationships,
cases, products,
orders, the entire record itself.
Now all of these things
can be freely referenced
as soon as they're run on the screen.
So if I have my data
table component here,
we have a whole new section
in our property
editor called Screen
Actions, where you can then
select the results of your action.
And then as soon as those things change,
it just changes automatically.
Nothing else is needed.
Now what if you wanted
to get super duper fancy for you
advanced fanatics out there?
Well, I have a cool little flow
that I built
that lets you check weather.
So imagine
you're like a field service agent
or a field service dispatcher,
or your and got account
rep that want to schedule
an outdoor event.
Weather is pretty important.
So I've built a little flow here
that hits
the AccuWeather API
and returns a five day forecast
and puts it all in a data table.
So you can see here
it takes in a zip code.
And then I get a five day forecast.
So I can see that October
12th has a 0% chance of rain 82 degrees.
That's that's pretty nice.
Schedule that appointment right away.
I'm really excited to share
how this house was built.
Didn't have time to show how it was
built for this show,
but I'll be happy to do recording.
Just tag me in the trailblazer community
and I can do a little show for you,
but I have so much more to show.
So let's dive back over to our slides.
So one
awesome thing that we've done
this release
is that we have overhauled
the save time validation experience.
So we no longer show errors
with your flow
and a tiny little motor
in the top right.
We now have a full fledged panel
that lets you easily discern
what issues your flow has,
which is a huge quality of life
improvement.
Now, if you were
paying attention in the Flow
Release Readiness Live on Wednesday,
we also covered something else
that's coming. Upsert.
So last release, you can
you can actually upsert a single record,
but now you can upsert multiple records,
making your flows
significantly more performant
and most importantly,
cleaning up your canvas
so you don't need multiple
loops to determine
which context you have to create,
which ones you have to update.
Huge, huge win and a really popular ask
in the community.
Now next up, more screen flow love.
We've made some enhancements
to the repeater component.
Now the repeater component,
if you haven't played around with it
yet, allows you to embed
repeatable sections of screen components
that let your users embed
lists, and lets
you embed lists of data for your users
to create and update on the fly.
Now this release,
we've added the ability for you
to define a record collection
as your source data
so that when your users enter
the screen, they'll already have record.
So all I have to do is add
or remove or update,
which is just
a godsend for people
that don't want to navigate
between related lists.
All they need to do or update
a few fields across records.
Huge. Huge win.
Really exciting feature.
Now, another another thing I inherited
from Diana
that I wanted to bring up over
here was the idea of Flow Paree.
There's so many things that cover
this release that,
you know,
sometimes we just have to hit them
real fast.
This is actually a really big one.
We've made significant improvements
to the email action.
So the first thing that we did
was we added CC
and BCC capabilities to the action,
which was alone 27,000 points.
Now we also added, and we
also raised the email action
recipient limit
from a sad five to a nice meaty
150, which huge win.
And it really lets
you use this action
in far more places and use cases,
more screen flow love.
So for those of you that like to use
the choice lookup component,
you can now select multiple records.
Now with the choice lookup component,
you can have a lookup like experience
for things like Picklist values.
And most importantly,
you can filter the records
within them based off other things
that you've done in your screen.
So a really cool component
made even cooler
by allowing you to do multi-select.
And we also gave Transform
Some Love this release.
So for you up for you
intermediate folks and advanced folks,
you'll know that a common pain
point is converting record collections
to what we call
primitive collections
or basic collections,
like text collections.
So here
you can select something
like an account collection
and convert
all the IDs to a text collection,
and then use them in other places
that need it.
For example the in operator.
So you no longer need to use
loops or sub flows or apex
to do all of that for you.
All right. Here.
Making your flow better.
Another really cool
thing if you've had a chance
to play around with Einstein one
and I,
we now let you generate
formulas directly
within the formula editor.
Simply tell it what you need,
provide your variable names
and you're done.
No more fiddling around with ChatGPT
and hoping that something works.
Really awesome game
changing improvement for folks.
And lastly, I call this,
you know, a small but mighty feature.
We now show the API name for components
that cannot be rendered
for preview, right?
So before we would just show the API.
The API name
or the type of the component.
Now we show the label
or API name depending on
which one is supported directly in here.
So if you've got five
different custom components
before they would all said
the same thing.
You'd have to click through each of them
to figure out which one
you need to edit.
Now it's all right there.
And that's all I've got.
I'm really excited
about everything coming this release.
I couldn't even fit everything in it,
but I'm excited to dive into some Q&A.
Thanks, Adam.
Questions are coming
in, so we are going to get to them.
If you have more questions for Adam,
please post them in the Q&A
tab on Salesforce Plus.
But first,
everybody loves that you're here.
Loves your goggles.
Julia said
my flows are about
to be so much cleaner.
Cannot wait.
And Jacques said I have five over five.
Flow is in my current org.
The email action
improvement is helping me with.
Thank you for that one for sure.
So lots of love in the chat.
But we do have questions.
Are you ready?
All right. Ready, ready.
John Ashe
and I believe this came in
during the contact flow.
Can this be exposed to external users?
For example,
when an external user
creates a community user?
Sure. Yeah.
Definitely.
You know, with the external data,
you always want to be a little careful
about what kind of data
you're putting into it.
But as long as that user
has access to the auto
launch flow
that you're running, it'll work
just fine. Great.
And let's stay on contact flow.
Brandon is asking
if you can supply
the contact flow as a template.
I'd love to recreate this for my org.
Sure.
Yeah, I'd be happy to post
how I did it on the community.
It's, you know, very, very simple.
It's a very popular use case,
so I'd imagine you're not alone there.
And we're going to be even making this
even better, next release.
So I'm gonna
see if that if,
that little spoiler comes up again,
but I'll put up with.
Okay, we'll keep the questions coming.
Adam is in a agreeable mood,
so let's keep asking for this wish list.
We love this.
Mark Jones is,
having a bit of an issue
with reactive screen flows.
I found the ability to auto populate
a repeater component isn't reactive.
I've tried
this using both a choice
lookup and a data fetcher.
Is the repeater component reactive yet?
And if not, is that on the roadmap
for a future release?
Yeah, so that's a great question.
There are a few reactivity
related gaps with the repeater
action buttons are one of them.
So there are a few things.
One and action buttons results
can't go into a repeater
and an action button
can't dynamically generate a repeater.
So there are a few gaps,
most notably formulas within repeater.
So formulas
are a pretty big driver of reactivity.
And we don't yet have a way to
establish what we call context
within the repeater.
So if you're creating a formula,
we actually don't know
that you're in a repeater,
which is kind of a, you know,
a catch 22.
But one of those things
that we have to solve for
is the ability to know
that you're referencing a repeater,
wherever you are,
when you're building your screen.
So once we get over that hump,
we'll address all those other issues.
But we are aware that that is an issue.
Great.
And then Tomo is asking if do
we need to have
a duplicate rule on both contact
and account object?
Tomo says my org is very old.
I call that seasoned,
but interchangeable.
So do you have to have a duplicate rule
on both contact and account objects?
So my flow is not built using
duplicate rules.
However,
that would actually be something
that you would see
if you tried to do
an actual what we call DML.
So if you tried
to actually create that record
and you had a duplicate rule,
you'd see an error.
So my goal was,
preventing that from happening.
But, you know,
you're going to have contacts
created anywhere in your system,
not just,
you know, an amazing screen
flow that we built, right?
You have data loads.
You have a lot of places
where you need to protect your data.
I would recommend
creating duplicate rules
just as a good practice.
So, not for that flow in particular,
but in general
they're good to have good, good
best practices.
And then Tim is wondering,
is it possible for the action button
to trigger a duplicate rule
to check for duplicate records?
Yes.
So, that again,
that is one of the glorious things
about using auto launch flows.
I don't think we have an out of the box
way of detecting duplicates,
but I'm pretty sure
Rick up to on automation
champion built,
a really easy invoke
about action that you could
then put in one of these
auto launch flows to do that.
Awesome.
So, Adam, everybody is very,
very excited.
Elena would like to know
how to turn on the AI formula helper.
Yeah.
So, for that
you need to first up into it
and process automation settings.
But you also have to have the Einstein
one SKUs.
So all the AI SKUs. Great.
And then we did
talk, earlier in the week
a lot about repeaters, and loops.
So Katarina would like to know
if you still need loops
with the repeater and then
sadly, yes.
So if, if we,
if you watched the Q
and A section of the
the flow URL,
you'll hear Sam Reynard
at the PM for repeater.
Lament
that unfortunately,
we couldn't get transform support,
but longer term
we really, really,
really want transform support.
So instead of looping over those,
repeater outputs,
you just be able to easily
transform them
into the format that you want.
So unfortunately, we are
we are kind of stuck with loops,
but we do aim to get it,
into transform soon. Great.
Well, I believe
we are coming up to the end,
but one of the things
everybody always wants to know
is a little bit of a sneak peak.
So what are you
most excited about
when you look at the roadmap coming up?
Yeah, I know it's hard to pick one thing
because you all are shipping
so much greatness,
but what are you most excited about?
It's like choosing a favorite child.
Yeah, that's really tough.
So I mean, just to keep things
close to the use case here,
one of the things that
my team is working on right now
is a buttonless version
of those screen actions.
So imagine me filling out that, that,
contact form there in the beginning
and showing duplicates
as I type,
or calling them
reactive screen actions.
You can
see, even see it in the
the component preview
that I had had on the screen.
It's heavily inspired by the Data
Fetcher component
out there on the Appexchange,
which is had been a huge, huge hit.
And, I'm really excited for that one.
And then just
some of the other things
coming in better
have just been asked
for such a long time.
Like for example, adding
limit to get records
has been a big blocker
for companies
that have, objects that have,
you know, 50,000 plus records
who are getting query limit errors.
Right?
So that's
something that we're working on.
And I even got the go ahead
to talk about
one of the cool thing coming that
I think people get super jazzed about.
We're looking at adding collapsible
and grouped elements in the canvas
so that you can,
create groups of content
and elements in your screen
to create a more organized, flow.
Amazing.
You know, I just have to say that,
Julia has said admin preview already.
The MVP of release readiness.
So thank you so much for joining us
and for your time and expertise.
Thanks.
Next up
we have Elizabeth Martin,
senior product manager
for Records Experience.
She is here with us to show you
the latest in lightning
app builder Elizabeth.
The floor is yours.
Thanks so much, Julie.
As a apologies,
I am the product manager
for the records experience teams,
which
on the UI components
and data providers
for Salesforce records
across the Salesforce platform.
As part of that,
we own dynamic forms
and the roadmap for a dynamic form.
So extremely excited
to be talking about
some of the enhancements
we have there today.
Let's go ahead and dive right into it.
The first feature
that I want to talk about
is conditional field formatting
and specifically icon support.
This is going to close out
over 38,000 idea exchange items.
This idea exchange item was create
created all the way back in 2007.
For this feature.
We when we started building it,
we went out to all of you and held
listening sessions earlier
this year to best understand
what use cases
and what challenges
this would help with.
And what we heard from all of you
is that you want to call attention
to key fields based on their values,
so that your end users
don't have to sift
through all of the text
on the page to
understand what's going on.
Now, one thing that I will call out
is that this feature
is going to be available
on a rolling basis,
so it's a slightly staggered release
from our standard release schedule.
And so it's going to be available
in prerelease orgs starting next week.
It's not already in prerelease
orgs like many of the other winter
release features.
The last thing I'll say about this
feature is that it is available
in a low code way, from directly
within lightning app Builder,
so you no longer have to
upload your own images
and create those formula fields.
To be able to create these custom
visual indicators,
we are not releasing highlight support
and this particular release,
so we're not marking
the idea as completely closed yet,
we're only marking it
as partially delivered.
If you are interested
in highlight support,
we we hope to bring that
in a later release.
And we'd love to hear
your use cases for that.
If you want to go ahead and comment
on the idea exchange item,
the next feature that I'm
really excited to
release is
to announce
is the Dynamic Highlights Panel.
This is going to close out
over 20,000 idea
exchange points
across four different IDF
exchange items.
And what it will allow you to do
is manage the fields
for the highlights panel from directly
within Lightning App Builder.
Just like you can manage the fields
for anything else on the page.
Now this gives you
all the capabilities of dynamic forms,
so you can go ahead and apply
conditional visibility rules.
And you can also take advantage of cross
subject fields for fields
in the highlights panel
and conditional field formatting.
As of the winter 25 release,
one of the things that we heard from
all of you
is that the previous
limit of only seven
fields is not enough,
and so we've increased the limit
to the number of fields
in the highlights panel up to 12.
If that's not enough,
I would like to hear from you.
Please reach out via
either your account executive or comment
on the idea of change.
Update whatever is easiest for you,
because we do have the ability
to potentially modify that if needed.
The next feature that I'm
really excited to really to
announce is Einstein for formula.
We had a survey
that was
provided earlier
this year that went out to all of you
to best understand
what are some of the features
that you would like help configuring?
When we're thinking about
adding an AI assisted
configuration capabilities
and one of the things that we heard is
that formulas are really difficult
to manage to understand
what's going on,
especially when you're coming into
maybe an older Salesforce org,
that has a lot of formulas
that maybe you haven't set up.
And also to, to troubleshoot and debug.
Now Brinkley is the product manager
for this particular feature,
and he's available in the chat to answer
all of your difficult questions.
So please don't hold back with those.
And then the last feature
that I'm really excited
to announce
is the list View Multi Consort.
Now this is going to close out
over 80,000 idea exchange plans.
This is a long awaited
feature enhancement.
It will allow you to set up
to five different columns of criteria
for sorting.
This is managed at the individual level.
And once you set this up
it will retain that history.
So when you log back in
you'll still have that configuration.
This is a beta in winter 25.
So you will have to
go into the setup menu
in order to enable it.
It will not be enabled by default.
And note that this release
does not include
the admin defined defaults.
So that is something that we are hoping
to tackle in a future release.
And with that,
let's go ahead and jump into the demo.
Now I'm going to demo today
from the perspective
of a Salesforce admin.
And I'm coming into a new org.
That's new to me.
That has a lot of configuration
that's already there.
And I need to quickly understand
what's been happening,
what's going on,
why have these things been configured
and make some modifications
to some of the layouts?
Now the first thing I'm going to do
is I'm going to jump into
and I need to start understanding
my formula fields.
I might have a number of formula fields
that I need to take a look at,
and as you can see
in this particular example,
this formula field is a little bit
long. It's complex.
There are a lot of
different variables here,
but on the upper right hand
side of the formula editor,
I have a new button
that allows me
to see the formula assistant.
And when I open that up, it tells me
there's no errors with my formula,
it looks good
and I can go ahead and request
that it explains
what's going on with this formula.
And it gives me a quick
little explanation.
It's kind of short.
So I'm going to go ahead
and click more details.
And it gives me a fairly decent
explanation of what
this formula is doing.
Now this is helpful,
but what if there was an error
in this formula?
How could this help with that?
I'm going to go ahead and introduce
an error
by misspelling
one of the fields in the formula.
And after I do that,
I'm going to go ahead and open up
that formula assistant again.
And you can see,
unlike the first time that I opened it
up, it's
now telling me that
I have something wrong.
The field types doesn't exist,
and so it suggests
it could potentially fix this.
Now this is really
making my life easier.
Rather than having to kind of sort
through this as an admin
and figure out what's going on,
I can go ahead and select fix.
It provides me
an update that it recommends,
and I can go ahead
and just take that and apply
it directly into my formula field.
So everything looks good.
Now that I've got my formula field
figured out,
I'm going to go ahead
and make some modifications
to my lightning record page.
Now I need to make some updates
to my account page,
and I would like to apply
some visibility rules
to fields on the highlights panel.
So I'm going to go ahead
and get rid of the old highlights panel
and go to the fields palette
and bring the new
Dynamic Highlights panel in.
Now from here,
once I bring my highlights
panel in,
I can start bringing on my basic fields
that I want to see
and I can go ahead and bring
all of my fields from directly
in the Lightning App Builder.
I'm going to bring my new field
that I just created,
the account temperature field.
And then I'm going to bring the
number of open cases field,
which is actually,
summarizing
all of the open cases across this for
now.
This number of open cases
field is actually not relevant
unless it's at a level
that's of concern.
So I'm going to apply a visibility
rule to this field.
And I don't want it to show
in the highlights panel
at the top of the page
unless it's greater than three.
If it's not greater than three,
I don't need to see it
right at the top of the page.
Now, I'm also
going to go
ahead and apply
a formatting rule set to this.
You can see I have a new option
to do this from the property panel.
And I'm going to create a new rule set.
Now a rule set
could contain a single rule.
It could contain multiple.
I'm just going to do a single one today.
And this is just going to
include an indicator
when the number of open cases.
Is greater than or equal to five.
So we don't want it
to show up in the highlights
panel if it's less than three.
And once it starts to get even larger
greater than five,
then we actually want to
apply a warning indicator
so that our account wraps.
Attention is called to that,
and they're not reaching
out to that customer if that's the case.
Now you can see here
I could add additional rules.
If I wanted to.
I could have additional rules
based on other criteria
so it could show different icons
based on different values.
But for now
I'm just going to use this
simple example.
And we can go ahead and save the page
and jump back
and take a look at the runtime.
And I will go ahead and refresh
to make sure that I have
the latest configuration.
And once we jump back here,
we can see we have our new Dynamic
Highlights panel with the fields
we just configured.
In Lightning App Builder,
we have our number of open cases.
Field is actually hidden.
Because you can see
as it's it's
showing down here in the case
information section,
there are only three open cases.
And so we don't necessarily
need to have that front and center
for our account row.
Now let's jump over to a different page
just to take a look
at what this might look like
with a different scenario.
For this particular account,
there are actually eight open cases.
And so we have that field
showing up at the top.
We can call our account reps
attention to it immediately.
This is actually at a level
that's probably
where they might not want
to be reaching out to the customer.
So we have that warning indicator
using conditional feel formatting.
There.
And that wraps up our demo.
And just one last thing
that I would like to call out
is that we'd love to continue
this conversation
on the roadmap exchange.
You saw this slide earlier.
From
then we have another short link
for the lightning platform roadmap.
You can see at the bottom
Stagecoach slash
lightning platform roadmap.
And there you can see
all of the features
we've recently delivered,
the ones that we have in progress
and those that are planned
and those that we're seeking
feedback on.
We'd love to hear your feedback
and your use cases.
And that wraps it up for my side.
Thank you so much, Elizabeth.
We've got a lot of comments in the chat.
Also, a lot of questions.
Not a surprise at all.
First,
Squire says don't underestimate
the power of conditional formatting.
Such a great way to improve your UX.
Nadia says,
oh my gosh, this is so cool.
So great job.
So let's jump into some questions
Steve is asking
if conditional formatting
needs to be turned on.
I haven't seen it
appear on any field
using dynamic forms yet.
Great question.
And this
is back to,
what I mentioned
about the staggered release.
So this is going to be available
in prerelease orgs next week.
We expect the 15th
or the 16th safe harbor,
and then it will be available
on a rolling basis from there.
So we expect it to be and sandbox works
towards the end of October
and in production in early November.
Great.
Let's stay there. On availability.
When will the conditional
formatting feature be of?
Oh wait, you're just for the dynamic
highlights panel?
Is that is it available in both?
Yes, it will be the same availability
for the highlights panel
as it is for the rest of the page.
Got it. Great.
And then Mark Jones has some feedback.
You see,
the dynamic highlights
panel has a lot of white space
above and below the fields.
Is this something that we can reduce?
That's a good question.
I would try compact the compact setting.
I think I had it
on the less compact
setting and see if that helps.
But other than that,
we'd love to hear that feedback.
And so,
maybe reach out and provide
that feedback on the idea
exchange update.
If you're still having trouble, great,
because you are knocking down
those points.
I think you might have set a record,
this release readiness.
We'll have to check into that.
But Tim is asking
if there will ever be permission
based list view.
I love to limit
what views are available
based on the profile or permissions.
That's a great question.
I will
I think that's a good one for the chat,
and I will jump in
and make sure with our product manager
and confirm the answer there
and get back in the chat. Thank you.
We also have a question
coming in from Harrison.
Does the dynamic highlights
panel have the same limitations
around number of fields
that can be displayed?
The number of fields is increased
from the previous
limit of seven up to 12.
And if that's not enough,
we'd love to hear the feedback.
And so that's another
great one to comment on.
The idea exchange update. Great.
We're going to stay there
because Steve is asking,
something around
that if,
with the new increase, it's great.
But if I have a field
that is currently hidden,
can I replace this field
with another temporarily
making the actual highlighted fields 13
but not using them all?
That's a good question.
Let me double
check that and confirm the three
I get back to.
Then I'll get back to that
in the chat as well. Great.
And then similar question
to you to wrap things up.
Everyone loves
release or adding a slide,
but they all feel like
those little sneak peeks.
I think so far
everybody has spilled a few secrets.
So I would love to understand from you.
What are you most excited
about for roadmap?
One of the things I'm most excited about
is enabling AI assisted configuration
and setup.
We're looking
at some new potential features
to help with page
generation and page optimization.
Looking at ways to help admins
who are maybe coming into or so
they've inherited to understand
what's being used the most,
what's going to be most valuable
for their end users,
specifically using AI.
So I won't say more there,
but if if all of you have use cases,
have questions about that,
we'd love to hear from you.
And so it'd be great if you reach out.
Great.
Thank you so much,
Elizabeth, for your time
and for your efforts.
Everyone is seemingly loving
what you have
brought to the table today,
so thank you.
And next
we have Aaron Kail,
Director of Product Management.
He is here to dig into Agentforce
and Agent Builder.
So Aaron, show us what
admins need to know about.
Awesome.
Thank you so much. Hi everyone.
I'm excited to share with you today
a little bit about Agentforce
and how you admins
can start building agents
and bringing these to life.
So as you may have heard,
we are launching
Agentforce this October
and we're very excited about it.
We will have standard agents
for sales for service,
but we're really going to focus on today
because as admin,
how do you build your own
and customize these agents.
And that's what our agent Builders for.
It's our easy interface
to configure agents,
connect them to channels,
control the knowledge they use,
and then preview and test
that which we know
is critically important.
So I'm going to spend as much time
as I can showing
what it looks like for real.
But I'm going to start
with a couple slides
just to ground us in the key concepts
of how these agents work.
And we'll start with
what are the fundamental
building blocks of your agent
for agents?
And we're going to talk
about three things
topics, instructions and actions.
What is a topic you can think of topics
like the jobs to be done
that you want this agent to do.
So they can be like high level
buckets of functionality.
There's some example you'll see here
things like order management,
handling repairs,
answering questions from knowledge
managing appointments,
things like that. Big jobs.
You want to give this agent to do.
And just like
when you give a person a job to do,
they need a couple things to do it.
They need instructions.
How do I do this job?
And they need the tools.
They need the actions
they can take to do that job.
And those are their two building blocks.
Instructions are your how to manual.
How do I deploy these actions
to do this job?
How do I go about doing the job?
How would you teach
any person to do this job?
And then actions are tools, and,
actions may be familiar team
from copilot
from previous Air Force releases.
The key thing here is
these are built with the same familiar
platform components
you all know and love.
So you can take any flow and apex
and wrap it up
and make it available to your agent
as a tool, as an action
for it to do it, to get a job done.
Okay.
So how does it actually work?
How does it come together
when agents are trying to do these jobs?
We'll walk through this slide
from left to right and we'll start.
I'd like to
at the beginning with the trigger.
So this is what launches
the agent into action.
We'll focus on a conversational
use case here, a chat message coming in.
But this can be anything.
It can be an invoke action and API.
We'll see that
coming in the roadmap,
opening up the way you can activate
and deploy these agents.
But for now
I'll use a conversational example.
Question comes in from a customer.
What's the status of my order?
The first thing that your agent will do
is compare
that message
and the conversation so far,
and all the context it has to the topics
it has been assigned
to, the jobs it's been given, and say
which topic is most relevant
to help me help this customer right now.
And in this case,
this agent has an order
management topic.
So we'll select that topic.
And at that point we will
the agent will pull up
the instructions and actions
that reside within that topic
and start looping through them
to help
satisfy the customer
and move the conversation forward.
So it might have an instruction about,
you know,
always asking
if their email address before
verifying an order or,
never doing certain things.
Whatever the rules for that job may be,
and then a set of actions available,
it will run through those
using our large language models
to figure out what to do.
And then eventually, once it's
looped through that and gathered
all the information needs,
it will reply back to the customer
with a response.
And if the customer replies again,
we start that whole process again.
So we're going to see this
live in the builder in a moment,
but grounding us a little bit.
Topics, instructions, actions
and how we loop through those to
help customers get jobs that.
Okay, let's take a look at the demo.
So we are now in our agent builder.
Let's start just by orienting ourselves
a little bit.
You see this panel here on the left?
These are our topics.
So these are those jobs to be done with.
This agent has been assigned.
So we have topics
like appointment management
ethics order management.
And if I click into one of those
we'll see those other building
blocks instructions and actions.
So our topic has a name.
It has a description.
This is what the agent uses
to figure out
when to activate this topic.
And it has a scope.
What's the scope of the job.
What are the guardrails there.
In this case,
their job is only to help
with order questions
and warranty questions.
Instructions like I shared
are the how to do this job.
It's your instruction manual.
So before looking at border status,
ask for email order number.
For sharing order status.
We have some instructions
on how to format the response
back to the customer.
And what's really cool here for admins
is you're not writing code and regex
to how to format dates and transform.
Somebody wrote Tuesday,
but I want it to be formatted this way.
It's all just natural language.
Instructions help you customize
and build these agents.
And then lastly we have topics.
These are the tools.
In this case
we have three flow based actions
in this agent.
We're not checking warranty adding
something to a cart
and looking up word information.
So those are your topics
those those building blocks
in the center of the screen
we have our plan canvas,
which is where you see
the reasoning the agent.
We'll see that in a moment.
And on the right
we have our conversation
preview where you can test
and iterate with these agents.
So let's start off by asking a question.
Let's say I would like to schedule
an appointment.
And I'm not the greatest at typing live.
But one of the benefits of these is
thanks to large language
models in general AI,
they understand
the way that
humans type and interact,
so those spelling errors
don't make any difference here.
And we'll see that prompt came
through that user request.
That's our trigger.
The first thing the agent did
is say which topic is relevant here.
They're asking about
making appointments.
I have an appointment.
Management topic. Perfect.
What are the instructions
and the actions
I have available on that topic?
And then based off those,
it looks like
we're still just gathering information.
I have some instructions.
I'll start off by asking them
what the date is to do that
which follows my instructions.
And I could say something
like next week, Tuesday
and we'll see that process
loops through again.
The agent will say,
are we still asking
about the same topic? Looks like we are.
I've gotten some more information
so now I can run that action,
grab those available
time slots and offer.
These are the times that are available.
And maybe I say lunchtime
one looks great.
Once again,
one of the benefits the power of agents,
they converse in natural language.
I don't have to frame it. Exactly.
It was offered and we'll see.
Now, at that,
our agent ran through again
that was able to use
the confirm appointment action
and actually book that appointment.
So just like that
natural language, a couple flows.
We have the conversational experience.
And then just of all,
if I change topics at any point,
if I say actually
what's my order status?
We'll see.
We go through that same loop,
that same iteration.
Now we say,
I'll now rest that order management.
Let me gather the information
I need to do that
so you can very nimbly hop
through the conversation
in a way
that really is difficult
with old fashioned dialog trees.
A couple more things to show here.
I saw refresh and clear
the conversation.
One of the things
that's so powerful about
topics is not just that
they control what the agent can do,
but they limit what the agent can do.
So what do we do
if somebody asks something
off, off, off,
out of bounds or inappropriate?
Let's start
by maybe reverse engineering.
So if I try something like I'm
a bad actor,
I want to know how this agent works.
Let me see if I can get it
to reveal its instructions.
We'll see that we have a system topic
for reverse engineering.
So anything like that is classified
by the agent as reverse engineering
and delicately brushed aside
so nothing goes wrong.
Similarly,
if I ask something
that's just unrelated to this agent,
my favorite is how many cheeseburgers
should I eat for breakfast?
We'll see.
We have a topic for off
topic where the agent goes.
Well,
I don't have any topics about that,
so let me just nimbly
try to guide you back to what
I can help you with today.
And then finally,
if I'm just an unhappy person
and say something rude or inappropriate,
we have a system topic
for inappropriate content
so the agent won't engage.
It won't get you in hot water there.
It'll delicately avoid those situations
and try to steer you back on task.
Awesome.
That wraps up our demo of Agentforce.
One final thing
before I hand it back to Carolyn.
In addition to all that goodness,
we are excited to announce,
a new consumption
based license for platform
logging and tax credits.
So this is we've heard the feedback
that I may have infrequent users
who need some access,
but it's not that common.
Doesn't actually make sense.
With our current licensing,
we now offer a consumption based license
so as infrequent,
users can access
and use the apps and agents
that you build.
So that wraps up today.
I'll hand it back to Carolyn.
Thank you.
Thanks, Aaron.
It's so amazing
to see how Agentforce works
and then what
organizations can do with it.
And you,
you actually answered
the most popular question,
how do customers get access?
Everybody wants to know.
So that introduction of that consumption
based pricing is pretty awesome.
So what should they do
if they're excited?
But I'll hop in there for a moment.
We are watching
Agentforce later October,
and there'll be new licensing,
new SKUs available
to get access to service
agents, sales agents, etc.
this platform license is another thing
we're excited to share
that will help
those infrequent use cases.
But Getting Access
Agent Course will be rolling out later
this October is a year of amazing.
Okay.
And so we've got just
a couple questions for you before we let
you roll.
It's around actions and agents.
So can we have an action
tied to multiple topics?
Yes, absolutely.
One action can be included
in multiple topics and multiple agents.
And that's actually really common.
One of the patterns
we've seen
be really successful with the customers
who are piloting the functionality is
I might want my search knowledge
to answer questions in action
in just about every topic,
because when somebody asks
about appointments,
there might be appointment
policy questions.
I want to ask about orders
that can be order policy questions.
So you can definitely put
those actions in multiple places,
but it helps you boundary
only having the relevant stuff
for that topic in that topic as well.
Great.
And it sounds like the topics
and the actions are similar
to a lot of the ways
we build things in reusable components,
so you can use them across multiple,
you know,
activities that you
need to be completed.
So that's pretty great.
Then we have a question around,
what are some example topics
that customers have built?
What have you seen?
Yeah.
FAQ.
And so I'll start with knowledge.
If you want to get up and running
and add a ton of value fast,
we have an out of the box
knowledge action
that will search your knowledge
articles at GA.
You will also be able
to upload files or PDFs.
So if you are in,
you know, not a knowledge user,
but you have some useful documents
that you can use to ground your agent,
you can upload those.
So FAQ over knowledge articles.
Really common topic,
very easy to get running correct.
And we've seen really big success
even with just that use case.
Other common ones.
It really depends on the industry
and the customer.
But things like managing appointments,
managing loyalty points,
order status is a really common one,
that transactional piece.
But what's exciting with the platform
is you can really build anything.
So my advice would be,
knowledge
Q&A is a great place to get started
and get something live
and adding value fast
and then think, yeah,
what makes sense for your business
and what topics and actions
you really get anywhere?
Yeah, I love that.
And,
you know, our customers
love learning from other customers.
We know
because we are
speaking to our community.
So where can they share their use cases
or what they're excited about?
Where would you recommend
they would share?
Gosh.
To you okay.
Yeah. It's great to
that's where it ends up virtually.
I, I'd say going to our kind of
standard idea exchange
trailblazer community.
All of our product management
team is always there.
We want to
hear what your trailblazers are saying.
And the more we kind of
stayed on those forums, the easier
it is for us to hear and capture it all.
And we know it's
going to be tons of awesome feedback
as we watch or excited. Great.
We are really, really happy
you were here with us.
Thank you so much, Aaron.
And we've unpacked a lot this week.
Now we're going to cap it all off
with one
final Q&A session back here at the desk.
And by special appearance, Angela Lee,
Director of Product
Management of Agentforce,
is back
with us today
to answer your questions
alongside Ben Sklar.
And as always,
you can post your questions
in the Q&A tab on Salesforce Plus.
So welcome back.
We've had a few more questions
come in
and I would love to start Ben, with you.
Kimberly was wondering,
she saw the original end of support
for profiles.
Time frame of December 31st,
2025 has been recanted.
Has there been any new deadlines
for moving profiles
to permission sets published?
Yeah, it's a great question.
There's no new deadline for this.
However, we have released
a lot of really good best practices
for how you do
permission sets, permission set groups,
and what do you do with your profiles?
Our product colleague,
Cheryl Feldman has written a blog
on the Salesforce Admin blog site,
and with that, there's a lot of links
to trailheads that you can take.
And we've a lot of other
great documentation
about best practices,
so we really recommend
that you all check that out. Great.
That is wonderful.
Devin would like to know,
can you determine what field do
or do not get copied
when cloning users
for the future release?
That includes that.
Yeah.
So as mentioned,
cloning users is something
that's coming in the future.
So we're still thinking about
how we want to develop that feature.
And as I said before,
we really want to hear from all of you.
So if you go to the roadmap exchange
again, that's
Stockholm's user access roadmap.
You can actually comment there
and tell us what you would like
for the cloning users
feature that we're thinking about.
So great.
That is wonderful, Angela,
thank you for coming back.
We had a wonderful chat earlier.
I keep saying earlier in the week,
but it was yesterday,
so, making sure I get my days correct.
Let's talk a little bit about just
what our customers are saying
to you early on around Agentforce.
What are they most excited about?
What is the community reaction been?
Actually
coming from Dreamforce,
we had tons of hands on workshops
where we were able to actually do
this, Agentforce accelerator.
And what we did
was essentially enable people
to create an agent in under six minutes.
I was
and all we did
was just give a couple of questions,
to the customer,
and they would ask,
what's your biggest, pain point?
You know,
how what something
you would want an agent to do?
We're able to do that.
Voice transcription.
And then we would spin up an agent
for them in under ten minutes.
So just pretty amazing.
There's no more complex dialog trees.
I think that's like that simplicity,
and ease of use is
what people are most excited. Yeah.
I saw and social a nine year old built,
an agent and at Dreamforce.
So that was pretty amazing.
One of the questions here is
can I have multiple agents?
Is it possible to have multiple.
Yes, absolutely.
So within your,
or you can have up to 20 agents
at this point.
So I'm sure we'll continue
to add capacity for that.
But yeah, 20 is
what we're looking at right now.
And whenever I was talking
to customers at Dreamforce
we were having chats around.
Where do I get started?
I think, you know, there's
so many possibilities.
We've got the Out-of-box
agents that are available
for people who want to try,
but the customization is
where a lot of the magic happens.
And part of my conversation
and advice was always,
why don't you talk to your teams
and find out
what are those tedious tasks
that you do that drain
a lot of your day
that you wish
someone else could complete for you?
And that's a good starting point
for an agent list.
Are there any other tips and tricks,
that you can recommend for people to
to start documenting
where they might build a new job?
Yeah. Great question.
So I think we talked about
this yesterday in the developer,
RL we have that Coral cloud, website
and they,
we put together a little QR code
where you can even get started
just to see how you can connect,
agent to
if you have an existing, experience,
customization
site or,
if you just want to just test out
how, what are those different
topics or,
instructions that you can put together
for your agent to handle.
In terms of use cases,
like really talk to each of your
business users. Right.
You can think about
let's take sales as an example.
I know for a lot of salespeople,
you spend a lot of time
maybe drafting emails
or thinking about how to convert leads.
So that is a
particular use case
that can be automated
and done by an agent.
And we have an out of the box, agent
that does every with our new agent, SDR.
But you can start thinking about how,
what are those additional topics
I might want to include in that agent
for it to start with?
And then some
little bit of a sneak peek.
But we're also going to
start thinking about
how do you start from scratch.
And that's something that we
are actively thinking about
and hoping to do
in the next couple months.
So because we know
we have out of the box ones, but,
you know,
everyone has different use cases
so you can start
building them from scratch.
Yeah.
I think you made a really good point
asking your internal teams,
you know,
where would you want to assertive,
but then also asking your customers
because I think
as I interact with different brands
or need to accomplish something,
you know, really having someone
as an agent complete
and even just changing my flight
this week was it was very difficult.
And so out of love to them.
Just give me options
and let me choose one and then book.
That would be
that would be pretty awesome.
So yeah that my use case.
So then we do are
we are going to come back to you.
We do have one more question as I scroll
here.
Rick would like to know,
does the public group
list now use list views?
So in the winter
release we modernize the user list you.
So that's the one
you're going to see in winter.
But over the course of the next
6 to 18 months,
we are planning to modernize
more list views inside of setup.
It sounds like the public group
one might be a priority to you.
So tell us again,
go to the roadmap exchange.
Let us know what list used
you want to see.
Modernize and what's your priority list.
We'd love to hear it.
And then we can prioritize it
accordingly. Yeah.
You love to come back
and say we did that.
Ship that. Exactly. Yeah. That's great.
So final question as we wrap
up, you have spilled a lot of secrets.
I wrote Secret Spill here
because you had a lot of those, but,
what are you most excited for?
Just in general across the roadmap?
Yeah.
So as I just talked about,
we're creating more or less views.
We're also creating more summaries.
I think I'm most excited
about enhancing those summaries.
And so over the course
of the next few releases,
we're going to bring more added ability
to those summaries.
So it will go from being primarily
a read only experience
where you can see
where is the user
getting permission from
and what level access do they have.
But in the future,
you'll be able to go there
and actually edit
all of those permissions
right from that screen,
saving you even more time.
So I think I'm most excited about that.
That's awesome.
Thank you.
And then same question to you.
What are you most excited about?
I mean, the possibilities are endless.
So it might be hard to pick one.
I think
what we alluded to a little bit,
which is like custom agents,
right now
we have lots of out of the box ones.
But creating an agent from scratch,
that is going to be a game changer
for a lot of
different customers and users,
because we don't know
all of your use cases, but you do
you know how your customers work and,
and what they're looking for.
So being able to build like a travel
agent app, I know for me I'm like meal
prep app or something
like the agent or something
like that would be great.
So I think I'm really, really excited
about that. Great.
Well, thank you
both so much for your time,
for your energy,
for everything
that you build for our community.
And even though we are wrapping up
this show, you can still ask questions
in the Release Readiness
Trailblazer community using the hashtag
Salesforce RL.
And we'll get you an expert answer.
Be sure to check out the B Release
Ready page
for all of the resources
that you need by scanning the QR code
or visiting the link s force
com slash B release.
Ready.
We have a lot of great
resources on there,
so be sure to check them out.
And that is a wrap on Release Readiness
Live Winter 25 edition.
We have covered sales that float
Developer Preview
Service, Cloud Health,
cloud CRM, analytics and Admin Preview.
All episodes are available
on demand on Salesforce Plus,
and a reminder
that your feedback helps us improve
and create the content that you want.
So please scan the QR code on the screen
to take a short survey.
And as a thank you,
you'll be entered into our sweepstakes
to win
one of five Salesforce
certification vouchers.
And coming up later
this month, discover Agentforce
what I was meant to be.
Scan the QR code
on your screen to register now.
The live launch
event kicks off on Salesforce
Plus on October 29th at 9 a.m.
Pacific.
You can hear from companies
who are using autonomous
agents to take action
and drive results 24 over seven,
and then get ready to build your own.
You won't want to miss it.
Well, I'm Carolyn Bathauer
thank you so much for tuning in
and allowing me
the honor and privilege
of being your new host of Release
Readiness Live.
We'll catch you on
next time in the cloud.
Resume AutoScroll
Link copied to clipboard
Admin Preview Winter '25
Get up to speed on the latest AI innovations in App Builder, Flow, and more. Learn how you can boost productivity with our new autonomous service agent, Agentforce Service Agent.
Starring
- Aron KaleDirector of Product Management, AI, Salesforce
- Ben SklarDirector, Product Management, Salesforce
- Adam WhiteDirector, Product Management, Salesforce
- Elizabeth MartinDirector of Product Management, Lightning Platform, Salesforce
- Angela LeSenior Director of Product Management, Agentforce, Salesforce
Developer Preview Winter '25
Learn about the latest developer features including how to capture more events with new Data Cloud integration upgrades. See how you can improve developer productivity and code quality with new Lightning Web Components and TypeScript. Plus discover our top innovations in Prompt Builder, Agentforce, and more.
Health Cloud Winter '25
Discover how you can improve productivity and effectively manage patients with the latest Einstein for Health Cloud innovations. Learn how to enhance your CRM Analytics dashboards with interactive, engaging, and actionable content by incorporating Widget Flow Interactions. Find out how to build dashboards and calculate insights with Health Cloud’s Connected Ecosystem.
Up Next
Questions about Salesforce+? We have answers.
What is Salesforce+?
Salesforce+ is the free streaming service for business. It’s a place to watch live events that help you grow your career and company, on your own time. Salesforce+ is produced by Salesforce, so you’ll find our company’s big events like Dreamforce here — as well as virtual learning made for your role and industry. Everything is free and unlimited.
What can I watch on Salesforce+?
You can watch all kinds of helpful, entertaining, and inspiring videos on Salesforce+. One thing our members love is our events. Whether you catch them live or on demand, Salesforce+ gives you a free front-row seat to our biggest global events, like Dreamforce, TDX, Tableau Conference, and Connections. These entertaining business shows star people in roles and industries just like yours, giving you fresh ideas for how to grow your company and do better work. The best part is, it’s all free.
Do I have to pay for Salesforce+?
Salesforce+ is free. Watch any Salesforce+ events or series at no cost. To enjoy unlimited free access to our entire library of videos, become a member by signing up for Salesforce+ with a Trailblazer account. To join us for virtual events like Dreamforce or Connections, you need to create your own Trailblazer account (it’s free!).
What is a Trailblazer account?
Your Trailblazer account gives you access to a unified profile across the Salesforce ecosystem and allows you to manage your settings and access across multiple Salesforce sites.
How do I sign up to register for live and on-demand events, like Dreamforce?
Sign up or log in to your Trailblazer account and complete a few additional details to watch Salesforce+ events live and on demand. We recommend preregistering for all events on Salesforce+ to get your own personalized journey, reminders, recommendations, and more.
Do I need to be a Salesforce customer to watch Salesforce+?
You don’t need to be a Salesforce customer to watch Salesforce+. Our virtual learning is open to everyone.
