True to the Core at Dreamforce '24

 Auto-transcribed on Thursday, September 19, 2024.media and text playback available on this page: https://aliceapp.ai/recordings/xc0LaAPn3TS6edUKRjFbt7sCg1mHpuWZ

Key 	Value 	
Words: 	11,211 	
Duration: 	01:01:26 	
Recorded on: 	Unknown date 	
Uploaded on: 	2024-09-19 18:33:33 UTC 	
Last update: 	 	
At: 	Unknown location 	
Using: 	Uploaded to aliceapp.ai 	

Speakers:

 Speaker A - 56.73%

 Speaker B - 13.5%

 Speaker C - 29.77%

Notes:

- All right, welcome, everybody. If you didn't know it was true to the core and you're in the wrong spot, you're welcome to leave. And it's really to hear from you what we haven't done, and basically to shame us.- How do I get the new UI enabled for existing orgs? We're also getting ready to roll this out to existing customers. To assess your code, find those customizations that might need a little bit of tweaking. And then you can get it ready in a sandbox environment before you roll it out to your users.- For existing customers, we are targeting summer of 25. Come, um, visit our spot in platform park and you can see both the UI in action, but also how to get slds two ready.- Salesforce has a lot of products and the products are somewhat built in silos. Can we look at shifting funding from building stuff in silo of customer 360 apps, build them for platforms so that all teams can use them?- William: We want to root out duplicative work. One of our biggest investments besides the AI focus with Agentforce is what we call more core. The idea is to move from individual clouds to more and more people going with the suite. In three years, every customer will be moving to the multi cloud suite.- Thank you. If you want to come one on one, give us questions. Enjoy the rest of Dreamforce. Thank you for being true to the core.

[00:00:09]  Speaker A 
All right, welcome, everybody. You know, uh, maybe one year we'll have a really cool stage that rotates as we're talking to you, but unfortunately we're only facing one direction. I, uh, am the voice of God today. There is no voice of goddess. Uh, this is true to the core. If you didn't know it was true to the core and you're in the wrong spot, you're welcome to leave. But if you came for true to the core, uh, that's what we're here for. And it's really to hear from you what we haven't done, uh, and basically to shame us and all the things that we should have done that would have been good for everyone, uh, and for you to give us that feedback. We have an incredible cast of characters here which are leaders of product and technology. We also have some incredible leaders of product and technology, I think. Where is everybody? Over here. Yeah. So, uh, everybody wants to be here to hear from you. Uh, and also I don't know the answers to most of the questions, so I need people to help me. Uh, so, uh, with that, I think. Do we have some opening slides that we're going through, David?

[00:01:18]  Speaker B 
We do.

[00:01:19]  Speaker A 
Can I hand it to you?

[00:01:20]  Speaker B 
You may.

[00:01:21]  Speaker A 
All right. Take it away. David Schmeier, our president of product and I chief product officer, the everything. Is that what I do, the OG? What do you do?

[00:01:29]  Speaker B 
Thank you, Parker.

[00:01:30]  Speaker A 
Yeah, thank you.

[00:01:32]  Speaker B 
Hi, everybody. It is great to be here. And, uh, couldn't be more excited about this. Dreamforce. We've been getting incredible feedback and, uh, I've been building software for three decades and the best product people, all these amazing product managers are the best listeners. And so that's why we're here. We want to listen to you, we want to learn from you. Uh, and hopefully you've seen the pace of innovation at Salesforce, which has been an innovator for 25 years, has really picked up and so we are innovating at a scale at an unprecedented rate. So I couldn't be more proud of our product and engineering teams. Um, having said that, as Parker said, we're here to talk about what we haven't done, but we're really proud of this platform approach to agent force. We do think that humans and agents working together is the future. And, uh, it's hard to believe, but we brought, uh, 5200 customers live on Agentforce in their sandboxes in the first two days of Dreamforce.

[00:02:36]  Speaker A 
How many of you gone to that section and tried it out? Yeah, I'm going right after this session. I'm gonna go learn how to do it myself, I'm pretty sure.

[00:02:45]  Speaker B 
I don't know if there's a leaderboard in this, but I think that's the most agents in a single sitting in human history. Uh, so it is kind of, um, because agents are new, so the bar is low. Uh, but still, we're very, very proud of that. And, uh, we have to choose when we come into Dreamforce, like what's the high level message? And agent force was what we picked. But there's a lot of other cool things like Salesforce foundations, which I'm really excited about, which hopefully this community is really excited about that. Uh, and the other thing that we've really taken seriously in the last four years is doing more based on what you vote on. And so we really take that seriously. Yeah, you can clap for that. Ah. And the other thing we've really taken seriously is being more transparent about our roadmap. There was never a, uh.

[00:03:39]  Speaker A 
I'm really excited about this, David, because I think they asked for this like two or three years ago.

[00:03:43]  Speaker B 
Yeah, we finally.

[00:03:44]  Speaker A 
So we're very responsive and it's great that we finally got it.

[00:03:47]  Speaker B 
Yeah. And a couple years later, here it is. But now you can see these roadmaps online and you can share information back and forth and chat with the product managers. And our idea is to show you what we're going to do before we do it. Uh, we all do something called three release Roadmap summit, where we look at the next three releases. So that's what we'll do. We'll congratulate our team when we ship the, uh, October release for a day, and then we'll get right back to work on the next one. And that's how it works in software. But this is really cool. I hope you like it. We'd love to get your feedback on it. And we also want to do more roadmap previews and webinars where we sit down and walk through it and answer your questions interactively. So again, very excited about it. It was a great idea to do this. And, uh, better late than never, Parker. And then this just shows you our commitment to this forum here to true to the core. And we really do. All kidding aside, we like to have fun in the suffer business, but we take your votes and your ideas seriously. So our points delivered are up 40% year over year. Yeah.

[00:04:56]  Speaker A 
Uh.

[00:05:00]  Speaker B 
Our ideas delivered are up 30% year over year. And our ideas updated by our product managers are up 35% year over year. So we're really excited about it. So keep those cards and letters coming and join our truth of force community. If you scan the, uh, the barcode there, uh, and you can kind of get there, um, I think we're now going to turn it over to Kush.

[00:05:24]  Speaker A 
Ah.

[00:05:25]  Speaker B 
And I really want to, first of all, thank you, Kush and Alice and the platform team, which gets sort of the brunt of these ideas because I think what you're about to talk about is really some groundbreaking stuff. So, uh, take it away, Kush.

[00:05:39]  Speaker A 
Thanks, David. And it definitely takes a village, and that village is sitting all over here and streaming in. Um, first and foremost, it's really great to see everyone. Um, now, last year at Dreamforce, David and Parker made an investment of dedicated resources to work on. True to the course. So let's now touch on, uh, some of those returns of those investments. We'll start off with dynamic forms. Now, dynamic forms continues to get better. We continue to hear your feedback. We continue to act upon it. We've closed a ton of IDX points these last two releases. And most importantly, the adoption of dynamic forms is growing at a very healthy rate, which tells us that we're moving in the right direction. Next. Nobody wants dynamic forms. That's cool. All right, now, the modernization of setup, um, is definitely in full swing. Woo. Yeah, this is good. Thank you, Parker. Thank you. Uh, we have established the right API platform so that teams can build lightning UI in setup very quickly. And what this has done is that it's enabled the accelerated delivery of a number of key capabilities across user access management and reports and dashboards. Now, we've got a lot up our sleeve looking into the future, but the one that we're really excited about is bringing agentforce to setup next. We're really excited to share that. Local development for LWC is now available across sites Lightning and mobile. This is your number two ask, and we are confident that this will dramatically reduce your debug time and your time to value. What's just as exciting is we are working on your number one ask as well around state management and stay tuned for that to be released in the next, the, uh, next offering. We've heard your feedback around experience cloud and the problems you face with deploying it. Now, a year ago in summer, we had about 250 customer cases for this. This past summer it went down to zero. Now, we still have a lot of work ahead of us. We're going to continue to round the corners and we wanted you to know that we're going to keep an eye on this going forward as well. Next Lightning is now 26.2% faster. The engineering team has been working actively on this. They are moving every stone, leaving no stone unturned as we march our way towards our goal of 40% by the end of the next release. And we will not close a single IDX point on this until you tell us that it's actually really faster. Srini, do we put people on unstable releases? Because I see that there's stable releases there. That's the data collection. Data collection data collection data collection. All right, just checking. I'm thinking even I was looking at it and uh, now the migration of list views from aura to LWC is complete. We finally now have the right foundation to innovate upon. We've already delivered multicolumn, uh, sort for lists. Yeah, that said, this epic of multicolumn sorts is the number one, uh, on IDX. And that epic isn't complete until we solve related lists. And that is expected in our spring release. So again, lots of innovation on this front.

[00:09:14]  Speaker C 
All right, and from there, um, Kush. Thank you. And we also have heard your feedback on the UI and the design of the UI yourself. If you've walked the floor, you've seen the new look and uh, in our keynotes you've seen it. And we're so proud to announce this is the new default out of the box style, uh, updated typography, color, clear hierarchies. But what's also happening is we have a full WCAG 2.1 aa accessibility out of the box that we're going to continue to maintain with this new system. But what's really exciting is there's flexibility under the hood now, so it looks new and there's a lot more you can do. Whereas there were two dimensions of styling you could do with our prior original lightning UI, there will now be eleven and more different types of customizations you can make to the styling of this UI. So that flexibility under the hood gives us a whole new level of branding, uh, and theming that you can do across your organizations.

[00:10:04]  Speaker A 
When you get to ten styles, you need that one little extra style.

[00:10:07]  Speaker C 
Dial it up to eleven.

[00:10:08]  Speaker A 
You can go to eleven.

[00:10:09]  Speaker C 
That's right, take it to eleven. Um, how's it going? We have over 7000 orgs on this new UI across starter, pro sales, eepe, and a lot more coming in the winter. And this coming year we're also testing this with customization, highly customized organizations, making sure that it's flowing with all the components that you have invested in. And it is fully compatible. Next slide, please. And a little peek at what slds two that's we're calling it is going to enable so that flexibility under the hood gives us the chance to do things like night mode. Um, and I knew there'd be a couple of applause. Advanced user preferences, high contrast. Those all can now come out of the box in addition to the flexibility that you can create in your own themes to make this look and feel the best it possible for your users. So if you want to learn more, take a quick scan of that code. Follow along as we're announcing the updates here. And again, a huge thanks to the team for all the work that's gone into these updates. Back to you, Parker.

[00:11:05]  Speaker A 
All right, well, now to the meat of it. I think we have two mics here. Uh, so please jump up while you're getting up there. Oh, there we go. All right, Charlie, you can't ask any questions, um, while you're waiting. Um, within Kush, within setup, we've emphasized the focus on user access. What plans come next after user access. Yeah, so our next plan is to look at templatizing, uh, a number of aspects of the UI. So we started with access summaries, list views. Now, how do we go beyond that? Our friends over on sales cloud have actually started an approach of sales go. There's a lot of goodness in that, that we want to templatize and offer to anyone building within setup. All right, great. And if you didn't notice, this line's longer than that line. But just saying. Okay, we'll start here, please. Well, first of all, thank you, as, uh, I always like to start with, um, especially, um, for me. I do a lot of presentations on design and UI, as Kat knows. So thank you for the design and UI updates, and thank you to the PM's who have been delivering, you know, setup fixes that result in fewer clicks for admins. So thank you. Thank you, thank you. I have a very specific question about the integration user. So if you're in an industries.org, you get a license and a PSL permission set license that go together. It's my understanding. I haven't tested this. I don't have a client on industries at the moment. Um, but if you, let's say you buy ten licenses and you have nine humans, and then you build one integration user and you got to give that your PSL so it can see the industry's objects. Your 10th human does not have a PSL available. And of course, if you need to buy one, your integration user is no longer free.

[00:12:47]  Speaker C 
That is a great question. Ah, wow.

[00:12:49]  Speaker A 
You can answer that. I don't think it's technology. I think it's policy. You just have to decide, we need to fix this.

[00:12:57]  Speaker C 
Parker, I said great question. Great answer. Um, so with the integration users, we've switched over to using permission sets, as you know, and we did that for security reasons. It's a modern way of doing it. We've run into some challenges, right? We've run into some challenges because permission sets have a secure by default setting. So by default, you don't have permission to anything, which is the right thing from security. But I know that people are like, well, you know, with the admin user.

[00:13:25]  Speaker A 
On how to implement it.

[00:13:26]  Speaker C 
Yeah, with the admin user, everything was on, and now it's all off. And so. But that we can work through. Um, there's also been a couple of issues where permission set licenses didn't have all of the right, um, capabilities in there. If you see any of those, let us know. File a bug. We're going to fix all of them because we absolutely want this to work for you. And I see Jay in the front row. So, Jay, is there anything else you want to add here to what we're doing? My mic. Here you go.

[00:13:53]  Speaker A 
Whoa. Yeah. Thank you for the feedback. I think Chris and team who have been focused on this, we've been hitting the tactical things to get this rolled out. I think with the specific PSL issue, uh, this is something we should be able to fix and just kind of not count against the licensing for the integration users. Thank you. Third answer is, we'll fix it. And while I'm at it, let me note marketing user checkbox, which I'm sure, Parker, you'd love to get rid of. Um, same problem. If you give one to an integration user, you don't have one for a human. All right. And just get your nomenclature right. It's not integration user, it's agent. Excuse me. So I'm Umair. I'm part of the analytics team, so I know the exact issue. Please tell me which particular user or the particular cloud you're looking at. We'll help fix it. All right, great. Now I'll go over here. Next question. Thank you. That's a great question.

[00:14:44]  Speaker C 
Hi. Longtime, uh, listener, first time caller. I've been in the ecosystem for almost 19 years now, wearing my lightning show.

[00:14:52]  Speaker A 
So what took you so long to ask a question?

[00:14:56]  Speaker C 
I'm really excited about the way the tool has grown and continues to grow. Thank you for that. Thank you for letting me make my living and support my lifestyle and my family by Salesforce. Customer support is a problem. And huh, I would do a lot of work. I'm a consultant. I do a lot of work with nonprofits. The choices now are signature, premier or basic support. Um, the problem with basic support is it takes days. With a nonprofit. They're usually running so slim they need something right now. But even if you pay for premier support, the first response is, oh, let us know that a time that we can get on the phone or on a zoom and talk about your problem. If you would just read what I wrote in my ticket, then we wouldn't have to get on a phone and talk about the problem.

[00:15:52]  Speaker A 
And some of us.

[00:15:55]  Speaker C 
And some of us.

[00:15:56]  Speaker A 
Ah, Jim Rose.

[00:15:59]  Speaker C 
Wow. If I'd have known I was gonna get this, I would have talked sooner. And some of us really want the answer in writing so that we know that we are understanding. We can read it, we can remember it because we're going 70 miles an hour.

[00:16:10]  Speaker A 
Thank you, agent Forrest. Yeah, thanks. Thanks for the question. Um, couple things there. Who are you? Oh, sorry Parker. I'm Jim Roth. I run the customer support team and trailhead and a few other things. But thanks for the question. We agree with you that basic standard support is too slow. We're working right now to turn on chat for standard support. It's not on there as well, so that'll get you sub 1 minute response times for standardization. Um, a big piece of that is what Parker said, which is agent force. So we're launching agent force on the help portal on October 11. And so that'll be a big piece as well. So we want really to address your question. We want to move from what we've traditionally had with um, asynchronous responses via the back and forth which caused this problem to synchronous responses using chat and agent force.

[00:16:58]  Speaker C 
Thank you.

[00:16:59]  Speaker A 
Ah, all right, great. Yes, please, Parker, thanks, uh, for having me here. Um, I don't know if I'm facing the right way. Actually, you are facing absolutely the right way. Thanks, Parker. Um, Mike, good to see you. As I told you last year, Salesforce, uh, is the most digitally accessible business enterprise application on the planet, bar none. So well done. However, however, um, it's clear that there are still a lot of issues that are hitting the releases and I think like uh, I don't know where the level of attention is being done at the design level. Right. So so many issues won't hit production if your accessibility practices are solid in design. Yeah. And then on the regression testing, we're, um, finding the bugs before your team is okay. That's not good. It's not good. So can we hire some people on your team? We're at your beck and call, Parker. We're at your beck and call. But accessibility, I mean, the European act of 2025 is about to go in. The Department of Justice just reinforced the Americans with Disabilities act. Accessibility is not a something to have. It is a have to have. Yeah, absolutely agree. Thank you for that, Mike, who runs all user experience for us.

[00:18:29]  Speaker C 
Hey, Mike. I am with you all the way. Um, one of the things I'm excited about in our design system update is being able to drive, especially as WCAG compliance and criteria are changing constantly. 2.2 is right around the corner, making sure we can update those centrally through that design system. So that's one piece, um, and then also things that we can bake into our tooling and testing before things go out the door. So we're making a huge investment both in what we do in Figma up front, making sure that everything is in the design stage forward is taking, reflow, resizing, not just the color contrast, but all of the kind of focus order pieces that are really critical. And then as we bring it out the door, also automated tooling that will do more testing and catching those bugs alongside what our teams are being trained up to do at a higher level. So it's top of mind, I'm with you.

[00:19:18]  Speaker A 
We're going to keep making progress explicitly. We used to make it as a definition of done for all the scrum teams. Now we also brought it higher up in the TNP v two mom for, uh, those of you know how we work. Like it's an explicit goal. So I think you'll see, uh, uh, just like we do. Availability, security, performance, accessibility has been, uh, uplifted. So I think you'll see a lot of changes happening, uh, with a lot more executive, uh, uh, sign offs and stuff like that. Yeah, that's really important because there's no finish line accessibility, just like with quality and trust overall. And we'll keep investing, keep calling us on it when we're not holding, uh, up our side of the bargain there. Thank you, Mike. So, asian force is amazing. Uh, everyone should go downstairs and try, uh, it out. It works. It's great when you get to present.

[00:20:10]  Speaker C 
Something, and it's working great from day one.

[00:20:13]  Speaker A 
I cannot wait to bring this new.

[00:20:15]  Speaker C 
Shiny toy to my clients.

[00:20:18]  Speaker A 
And my clients use industries. Clients use use industries. So financial services, cloud, public sector, nonprofit, cloud, they are investing a lot in.

[00:20:30]  Speaker C 
Omnistudio, so they are using data integration.

[00:20:33]  Speaker A 
Procedures to bring in data.

[00:20:36]  Speaker C 
They are building a lot on surveys.

[00:20:38]  Speaker A 
Studio omniscript. How can we bridge that to agentforce so that they don't have to rewrite.

[00:20:46]  Speaker C 
Everything again to make sure that everything is in flow? Thank you for building your own agent for us. And I agree, everyone should go to, um, downstairs to build your own agent force. That is a great suggestion. I'd love to partner with you on that. We are releasing over 100 industry specific agent actions this week along with the overall release. And it right now has flow, it has mulesoft, it has apex code. I'd love to partner with you on that other piece.

[00:21:16]  Speaker A 
Thank you very. Question. Yeah, uh, I'm Elan. I've been here before to bug you guys several times. Um, before I ask my question, I just want to say it's really, really nice to hear that people are using integration users. So that's awesome. Uh, and so integration users is a good example of when there was a best practice in how you guys want us to do stuff and it wasn't a really built to let us do that. And then you brought in integration users and that was fantastic. Um, along the same lines, when I use Salesforce and there's a best practice, I want to make sure I'm using a salesforce tool. At least I think there should be a salesforce tool to enable me to do that rather than going to a partner tool. So for like eight years, I used chain sets and I don't do that anymore because I use DevOps center. But DevOps center seems like nobody cares about it because in the one year that I've used it, I haven't seen a single new feature. And there are such glaringly obvious things that should be added that seem, from my perspective, simple. So I'm just curious, are we going to give more effort or more resources or see changes to DevOps center sometime soon?

[00:22:28]  Speaker C 
So I'm glad to hear that you're moving from change sets to source driven development. Um, I agree with you. It's a better way to develop. It's how we want to see both our low code and pro code users being able to do that. We are investing in DevOps center. Uh, we have a team on it. We're going to continue to invest in it this year. It went slower than we wanted expected. We were dealing with some issues that we were hearing from you. Um, and we were fixing things and making them work. We have a bunch of investments coming out I saw Dan and Chris Williams. Yeah. You want to just jump up to the mic and tell people about what's.

[00:23:04]  Speaker A 
Hey, how's it going? This isn't awkward at all. Uh, so uh, a uh, couple things that we launched. Uh, so BitBucket beta, uh, for sport. We had been hearing that this is one of the key blockers. People make an investment in a source code control provider. They want to make sure it's supported. We launched the beta now DevOps, uh, center testing. So first class support for testing. This is a pilot that's running now. We announced four partners and now we have quality gates. So anytime you're moving into production, you get to set the bar, much like the security folks that will check the hologram. You're doing that for production. You must meet this bar for this application. That can be unit tests or other, uh, coded UI tests, for example. And those all, uh, ship now. And obviously we have a lot more investments within there doing things like our code analysis tools as well. I see John Bello uh, over here as well. So uh, we are making investments. I'd love to learn more on where you see, and the other big one was the VC's integration. So uh, we were using GitHub events, which frankly was flaky. And so one of the things we allow for is auto sync and for you to sync, which was a challenge that we heard from you all. Cool. I mean, thank you for working on it. I do have specific things I can talk to you about. Yeah, yeah, that'd be great. So yes, we'd love to hear the specifics.

[00:24:19]  Speaker C 
Yes, thank you.

[00:24:20]  Speaker A 
Thank you. All right, just real quick, 1 second. Uh, how do I get the cat, how do I get the new UI enabled for existing orgs?

[00:24:32]  Speaker C 
Ah, great. Sorry, I threw out my own. I was so excited by that question, I threw out my own earpiece. Um, great question. So, uh, currently, you'll see we got some orgs that are um, set up, uh, by edition, and those are new customers. Now we're going to see more editions rolling out for new customers. Um, there's a little toggle we have is a starting point where we can toggle on and toggle off easily, um, inside of the UI section of setup. And that's just the starting point to be able to get it rolling, uh, out as an opt in. Right. Customers can try it out and if it's something you want to make a little more tinkering on, then you can also turn off and then turn it back on when you're ready. But as more additions come out. We're also getting ready to roll this out to existing customers and we just want to make sure all the right tooling's in place to make that as easy as possible. To assess your code, find those customizations that might need a little bit of tweaking. We're finding it's usually an incremental amount and then you can get it ready in a sandbox environment before you roll it out to your users. So you see that between now and, uh, Hilary, do you want to mention kind of the timeframe in which we're, um, bringing new additions forward for existing customers?

[00:25:36]  Speaker B 
Um, yeah.

[00:25:36]  Speaker C 
So for existing customers, we are targeting summer of 25 and I encourage everyone to also go to our session today at 130 where you're going to learn the context behind the new UI. And we're also going to talk a little bit about availability and how you can stay up to date on the latest when you can turn it on in your.

[00:25:53]  Speaker A 
Is there a place at Dreamforce that's dedicated to user experience and is there a place people can go and say, hey, I'd like to turn it on? And what do you think about this and how could I make this UI better?

[00:26:04]  Speaker C 
Come, um, visit our spot in platform park and you can see both the UI in action, but also how to get slds two ready. So you will be fully ready when it's time to.

[00:26:12]  Speaker A 
All right, so go to that session, go check it out. And platform park, you said?

[00:26:16]  Speaker C 
Yes.

[00:26:17]  Speaker A 
Okay, platform park. Good. Next. So there's been a big focus on unifying data. Are those questions on your shirt, by the way? No, this is all the setups. It's not actually. There's more that aren't listed, including setup, setup and admin setup for admins to use. Um, I figured we needed to show all the setups. Have you tried out the agent that will set up agents? Well, that's agent setup, but that's not listed yet because it may just be an agent doing it for you. We'll see. I don't know. Uh, so there's been a big focus on unifying your data. However, Salesforce has a lot of products and the products are somewhat built in silos. There's the customer 360 apps team like sales, cloud service, cloud, all of the different industries, all these different clouds. Then there's the platform funding. Seems like it's gone to what clouds bring in revenue. So sales, cloud service, cloud, bring in a lot of revenue. Platform over here doesn't bring in direct revenue but supports all of these. So what happens is the customer 360 app. Teams get funding so then they build new stuff which is locked in their silo of a sales cloud or service cloud or whatever team they're on. And then platform doesn't get it built. But then say service cloud has document generation to support FSL. Now sales cloud might want to have it, but now service cloud has no incentive to make it available. Can we look at shifting funding from building stuff in silos of customer 360 apps, build them for platforms so that all the teams can use them and really look at maximizing number one shareholder value and also reducing duplicate work of why would two teams build the same thing? Examples document generation another one, feature discovery. We have my service journey or my Salesforce journey which is built by service cloud. We have sales cloud go which is the new sales cloud setup. So those single solo admin can use sales cloud setup, service setup, all the setups for one person. It doesn't make sense. I blame David. I think you're absolutely, do you work at Salesforce by the way? No, I'm thinking did my chat GPT m therapy session leak? Yeah. I mean number one platform does drive revenue so it's want to make sure you understand that. And I think uh, the woman beside me would probably be the first to say yes, we need to fund it more. But David wanted to go first.

[00:28:42]  Speaker B 
By the way, welcome to my world. This is what I look at every day is what you're talking about. Um, and I'll give you some evidence of this. First of all, we want to root out duplicative work. So we used to have two revenue clouds, now we have one. We used to have three payment teams, now we have one. I'd love to get a list of all the duplicative things that you see because I'm constantly going around and merging teams and merging uh, charters so that we don't have that. We want one component for the entire suite. The second thing is, I think what you are saying is directionally correct as of three or four years ago. But there's more work than maybe, you know, that's going on to unify the suite. Now one of our biggest investments besides the AI focus with Agentforce is what we call more core. So bringing marketing cloud and commerce cloud onto the suite and because of that, that enabled Salesforce foundations. And so that was the whole, everything you're saying was the genesis behind foundations. So now you basically can get in a sandbox for free, the car with all the options and you can just try out everything. Sales cloud, marketing, cloud service cloud commerce, cloud data, cloud, AI, in the flow work, prompt builder and now agent force. And you can just play around with it. And if you decide you want to use it, then you can pick the edition you want. You can use consumption through the digital wallet. So the idea is to move from individual clouds to more and more people going with the suite. I believe in three years that's what every customer will be doing is moving to the multi cloud suite. And we want to make it as easy as possible to do that. So my goal, my dream is we have 2500 skus today, that there'll be one sku and it'll just be the integrated suite and everybody will go to it and use it. And then increasingly we'll go from users to users plus consumption and the consumption side. You pay for what you use, but I'd love to get a list from you of the specifics of like what you want to see more integrated, where you see the redundancies. But I think of myself as the chief redundancy officer, I'm going around and squashing those things. So these are like bugs, not features. So love to talk more about it.

[00:31:08]  Speaker A 
Yeah, and I'll just add as well. I love your question, by the way. Thank you. But we're also unifying the analytics suite as well. Instead of having four or five different stacks, one unified analytic solution. So 100% to what David said. And it's, again, really I appreciate the.

[00:31:22]  Speaker C 
Question and can I add to it too? Um, so thank you, Andrew, I love your pitch for more resources. That's awesome. Actually, um, I wasn't here three or four years ago. I've only been here for a year and a half. And since I've been here, we've increased the investment in the platform and we've increased it pretty dramatically. Uh, you saw there was a million IDX points. That was from investment. Thank you, David. Thank you Parker, for that. Um, specifically on idea exchange and being able to tackle those, but it's more than that. As we've approached AI, I think our first version of it was to look at, hey, what are some low hanging fruits that we can hit inside of sales, inside of service? But this big investment, what you're seeing with agent force here is all an investment in the fundamental underlying platform of AIH that we can use across all of our different clouds. But also you can use as part of custom application development, custom creation and leverage for whatever you want to build on the platform, because it's part of the core platform. And one of the other things I'm excited about, when you talk about, hey, we're unifying, we're pulling things into more core is an investment in devsecops across, across all of our clouds. And so you're seeing that and you're going to continue to see that with consistent developer abilities, you know. So William, we just launched, uh, data cloud sandboxes. Um, and we're bringing all of that in so that you can build across all of these different clouds. And that's all platform investment. So I'm excited to be here final three. But I like your shirt. Yeah, and your shirt's amazing. I like one. Um, one is the, the two biggest investments by far. We've made more core and agent force and the AI stack, all platform investments that benefit every cloud. Two is that we've taken a platform approach to agent force. And that's why it's so powerful, is that these agents can play multiple roles. They can seamlessly hand off with each other, they can seamlessly hand off to team members in different clouds. And then the third thing I'm really proud of is some of, you know, I used to leave the service cloud. I seek authentic in the audience. We invested a huge amount of resources in completing SCRT two and now we natively offer all of these digital channels, whether it's Apple business messaging or WhatsApp. We just acquired a voice company that is not going to be limited to service cloud that powers all of agent force.

[00:33:46]  Speaker A 
Thank you. All right, Ryan, good question. Uh, so for dashboards, we have a very restricted amount of color schemes that we can access. Is it possible to have a custom color scheme option so that we can reflect our own company branding guidelines for color choice? This seems like a no brainer. It is a no brainer. And I don't know where the question came from. It came from right here. Came from right there. It came from someone who was next in line to ask, um, a question. So in our keynote yesterday, uh, which was at 1230, if you missed it, it's now available online. We talked about the future and the unification of all of our analytics stacks, which I'm very excited about. It's called Tableau Einstein. It's built on the Salesforce core platform. And in the demo, at the end of the demo, we talked about things like rounded corners, things like the new UI, which we just talked about here. Also the fact that you can have custom color schemes and all the things that you want that you haven't had in tableau and other analytics products that we offer. So we're on that journey and very excited about it. Awesome. All right, great. Okay. Right over here. Thank you. Awesome. So first, thank you, uh, so much for taking these questions. And I'm going to preface this with thanks to the flow team for everything you've done, um, as a. I don't know if you want to clap after my question.

[00:35:05]  Speaker B 
Uh.

[00:35:05]  Speaker A 
Oh. So as a software engineer, um, on 15 years on Salesforce, um, the true culture of the, uh, development experience and the engineering rigor we've had around Apex since day one was test driven development. It was a requirement that you could not build code in production and that your code had to meet at least that 70%, um, testing guidelines. Right. So I'm glad we bring up testing gating today. We cannot build automated testing for flow. As flow continues to get more parity with Apex, including call outs, including agent force, we are introducing a plethora of regressions in our orgs that are affecting revenue and we have to resort to building Apex to test our flows, which is defeats the purpose of declarative development or buy expensive third party tools to run these. We have asked over and over, why don't we have any sort of testing on flow when it's been a core component of all pro code tools since day one? Now with Agent Force, we're going to see thousands of flows being introduced because each agent requires a flow, which means now we have potential regressions with an LLM model that we can't test as well. So as we look at the changing out change sets and getting quality where on the roadmap are automated tests and also the ability to within DevOps center be able to do code reviews without having to click 500 times in the canvas to figure out what's going on. All right, that was a great question. I'm going to add to it just to pile on. Can we address the data in flow debug emails? Unlike apex emails, flow error debug emails contain all data input into the flow. So emails containing Pii PCI are blasted out. So that sounds like a problem as well. There you go. Lots of questions. Do you want me to. Go ahead, Parham? Go ahead, Alex. All right, great questions. Uh, you're absolutely right. Testing automation is lagged in flow. We're going to work on it. One of the biggest disappointments for the flow team was we built flow tests, but we didn't make them API accessible. So you can't automate them, you can't put them into your CI CD systems, whatever. Those are not a big deal. But the priorities came in. We redirected the group. Uh, so we're doing our strategic planning right now for next year, and we're looking at testing automation. We're looking at automatic generation of tests because that's something that should be done. We're looking at creating permission that would allow you to be placed@the.org. level that would allow you to mandate that tests were every time a flow went into production, that it had tests. So you could use that if you chose to. Uh, and we're also doing a lot of investment into the debug and error management space in general. Uh, so, um, I'd like to, afterwards, I'd like to get your contact information because we're doing a fresh gathering of information, fresh gathering of info on what exactly do we need to do to make flow more enterprise ready, to make it more robust, make it something that it departments will love and bless and feel that it makes their jobs easier. Thanks. If I may just add, I mean, in addition to testing, I think governance is also a really important aspect of flow as we see more and more usage of flow to do drive mission critical processes in organizations. So we're also looking at how we can support governance as well as we take flow away from setup to a more of a business analyst tool where you can create processes. How do we make sure that before you roll something into production, it goes to the same sort of, you know, scrutiny that you would put any other code through as well? Can I follow up on that? So, business analysts and flows, now we're introducing engineering rigor into the business with no one, you know, with folks who don't understand DML loops, etcetera. That opens up a quite large area because already as a client and I'm seeing other customers, we have horrible, terrible flows out there that are borking environments because we don't apply the education around engineering rigor to low code tools. I mean, flow is code regardless of what happens, because you're still applying those same decision elements in loops, maps and sets. So we need more education on the development rigor around what flow actually does behind the scenes. Clearly agree. And that's why governance is really important in that aspect. Yeah. All right, great questions. Okay, over here. Hey, y'all, welcome back. Uh, thank you for what you all do. Really appreciate it. You build some really cool products that we love. But what I would say is sometimes we run into weird challenges. I have an enterprise account. It has less than 5gb of storage. And when I refresh my sandbox, it doesn't copy all of my data into my um, partial copy sandbox that has less than five gigs available, selectively copies, and now I have to spend days figuring out what things didn't copy and go get that data into my sandbox. So it'd be nice to not have selective copy on partial, but do a determination of when I make a template, use that template, and copy everything that can be copied.

[00:40:25]  Speaker C 
Yeah, that's great feedback. Um, we do copy everything if you do a full copy sandbox, but I understand that in a partial copy sandbox, um, it can be challenging to figure out what's getting copied. So, um, let's talk afterward. Um, I'll be right here and we can talk more about what we're doing in the roadmap there. Thank you.

[00:40:43]  Speaker A 
All right, Kush, when will multiselect pick lists be fixed? I didn't know they were broken. We don't have something on the roadmap for that just yet. What's broken? I have no idea myself. And so it'll be good to double click on that one.

[00:40:59]  Speaker C 
Yeah, there were multiple issues after the last one of these. Andrew wrote a blog post about it, which we published, um, to try to help people understand it. And there's now, this is the worst fix on the list. We have now a pop up when somebody creates a multiselect pick list to warn new admins about what the challenges are and try to redirect them. There's some other features you can use that will work better for the scenarios. We're, um, trying to redirect people, but, yeah, it's on the list. It's something that we.

[00:41:28]  Speaker A 
All right, well, it sounds like we need more feedback on that. Come up on the stage after. Yeah, right here. Hi, um, as a longtime, uh, developer, I was super excited back when you guys introduced scratch orgs and everything, right? And then I went and I joined.org.

[00:41:43]  Speaker B 
And I was super excited because that whole team was doing the manage package.

[00:41:46]  Speaker A 
Approach and you all started working on two GP and unlocked packages and stuff. And then fast forward to now coming.

[00:41:52]  Speaker B 
Back out from behind the curtain.

[00:41:54]  Speaker A 
It's been a number of years, so if this is an uninformed question, I apologize, but, um, what are we doing to make it easier for those enterprises to enter into the unlock package? Because to be fair, I inherited a six year that's got the tech debt of like 14 years. And getting to a modernized development process has proven to be difficult. For instance, I can't even create a scratch right now from our code base because the limits on what I can push with SFDX at the moment seem like very small. Um, I know we have some tools like, I think happy soup or something like that can help you find those dependencies. But anytime you reach out to somebody, the answer is, yeah, that's hard. So, yeah, it is. And so I'm just wondering, is there any additional work going on in that area to help the enterprise get to.

[00:42:43]  Speaker B 
The point where we can do the modern stuff?

[00:42:45]  Speaker A 
Cause I'm still very reliant on sandbox development, which gets very hard when you've got 1617 teams.

[00:42:51]  Speaker C 
So this is an active area of investment for us. We just launched scratch snapshots this summer. I'm hearing from a lot of our partners something we're telling is twelve times faster. It's 24 times faster. So we want to make this really work for you. One of the, we're working with some of our biggest customers right now and our biggest partners to look at the scale limits and how do we break down the packages into sizes that work and get underneath the limits. So actively working on this and would love to partner with you too, if you're pushing those limits. We also are building a tool to help companies upgrade from one GP packaging to two GP packaging. It's a two GP migration tool. Um, we're piloting that. And if you would like to be a part of that pilot as well, I would love to talk to you about, uh, how to get you onto two GP packaging. So thank you.

[00:43:39]  Speaker A 
And one little additional plug. I think some of these things will be easier for us if you migrate to hyperforce. I don't know if you're already on hyperspace, then we can try some special things and see if that solves the problem. So let's take it off. Yeah, I would love to do that. I would love, um, to talk to you to know more about this because we are continually investing both in unlocked packages and scratch arcs. I would love to know the specific set of, uh, challenges that you're running into so that we can bake that into our plan.

[00:44:07]  Speaker B 
How do I find you?

[00:44:08]  Speaker A 
Just like right after this, I'll just come back and everybody needs to introduce. Who are you? Oh, sorry. I'm Dilip Berkey. I'll connect with you.

[00:44:17]  Speaker C 
Dilip is the product manager for all of the scratch orgs and the sandboxes and all of that.

[00:44:21]  Speaker A 
So, yes, so I would definitely find out how to get in touch with you. All right, thank you. Good question. Love the hat. Okay. Right here, uh, it's my 8th true to the core, so I appreciate you all for everything that. Thanks for your dedication and keep coming back. I had a question for the three at the end. David, uh, Claire and Sereny. Um, I wanted to ask if you're satisfied with Salesforce's use of AI on its public facing digital properties. I feel that that's a nice softball question. Well, in 2024, I feel it's kind of ridiculous that we're posting 500 pages of release notes when we're talking about technology that summarizes this and gives us personal examples. And I find it kind of ridiculous that I can't get, I can't get code examples, I can't get code examples of how to use those new features that are personalized for my developers. Uh, sreeni. On the engineering side, I do feel like this latest release, the amount of staggered features is more than ever. And I think it's kind of ridiculous that you expect us to be magically checking to see when these features come available. Why don't I have a bot that tells me when these things are available? I just feel like some of the AI side of things is focused so much on the customers but we're not able to get our hands on this technology with our interactions. Can we blame marketing? Who's not on the stage or I'll.

[00:45:50]  Speaker B 
Start and I'll uh, let my colleagues chime in. Um, we're now embracing Salesforce on Salesforce as a core mission for every single one of our clouds and we think of ourselves as customer zero for every single one of these. So that was not true maybe a few years ago, but it is now.

[00:46:10]  Speaker A 
A few months ago too.

[00:46:11]  Speaker B 
Yeah, as of a few months ago this got on the v two, mom. And so you're going to see agent force in support with Jim's organization. You're going to see digital sdrs in sales. You're going to see this in marketing and signing up for the events. So we're going to use everything we've got. So if you have ideas on how we should use it, we'd love to hear them. Uh, but we're all in it. So we agree wholeheartedly and I think you'll see a drama a year from now. You're going to see a dramatic change.

[00:46:40]  Speaker A 
But I do think his point, I'm not sure we're focused as much as we should be on where he pointed, so. And by the way, just go to the Salesforce on Salesforce zone. It's an awesome area. Pick on them if you don't like what we're doing. But we're trying to be better about using our own technology. There's some really good examples.

[00:46:57]  Speaker C 
Sorry, I couldn't agree more with you. I think we've had some early wins. If you haven't tried it, you should engage with Ask Astro, which is built on Agentforce. It's part of the Dreamforce mobile app. And so that's our first foray. But to be completely honest, we're going through the same journey that many enterprises are that have been using Salesforce for a long time, which we have. We have different instances and we're deploying data cloud to be able to make sure that we get our data ducks in a row so that we can enable those use cases that you're talking about. Jim, uh, Roth, who you heard from earlier, he leads our customer success and customer support. We're partnered very closely to address those data gaps. We've accelerated that roadmap so that we can deploy exactly what you're talking about in the coming months. And if you have specifics, I'd love for you to come find me after the session because I want to write them down so that we are addressing that as part of our requirements.

[00:47:51]  Speaker A 
And I'll just add one more that the help and portal. Uh, what you're saying, this is definitely like David said, it's going to change very fast. We'll fix all of everything you're saying. It's in our list. And then, uh, maybe in three months or four months, you should see a big difference. Great question.

[00:48:13]  Speaker C 
Hi, my name is Cassandra. I am a, uh, salesforce admin with Aristotle. And, um, this is my third time asking questions and I think some of you know what I'm asking for. And so the first one is the night mode. Thank you. That looks amazing. And thank you for listening to the community that we really want to have parity with other web applications that are out there. So, uh, can we please have it next release and on the flow builder first? We're working really fast, really hard, and I remember you asking this question at my very first through the course. So thank you for coming back. It stuck with us and absolutely continue to give us that feedback. Thank you. And, um, so there are two other things that's about the old stuff. One is layouts. So we want to move our users to permission sets and permission set groups.

[00:49:03]  Speaker A 
That's great.

[00:49:04]  Speaker C 
But layouts are still tied to profiles, so I don't know how we're going.

[00:49:11]  Speaker A 
To move those users.

[00:49:13]  Speaker C 
And we don't have a conditional way to give certain layouts to people who are on specific uh, permission set. So that's something that would, uh, be nice if we can get it worked with.

[00:49:26]  Speaker A 
Um, should I finally, Cheryl gets to answer a question? Yeah. Hi, my name is Cheryl Feldman. I cover, uh, all of the user access features in product. Um, so when we think about profiles, we think of them as very much your one to one between user and a setting. Um, your permission sets and permission set.

[00:49:51]  Speaker C 
Groups really handle your many to many.

[00:49:53]  Speaker A 
We've always envisioned that page layouts would stay on profiles, but what we've been hearing lately, it's been causing you to have a proliferation of profiles. What I would love to do is have a chat with you, post streamforce, and understand more of your use cases. I think we may need to rethink this a little bit, but then I think about if we put them in permission sets and permission set groups, which one, if you have many, like which one would we show you? So. But I would, I would love to take your feedback on your specific use case cases, but it's a good call out. Thank you.

[00:50:27]  Speaker C 
And just to build on that, I want to let all of our closest trailblazers in on a very exciting sneak peek that we are working on. And it's called, it's a partnership between Kat, myself, and Silvio from our research team. It's called generative canvas for lightning. And we're going to use, we are using generative AI to dynamically generate page layouts for specific users based on their role, their profile, and what they're working on in that present moment. We just released it in pilot on the app exchange. We would love you to participate in that pilot. And then we're partnering with Alice to take those learnings and bring it into production next year so that we can be much more dynamic and personalized in the layouts that we offer to our end users. That's interesting.

[00:51:13]  Speaker A 
Or even better, just live in slack and have the UI come to you.

[00:51:17]  Speaker C 
So many choices. And one last thing, and I think this is, I didn't want to hug the mic, but I really wanted to kind of talk about it and get it out of the way. So when you create an object, there is a way to all the way down at the end, there are a couple checkboxes, and one of them is notes and attachments. Why do we still have that? That's my question.

[00:51:42]  Speaker B 
Parker, did you put that in there?

[00:51:44]  Speaker A 
Yeah. I'm tired of removing that setup because Parker may be upset.

[00:51:49]  Speaker C 
Well, just to play devil's advice, do.

[00:51:51]  Speaker A 
You not want notes and attachments? You may get rid of it?

[00:51:55]  Speaker C 
Yeah, I mean, we're not using notes and attachments and lightning. That was a classic feature. And we have separate notes and files related lists now. So why do we still have notes and attachments whenever we create an object?

[00:52:08]  Speaker A 
That's a fair point. Replicative things. Where's the. We'll get that redress back there. We should fix that. Yeah, good point. Uh, I love that. Um, David, we'd love to see the plan to support multiorgs without the need to purchase duplicative licenses. Let it follow the user. If the user moves between orgs, Chris Billmeyer might be in the room. Might uh, be a chance to talk about base suite. So, uh, you want to talk about usage based pricing or flexibility that we want to do as we think about people moving between orgs? Sure.

[00:52:44]  Speaker B 
Yeah. One thing that we're very excited about that may not be intuitively obvious to everyone, is you can use data cloud to harmonize to similar systems. But if you can do that, you can certainly use it to connect different salesforce orgs. So I believe that we're going to see more and more customers. We already have a bunch doing it, and there's a new, um, uh, set of capabilities around this in the latest release of data cloud. So you might want the autonomy of five, uh, orgs, but you want to put it all together in the cloud.

[00:53:17]  Speaker A 
But they don't want to pay. I'm a user.

[00:53:20]  Speaker B 
No, I'm getting there. I heard that. Uh, so that's the first thing is there's a new way to handle this multi.org situation. Um, we've done a number of things in pricing. Like we did this in tableau, actually, with CRMA and tableau, where we didn't want people to have to pick and choose between which one do you need? So we have a universal license for that. So, uh, we don't have an off the shelf solution to that, but we're happy to work with you. We agree that, like, a user is a user and you shouldn't have to pay twice for users. So we agree with that.

[00:53:55]  Speaker A 
I think it's the spirit of what we've been trying to do to move to consumption based pricing, more transparency in our pricing. And so certainly if it's the same user moving around and the same amount of work, we should be charging you one set of fees, not multiple. Good question. Okay, where am I going next? I'm going over here. Thank you for that help. So this is a technical question around knowledge search. Uh, I've talked to several people. Um, so for knowledge articles. You can assign data categories, one or more data categories to knowledge article, but when our customers search for knowledge, they can't limit their search to those data categories and so they're searching for error messages or something like that, and it's returning a whole bunch of extra knowledge articles that are unrelated to what they need.

[00:54:47]  Speaker C 
Great question. Um, we have our knowledge expert from service cloud here, Deborah, so I'd love to talk to you afterwards. Um, you should be able to filter on data categories. Is there specific use cases? Let's talk about where you're finding that to happen. You really should be able to do that. Um, are you using it in the, can you explain a little bit more about where you're struggling with data categories filters?

[00:55:16]  Speaker A 
In our experience, um, customer site, when they do knowledge searches.

[00:55:22]  Speaker C 
Okay, so you're saying in your self service site. Yes, specifically. Okay, got it. Let's sync up afterwards. Good question. You're absolutely right about that. We should have data category filters there. Um, let's talk afterwards about that if you don't mind.

[00:55:37]  Speaker B 
That'd be great.

[00:55:37]  Speaker A 
Thank you.

[00:55:38]  Speaker C 
Thank you.

[00:55:38]  Speaker A 
Great question.

[00:55:39]  Speaker C 
Thank you. Oh yeah.

[00:55:41]  Speaker A 
So we definitely need to solve these data category filters in the knowledge area. But one of the other thing I wanted to make the plug is that, uh, in our tableau Einstein keynote yesterday, Nk showed how a lot of our customers are starting to use tableau. And within data cloud we've added this new capability for vector search where the vector search allows you, or hybrid search allows you to look at a lot of other data and a lot of the unstructured data as well, to look at knowledge articles and search them, match them with cases and other. So one area to look at is in addition to what we'll do in the platform, to maybe explore like how data cloud and tableau can help you in these things there as well. We're doing a huge amount of investment in unstructured in those two areas.

[00:56:25]  Speaker C 
That's right. And just a huge shout out to the partnership between the service cloud and platform teams. We started a journey two years ago to offer unified knowledge. We know that you don't have just have knowledge in Salesforce. You have many knowledge repositories across your company. So Deborah and her team have been working on that. That was just delivered a few months ago and it's a really powerful way to bring all of those knowledge sources together and then to mayor's point to be able to run rag and embeddings across all of those sources.

[00:56:54]  Speaker A 
Great. Over here, please. First of all, thanks for um, having this session and then all the leaders listening to us. Uh, I believe this is one of the most valuable session that we have in Dreamforce. Um, I have two questions related to hyperforce. Um, there are a lot of uh, hyperforce migration is happening, but in the recent past we are seeing multiple performance degrades, especially in hyperforce arcs. And we did not see these type of things in the first party data center. Uh, is there anything that is specifically happening with hyperforce or is there any attention paid to that? The additional question related to the same thing is uh, we are seeing some kind of issues related to the platform events and the hyperforce. The older architecture with which we developed the platform events integration, it's working fine in first party data center, but the same thing is not working in hyperforce. If there are multiple, uh, if there is a huge surge in the volume. Uh, is there anything that is happening? Uh, I'm curious, before we answer, have you, do you know about scale center or have you used. Yes, do you use that? Yeah, scale center, it's there. But I don't think scale center is capturing the platform event related one. So just so for everybody know, I think we have migrated, um, more than 6 million orgs, almost like we are, uh, 87% of our customers are already on hyperforce. Across the world we have migrated some of the biggest orgs, um, ah, immediately after migration we had an issue with platform events and the way we were syncing with aws and all, I think, but that I think is resolved. But if it's still there, I would like to know. There was um, one transient issue, uh, with Fileforce, uh, where we were still accessing because of the uh, time it takes to sync up the old um, files we had had, which we knew, and then we worked with uh, some of our uh, underlying partners and network partners to increase the bandwidth. My understanding is um, these two issues got resolved some back, but if you have a specific issue, I would like to know for your specific and resolve that. But I think so far my experience has been um, we have migrated thousands of hours, millions, hundreds of petabytes of data. Touch uh, would rarely do I see an issue, but uh, these two are, if you're still accessing, I would like to know. Great. So we have time for one last question. I apologize. Just want to comment on the scale center part of it. So in scale center, uh, we are planning to have either an investigation or an insight, just like we launched Apex guru, uh, so have uh, insights related to platform events as well. So uh, we have a lot of pilots coming. We would love you to participate and give us your feedback on that. Wonderful. Hello. Oh, there you go. Hi, I'm king. Uh, I'll make this short since we're pretty short on time. Uh, I'm so glad to see that night mode is really on the roadmap and it's getting that serious love and attention. I'm a big fan for personal preferences, but I think it's great for people who are light, uh, sensitive, too. So it's great for accessibility and all that. Uh, I just wanted to clarify that it's going to be applied to all the different types of Ui interfaces. So not just like end user in Salesforce, but flow, uh, builder, canvas, uh, promptbuilder, model builder and other salesforce affiliates. So like, uh, the mobile app, uh, and trailhead as well.

[01:00:25]  Speaker C 
I like your push towards the furthering of the roadmap. Thank you, King. Um, so we are focusing first on what's going to reach our end users. That is the clear set of the roadmap in the timeline that Hillary shared between now and the summer. But we are thinking together about builders. We know that that's where a lot of time is spent and where a lot of eyeballs are draining. So we want to focus on that as we start to figure out what the next stage of this roadmap is. So stay close. Have a session today at 245. We'll talk a little bit more about hall. This is rolling out if you want to come by and talk more.

[01:00:55]  Speaker A 
Thank you. Thank you. And, uh, unfortunately, we are out of time. Um, we didn't get a slack question, but I will say last year you asked rescheduled send and thread. We did ship that. So hopefully if you're a slack user, we have that. Um, and, um, with that, we will all be here after. If you want to come one on one, give us questions. Thank you very much for being at Dreamforce. Thank you for being true to the core. Enjoy the rest of Dreamforce.