Name: Your Ultimate Guide to the Top Salesforce Winter ‘26 Features
Uploaded: 2025-09-04T16:31:00.597Z
Duration: 1 h 1 min 24 s
Description: Your Ultimate Guide to the Top Salesforce Winter ‘26 Features

Transcript for "Your Ultimate Guide to the Top Salesforce Winter ‘26 Features": Beautiful. Alright. Welcome, everybody. I'm Peter Chittum, and this is the winter twenty six release preview from Salesforce, Ben. We are very pleased to have you here on the webinar today. And, yeah. Alright. We're already getting some people chatting to us. David Miller from Grand Rapids, Michigan. Awesome. Kinda right in the middle of Michigan, if I'm not mistaken. That's actually, that's Apex Hours, territory in there, isn't it? That's where, somewhere near where Amit lives. Cool. Let's move on to the next slide. Yes. So we are Salesforce, Ben. Everybody, I'm sure knows us from our amazing website with, some great content. But did you know there's also a newsletter? We have loads of great events just like this webinar, but we also have them in person. If you ever go to any Salesforce events, or sometimes for community conferences, we have some great in person experiences that we put together. We also have a YouTube channel. You should check that out. Make sure you go there, like, subscribe, click the bell, all those things. And we have a podcast that is on hiatus, but we are looking for, we have some ideas for how we can reboot that, so keep an eye on that. There we go. And with that, let's do some introductions. I'm joined by Tim. How are you, Peter? I'm doing great, Tim. That's good, man. That's good. That's what we like to hear. So Tim Combridge, now Tim, I just did a webinar with you, like, two weeks ago, and you had a different employer. Didn't you? That's right. That's right. This is my, first official, webinar event as a part of the Salesforce Ben team. It's very, very exciting. I'm stoked to be here. That is amazing. Tim, people cannot hear you for some reason, and I don't know why that is. Randall Jones just popped that up there. I can hear Tim. Maria can. Sasha can. Okay. So you're fine. On you go. Okay. Yeah. That's, that's, my first, outing as a as a Salesforce Ben representative. So, yeah, super stoked. Yeah. Yeah. Very, very pleased to have Tim join the team. And, again, my name is Peter Chittum. I lead the technical content team that Tim is on, as well as a few other of us folks. And, yeah, we're super stoked to have you here on the release webinar for winter twenty six. Brilliant. Thank you very much. Alright. Now, of course, these webinars happen because of our amazing sponsors. And, this time we're sponsored by Salesforce. Salesforce gives sales and service customers access to more of Salesforce and is now included with your existing Salesforce implementation. Salesforce has made it easier than ever to get started with the connected customer three sixty by building their foundational apps into your CRM at no additional cost, I might add. That's right. It's for free. Salesforce is a free add on. It gives Sales Cloud and Service Cloud customers on enterprise edition and up free access to Agent Force, sales, service, marketing, commerce, and data cloud. That's like all the clouds, isn't it? After activating foundations, you can leverage any one of the features shown on this slide. Use them to enhance your business or test proofs of concept with different Salesforce agents for free. Just to give you two quick examples, there is a new Salesforce for sales agent focused on lead generation, and there are marketing cloud capabilities, provided to your business free via foundations, of course. So, yeah, go and check that out and see what's available for you in the, foundation products. Wonderful. Thank you for that, Peter. Hey. Look. I'll, quickly introduce the agenda for today. So there's three key points that we wanted to talk about. Number one, we've all been talking about, security. It's been a big topic the last week or couple of weeks, I should say. So we're gonna quickly go over that, and then we're gonna dive straight into the top features that are coming in the winter twenty six release. It's another brilliant release. You'll you'll be, not shocked to hear that. So we're we're really excited to share those features with you and then go and give you a demonstration of some of those features and what they can do in your in in your org. Just a reminder, please ask questions as you go. So we got the chat over there. Don't hold your questions to the end. We we wanna try and tackle them as we go, if we can as well. And get involved too. It's always good to see the conversation, happening when the as the webinar goes on. Beautiful. Peter, I will hand over to you for the breach catch up. Yeah. That's right. Everybody I'm sure has been tracking what's been going on in the news with the security breach that has started. We were really tracking it about a month or six weeks ago at at first. So let's just go through a few things, to kinda catch us up where things are at. Again, these aren't winter twenty six things, but Salesforce has released some stuff that is available now. And so we felt since we're kind of doing an update on features in Salesforce, it'd be worth talking about one of these in particular. And that is on September 2, Salesforce launched new restrictions on apps that use the device OAuth flow. Now if you know OAuth, there are different kinds of flows that are about different ways of ensuring that you've authorized users to access a particular service or application. The device flow is one of these, but it has a particular vulnerability that seems to be one of the things that the hacking groups have been take have been taking advantage of. So as of today, as of actually earlier this week, device flow has been removed from data loader. And, in, in the winter twenty six release actually, device flow will be removed from the Salesforce CLI. In addition to that, oh, and actually, yeah. So take a look at the article there, prepare for connected app usage restrictions change. That's one that we wrote to catch up on, you know, what you need to be prepared for with these changes. Let's go to the next slide. Yeah. And we like I said, we have been doing a lot of coverage of this. There's some great questions. We'll try to get back to these, and we certainly encourage you to look into these breaches, as they are potentially impacting any Salesforce customer is what we're saying. But do tech check out the, Salesforce admins guides for auditing connected apps that has some good guidance on how to make sure the connected apps that are in your org are the right ones. And then, again, I talked about that help article prepared for connected app usage restricted restriction change. That's in the Salesforce help. It's a knowledge based article to understand how these changes are taking place. Alright. With that, let's continue on with winter twenty six. Good stuff. Thank you for that, Peter. Alright. So just a reminder, we are partway through. This is not a, hey. Winter twenty six is in your org now. Obviously, we're we're still in the earlier days. Salesforce has put out a, a timeline that sort of explains where we're at, where we're going, and what's left. We also have a an article on the Salesforce Ben website that goes into detail on the different steps and ways you can prepare as well. In fact, there's a handful of articles on the Salesforce Ben website talking about winter twenty six and being prepared and and, what you should be doing, as it rolls out. Just a reminder too that the we're talking about some of the key release notes today. There are some other products as well that have their own separate release notes or or separate release schedules as well to follow. So Data Cloud as well has a section in the release notes that's updated for their monthly releases. Salesforce CLI, Visual Studio Code plugins, and Heroku all update weekly and have their own change logs as well that you should keep, keep on top of to make sure you're not missing anything. Now just a reminder, what did you say before, Peter? Was the, the the man struggling with a heavy umbrella picture? I like that. Yeah. So this is a UK roadworks sign for people who aren't familiar with it. There's a lot of folks who don't live in The UK on this. I just chose to throw this in as the icon because there's a there's sort of a UK joke about this not being a worker with a shovel, but rather a man struggling with a very big umbrella. But, yeah. I like it. I like it. I'm never gonna be able to see it the same way. But yeah. Look. Ultimately, that's that's not what this is about. What we're here to talk about, basically, is that, winter twenty six is still in its very, very early days. So as you will be playing around in your preview org, in fact, if you have been playing around in your preview org already, you may have noticed that some features were missing or incomplete or some features I've noticed were there before and have been temporarily sort of pulled. And just a reminder as well, until GA date, Salesforce doesn't guarantee that any of these features will actually be released. You know, that it may be that they require a little bit more, a little bit more work before they're ready to go. So just remember, it's good to stay on top of it. It's good to test these things out, but nothing is sort of guaranteed. So just keep that in mind as well. Wonderful. Alright. Now, Winter twenty six, as I said, no doubt is a massive, massive release. We got heaps to talk about. We've only got I was gonna say an hour, but we're down to fifty minutes because I've been talking too much. So we're gonna break down the features into we'll start with admin, and then we'll go into some developer features or benefit developers, and then we'll go into domain. So we'll talk about some features that'll benefit you in sales, then service, and then, of course, marketing as well. Now we're not gonna talk about every single feature. Obviously, there's over you know, in the main release notes, there was over a thousand pages just in that. So we're gonna talk about some of the key ones that we think will be beneficial to you. So starting off, like I said, with admin. Action Hub, and just on, you know, features that were sort of, you know, partially pushed in and have since been upgraded, if you read my initial Salesforce flow features article, you would have noticed that Action Hub looked a little bit different to what it does in this slide. And Action Hub is one of the pieces that has come in and been upgraded since the sort of first winter twenty six injection. So this is what it looks like now. What the intended Action Hub is is it shows all the actions that are available to you or those that you have permission for. You can filter them by type. There's a searchable data table as well. And the Action Hub sits within the automation app. I've been a little bit sneaky here because I had a limit on how many things I was allowed to talk about, but the automation app now has its own special link in the setup menu. So if you're like me, which I'm I'm still you know, I go into setup, go to flows, and they go, oh, no. Wait. That's right. I'm supposed to go to the automation app, and then I go to the automation app. There's now a link in setup to send you to the automation app. So that's something I thought was probably worth mentioning as well. That's due to winter twenty six. There's a there's an interview, on I'm sorry. There's an article, that talks about an interview between, Salesforce Ben, Ben, and Adam White from Salesforce about why this exists and what this is for. Ultimately, this started, I don't wanna misquote the article, but it was ultimately started because of the agent force leverages actions and flows to to take action on your data. So having hub to see all of your actions, you can then click into each individual action and see where it's used as well. So this just provides you a really good way of being able to see and monitor the actions that are available inside of your org, where they're being used, etcetera. So flow debug. Man, flow debug, honestly, when this came to the previous release, the the the original, iteration of flow debug, I was I was stoked. Flow debug is or or previously has been sort of quite, you know, an arrow panel on the side of your page that made things a little bit difficult to work with. We saw in the previous release that you could now expand it to take I think it was up to 70% of your page, which gave you a lot more space to work with. It also lets you search. It lets you collapse different sections and put it in a card based view. But it was missing in screen flows, and I had some some some screen flows that, were were causing me some nightmares, and I was I was just like, oh, man. I can't wait for for winter twenty six. And finally, here it is, winter twenty six. I look on the right, and it's it's not there. Oh, interesting. They've moved it to the left. There's a reason for that. We'll talk about that later. But the biggest thing I wanted to talk about was, flow debug. The enhanced flow debug is now here for ScreenFlow as well. So there's a resizable panel, like I said, on the left hand side on the left hand side of the screen, and you get your card based debug details and additional features, which make debugging so much easier. Honestly, it's a massively different experience. Something else that we have, type ahead. So when you're when you're constructing a a list view and you wanna configure the columns inside of your list view, previously, you would have to scroll. If you're anything like me, like, I'll click on a a pick list or a drop down field or whatever, and I'll start typing the words so that my, you know, select to go straight to that line. I couldn't do it here. And for those of us who have experienced orgs with just a heap of fields on on you know, some objects will have potentially hundreds of fields. Scrolling was a nightmare. Absolute nightmare. So now you can just click in and start typing and, ah, there you go. So here's my little example. If I press the f key, it takes me straight to flow definition. Really, really, really helpful. You could also select a field in focus by pressing control space, which works for both Mac and Windows as well. And this works for all languages and characters supported by Salesforce. Alright. Next is field history tracking. So we get a big upgrade to field history tracking, in winter twenty six. If you go through setup and into field history tracking that way, you'll get a brand new UI. It feels a lot more modern for starters, and it also lets you, you know, set the fields you wanna track, monitor the fields that are already being tracked, and seek compliance information next to those fields as well. It's designed, obviously, to streamline the audit and compliance process, and I think it does a great job with that. Alrighty. Now we can apply styling to text in a display text component inside of a screen in in Flow Builder. I think I said that right. Yes. We could already do this to a degree, but what it would require is selecting the text and then saying, okay. We want it to be bold and we want it to be roughly, you know, 36 size 30 six. Whereas now, we can select actual set styling. So you can have it makes it a lot easier to to keep your flows uniform. It also improves accessibility for screen flows, for screen reading on on screen flows as well. Now like I said at the beginning, there is just so much that I wish I could talk about, and I I probably could. I'm I'm a bit of a talker. I like talking about these things. These are a few more features that I didn't get time to to, discuss today, but, again, we are limited on time. And I want to show you what some of this stuff looks like. So let me just, set up my screen here. Alright. I'm saying Michael's saying that at Tim, max number of fields still the same. Right? Max number of fields on the object itself? On audit trails. Sorry. As far as I'm aware, yeah, there's no change to that. I didn't see any anything about that. So yeah. Somebody asked if I'd put it in there. No. That's a it's a good question, though. Be good if there was, hey? Wouldn't happen. Alright. Okay. So we can see that now. Let me just zoom in a little bit because my screen's a bit big. So I wanted to start off, by talking about the action hub real quick. So this is the automation application. We can see action hub beta, and we also see a list of all our actions. We can sort them by action type. So we can go by flow, by apex, by, you know, quick action, etcetera. And we can also search that list for a specific action that we wanna go and and see. Now I don't I didn't, pick any of these that would have any examples. No. But what you do is you click in, and you can see any flows that are using that particular action. So it just gives you a good top down view of, right, here's all the actions I have access to. Where are they actually being used? Very, very handy. Now alright. I've got a few tabs open to to try and speed this up a little bit. So I wanted to talk, about, first off, the display text. So what we can see in here is I've added, this is just a a sort of a default, flow in the in the DreamHouse application. I've added a bit of a header. Right? Because we wanna be able to see, okay, what are we doing? Providing the property's address. Now what I didn't do is I started doing it on the general property details, section. So I've got the text in there, but what I wanna do is I wanna make it what did I say? Bold and 36 or something. Right? Probably not. That's not ideal. Because if you look at that closely, it was a different size to the other one. This is inconsistent, and we miss out on all that, screen reading goodness. So what I'm gonna do instead is I'm gonna change now we have paragraph styles. Like I said before, we can now set between normal, which is just normal text, and then heading one, two, three, all the way through six. So I've been using heading two all the way through, and there it is. It's that simple, and it's consistent. So they're all using heading two. Heading two is the same no matter where you're on your flight. Okay? So I'm gonna save that. That is, applying styles to text inside of a ScreenFlow. Speaking of ScreenFlow, let's debug it and see what that looks like. Look at that. We finally get that resizable debug window. It is on the left, like I said. The reason being is now we can have a panel on the left for debug and a panel on the right for configuring an element if we want to. There's a little bit more of that coming, as well by the sounds of things. So keep an eye out on you know, throughout the winter twenty six release and in upcoming releases as well. So when we debug a screen flow, previously, with with other flows when you debug, really all that mattered was the debug itself and you could see your flow. You could provide information at the beginning. Your flow kinda did its thing. Screens, we have this other element. So we can flick between the canvas and the screen up here. Let's say I just wanna call it, you know, my super property. I'm gonna just skip the rest that I don't need to put in and go next. Ignore there we go. The bold's gone. Like I said like Peter said before, there's some heavy umbrellas around here. I mean, we're we're still in the roadworks zone. So if I go next, next, next, we can see that the, the headers are consistent and the same throughout, so back and forth, etcetera. That's ultimately what I wanted to show you in there. Now something else I wanna show you is the type ahead for list views. So if I come to my all flows list view here and I wanna configure another column, let's go, you know, I wanna use the flow owner. You know, I could scroll oh, hang on. I've overshot it. Oh, where's flow owner? I'm not sure. I'm just gonna click in, and I'm gonna start typing flow. Oops. There we oops. Hang on. There we go. Flo owner. Beautiful. There it is. Nice and simple, and now it is in my list view. One last thing I wanted to show you was around the field history tracking, which now because we're in the setup domain it's zoomed out on me, so here we go. So once you go into setup, if you search for field history tracking or you find the menu inside of, feature settings, you can go in here. Let's have a bit of a look at the property application. So I can see that enable field history tracking is turned on. We can see that I've got a couple fields tracked. So I'm tracking the price sold and the asking price, and I'm also tracking the deposit bank details field. And we can also see the sensitivity level of those fields. Now these, I'm I'm guessing, are designed to filter based on, you know, I just wanna see the internal fields. I just wanna see none classified. As of right now, I'm not able to get these filters to work. Again, heavy umbrellas, roadwork zone, things are still rolling out. So there might be a few little, issues like that at the moment, but they will be ironed out before the release assuming, again, nothing guaranteed will will go live until Salesforce pushes it live. So with that said, that was all I wanted to show you around the admin features. Peter, I might hand over to you for the developer bits and pieces. Okay. Alright. I think we're, I think we're rolling. If I can just remember, how to go into presentation mode. Fantastic. Thanks, Tim. It's a great overview. You should take a look at the the, the chat, by the way. Somebody, has been giving you some votes of confidence for your first Salesforce Ben webinar. Technically, not your first webinar, just your first as, you know, as one of the team. But, yeah. Fantastic. Alright. So the first developer feature I'm gonna spend a little bit of time talking about is called trusted mode when you run lightning web components. Now the problem that we, that Salesforce had when they went away from Visualforce oh, so many years ago, and launched the lightning component framework, is that Visualforce used to use an iframe that would they they call it sandbox or protect the rest of the user interface from the functionality in that iframe. And so your Visualforce page would show up and there wouldn't be a problem. Like, that that Visualforce page couldn't go and access data it wasn't supposed to. Now when they came out with the Lightning Component Framework, they wanted all of the components to be first class members of the user interface and to essentially share the same dom. And so when Lightning Components were first launched and then later LWC, there was something called locker service and then eventually, we got lightning web security. And these features are about making sure that given the fact that the user interface is comprised of components from Salesforce, from ISVs, and from the customer themselves, we need to make sure that there was never a case where a component was going to do some kind of compromise access of data to a component it wasn't supposed to. And that's where lightning web security came in. And in doing that, Salesforce basically said to customers, it doesn't matter how much you trust this JavaScript library. If it accesses certain features, you can't use it. Now, the shared security model would say that Salesforce would allow customers to use something if they have gone through the vetting process of that feature. And so, what they did actually, I I'll talk through a little bit, more with this. So to understand how Lightning Web Security works itself, the you know, your browser, when it's running JavaScript, you could kind of consider that to be a host environment. And it's a little bit like with your laptop, you know, as a host environment as well. Now there's also a virtualization layer, and that's essentially what lightning web security is. And then each name space of a set of components runs in its own virtualized space. So the default name space of any components that are created by the customer is called c. And that's why components will have a c dash and then the component name. And then you can have lots of other name spaces as well. And those could be your own packages as a customer. They could be managed packages from AppExchange and of course the Salesforce components themselves are in their own name space. What this means is that certain global objects in the JavaScript run time, for example, the window component I have here as an example, it's going to exist but it's the virtualized version of it. And what that means is it doesn't quite behave like it would if you were directly accessing the browser window, object. So that's how Lightning Web Security works. Locker is a little bit similar. It it accomplishes the same thing but it uses different technology. Lightning Web Security uses a more recent standard from the t c 39 standards body. Now so what is trusted mode? Trusted mode essentially allows you to so first of all, you have to turn it on and then for any static resources that contain a trusted JavaScript library, you have to name that static resource and then that JavaScript library will be able to directly access those global browser objects, cookies, local storage and then other things that normally lightning web security would put behind the virtualized version of that. So, this is huge for customers. Maybe you've already built a lightning web component or you have access to one and maybe that lightning web component uses a JavaScript library that you're happy to have work in your Salesforce front end, but Salesforce previously wouldn't allow you to do that. Now you can turn on this trusted mode. You can enable it for that particular, static resource and you can run with that component as is without any modifications or changes. So that's a big, big change. It does throw a lot more responsibility to the customer in that shared responsibility model. So So I think that's gonna be really interesting given what's going on right now with the the sort of security breaches that we're seeing. But it's a massive change and I think there are certain customers this will be super valuable for. Now next thing is about packaging. Now packaging, if you are doing any kind of package based development, you have to identify the packages, in your SFDX project dot JSON file when you go and deploy them. So for instance, in your build process, you would, you know, you'd stand up your sandbox, let's say. And then you would have a project definitions file like this that would state which packages were required and then it would go through the installation process of those. And this is actually the example from the release notes that I put up on the slide here. And it kinda gives a very simple example where package a you see up at the top in purple has a package b, which also references package a. But then package c, which is the last one, you can see has to reference both package a and b. So it kind of references this whole package hierarchy. In this case, this doesn't look so bad. So I wanted to play this out a little bit further. If you had a more complex package hierarchy where maybe a references b and c, n b and c each reference d, e, and f, what you end up with is spaghetti. Right? And if you look at package a, you have to mention every single package in the hierarchy, which means if you need to refactor or add a package or remove a package, it just becomes a huge headache. The more complex your package hierarchy, the more insane actually this becomes. So this new feature, simplifies this where a single component or sorry, a single package only needs to reference its direct ancestors from now on. So that would greatly simplify package a's dependencies, because it would only have to name b and c. It wouldn't have to name all of the other things in its package hierarchy. So, from a developer experience standpoint, this is a huge usability improvement. So, if you're not a developer, hopefully, I've illustrated for you, how your developers are gonna be a lot happier if they're doing package based development. And the last thing I want to cover here is some of the testing updates. So, there's actually quite a few changes that have happening for that are happening for this. And I think a lot of it has to do with, it it seems like Salesforce bringing on more and more, the support for being able to run and automate flow tests. And in doing so, they're not just sort of adding flow features, they're reevaluating what it means to test in Salesforce. Because what you can see in this user interface is that, in addition to I'm gonna put on my little, laser pointer here. In addition to this here, which is, that's an Apex class that I've tested. There's also down here a flow that I've tested. So, I can now run and execute both flow and Apex tests from the UI. But it gets even better than that. They've added some new APIs where you can actually find and execute not just Apex test, but now flow tests as well. And those are, again, from a single unified API endpoint. And then the last thing that has trickled down from this is in the Salesforce CLI itself, which has always had Apex testing capabilities. They have now surfaced flow tests that you can see right here. That is executing a flow test. And then, there's another one where you can go and retrieve the flow test results, which I've outputted here onto my command line. So so there we go. Oh, what's that? Extremely intensifies? Oh, is that Excitement intensifies. Insight yeah. Yeah. Anytime we see upgrades to flow testing, I get excited. There we go. Yeah. So, so there we go. Now when I've talked about this, and I think this is absolutely fair criticism, I would say, you know, right now, flow tests, there are some flow tests that are very effective, but quite a few flows right now are not really testable. If you have a very complex data structure, for example, that's a bit of a challenge. There are no UI based flows that are testable today. So flow tests, I think, are let's let's say, you know, maybe not quite their infancy, but their toddlerhood. I don't know. But but here's my take on this. And I've seen this before. Sometimes sometimes, a product manager will put a feature in place that, that kind of creates a demand. And so I'm wondering if the the the ability to automate flow tests, if some of the reason they did it this way was to kind of build a bit of a groundswell of support to invest more in flow testing. At least, you know, nobody's told me that, but that's kinda what I'm hoping. I'm doing a little bit of inferring and, kind of reading the tea leaves as to as to what the flow product team are doing. But, you know, if they are, I think we should all support them and really, you know, vocalize that we really support building better tests for flows. And I know Tim is a big supporter of that. Those of you who watched our webinar a couple of weeks ago will absolutely know that's something that we all support. So there we go. And I think oh, yeah. So, loads of other release features. It was very difficult to pick just three to go with, at least a a a enough that I could fit into the size of this webinar. Some of the ones, I think, sort of, new CDN domains is really interesting. Improvements to the lightning web components local dev, that's kinda going in the right direction. SLDS two point o is gonna be generally available. More typescript generation definition, sorry, for LWCs. There's loads and loads and loads of developer features out there. None of them are super big and super flashy, but all of it to me shows kinda going in the right direction. And I think with that, I've come to my demo slide, which is my cue to do a demo of all things. Let's just make sure I'm going to the right place. Yes. There we go. Alright. So this is the application test execution UI. Now, I think this is really just the Apex test execution user interface. But they have kindly renamed the, the menu item for that to be more inclusive. It's no longer just Apex. It says application. And as you can see, when tests run, I'm gonna actually make this a little bigger. That was quite small to me. That's probably a little bit better, isn't it folks? Yeah. So you can now see in my recent test results, I can see a test run that says flow testing dot set new property status. So clearly, that is a flow that I ran test for. And then I also have test property controller. I had a failed test in here earlier that I thought would be kind of cool, to to sort of show it, like, fixing it. But, Brandon. Well, so Brandon so you would only have seen a renamed user interface if you're in a winter26 org, which this is. So just be aware of that. If you were in a winter26 org and running Apex test, then you might have seen application test execution and missed it. But anyway, so how do I run a test? This is basically the same thing, as I used to do with Apex. But the interesting thing, of course, is that, you know, I still have my namespace so I can execute those. I still have any other namespaces, but then I also have flow testing. So my flow testing namespace, essentially, is gonna show me any flow tests that I will have created. I can select that and I can click run. I think it's tantalizing that they've put, they've put code coverage tick box and maybe that's just because they couldn't be bothered to remove it from the test run. But I I wonder if they are gonna have code coverage for Apex oh, sorry. For Apex. For Apex. Yeah. So, you know, fingers crossed that that comes our way someday. Nobody said that that's happening. Let's just be clear. But, you know, it'd be really cool if it did. And, to me, the fact it's still there says that maybe they're thinking about that. Okay. So that's run through the user interface, but, of course, we don't just wanna run this through the user interface. We wanna be able to automate this. Right? So, to go and find my oh, what do I do with that? Oh, there we go. You know what? I had it in the wrong place. Alright. So, so here I've got, my Salesforce command line. And just to make this go a little bit faster and to not have you watch me typing out command line commands because no. Let's face it. That's good, like, you know, content. I've gone ahead and just had these commands sort of filled out so I can execute them. Now the first one is just a request to the tooling endpoint that you can see here. And what that's going to do because I've I've prettified it prettified it into some JSON and then I used grep to just pull out some filters, you can see that, these are the three new endpoints that they've surfaced to the tooling API. One is called run test asynchronous, the other is called run tests synchronous, and the final one is just tests. Now the tests endpoint is to query for tests. So if you wanna see which tests are available in this environment, that endpoint will give you that information. And then you do have to specify your name space just like you saw in the user interface. And I'll show that in a second. The run tests asynchronous and synchronous, of course, are to actually run the tests once you know them. Now let's go and see about executing some of these. Oh, and by the way, again, you know, road sign, road sign, caveat here. I looked really hard to try and find some documentation for either of the two run tests endpoints so that I could know what the JSON payload would be to actually run a test, and I didn't succeed. So if anybody does know, like, anything about that, I would love it if you would post that on social. You could mention me, because I'd like to learn, like, how do I actually go and run the test with this API. The one place I didn't look, which, you know, I I just ran out of time. I'm sure in the open source code for the Salesforce CLI that runs in the flow test, like, somewhere in there is something that will tell me what the JSON payload would look like. But I I just didn't have the time to dig through that to find that out. So my apologies. I tried to bring something to you. But anyway so I won't have the run tests examples in the API, but I do have the Salesforce CLI version of that for flow. Okay. So how do how does the tests endpoint work? This is really interesting to me. If you run it without any parameters or anything like that, what would you think it would run? Anyone? It actually does the flow test. So it's actually only returning the flow tests as a default. I think that's a really interesting choice, and I'm not sure why that is or if it'll even, like, last out through, GA. But as of today, this is what just running the test endpoint does as as a as a get request. And so you can see here, it's just returning the information about my flow test to me including, like, what's the signature of that test and what would the name be if I wanted to run it or what's the name of the actual flow itself. So there there's my my, my request to the test endpoint for the flows. Now this is a bit of a letdown and, again, road work. When you go and say my namespace, again, in the documentation, it says this should return any tests that are just Apex tests, basically, in the in the home namespace for the org. Unfortunately, I get back an empty array, which that's a bit of a sad trombone moment. But we can at least see how the API is going to work. And then the last thing I wanted to show in the demo was running a flow test from the command line. And so here you can see, in the Salesforce, there is now an Salesforce flow topic. So that's really interesting. And in that flow topic, there are a few different things that you can do that I showed on the slide, like run tests and get tests. This is gonna do the run test. So clearly, the run test API endpoint works because they're using it here. Right? I just couldn't find the documentation. But if I run this from the Salesforce, and because I ran it as synchronous, that means it won't just come back and say go and fetch the test later. It'll wait for the test to be done, give me the results. And again, just like I saw in the UI, my test has passed. Woo hoo. Exciting. I just ran a flow test from the command line. That's like a first ever for most of the people in this audience, I think. Right? It was for me anyway right after I ran it. Alright. There we go. Excellent. That's the perfect gift there, Tim. And with that, I'm gonna turn it back to Tim to talk about some of the other features that have that are coming in winter twenty six. Amazing stuff. Dude, that isn't honestly, I I love I get very excited about these releases. Where's my page? Yep. I definitely know you do. I I think you did enjoy that one. Oh, big time, mate. Anything anytime they're talking about sort of streamlining the testing of flows and and potentially putting in some more guardrails because it's a great tool, but but I think something that came up in the previous webinar was there could definitely be some more, you know, sort of tightening of of flow. But, anyway, I'm I'm I could I could talk about this all day, and I will if I don't stop today. So winter twenty six features by domain. So this is by sales, service, marketing, and bits and pieces of the winter twenty six release that will benefit these teams. Now the reason I'm saying by domain and not product is because some of these are not really product specific, but we thought about some ways that you could use them to benefit these different domains in the business. So the first one, look, this is Einstein Activity Capture now stores as a native activity record. So previously, these were not stored in standard records. These were stored off in, I think it was AWS and then called and had limitations around, what you could actually do with them and how you could use them. Now that they are just activity records, you got a lot more functionality over the top. So this one, if you've been having issues in the past with with, EAC records and and the emails that are stored as a result, of emails flowing through EAC, definitely investigate this, because you will likely find a lot of those problems resolved. Now this one is not new. Sorting lists, list views by multiple columns is not new, but it is generally available now. So I thought it's definitely it's a very, very powerful one, and it's definitely worth talking about as well. If you weren't aware of it, this is a a powerful feature. So instead of just being able to sort you know, you click up the top and you can filter by flow type up or down, you can filter by flow type, and then by status and then by last modified in this example. I've got another example I'll show you in a second. Worth noting as well, when you set this up, so when you configure this on on desktop, it will apply to the same, list views on the mobile application as well. So it will transfer across from from desktop to mobile so that you've got your same filtration. So your same your same, sorting on mobile as you do in desktop. So mobile users are missing out there. And the configuration will remain until it's either cleared or changed. Empowering sales ops to manage flow approvals. Now this is another one. Again, I've gotta I've gotta catch myself because I could talk about this for a long time. Empower sales ops to manage flow approvals with a new approval designer permission. Pretty cool. Right? But that last point down there, this does not require the manage flows permission like before. Approval designer permission allows for management of flow approval processes. Now this is interesting and this is, like sorry. This is particularly interesting because when we saw the birth of the automation app inside of the main Salesforce set, building flows outside of setup, There was a lot of speculation that started there that, hey. I wonder why this is the case because setup is is typically reserved for sort of admins, delegated admins, and developers, and all that sort of thing, and not so much for for business users. Business users don't really use the setup much. So why would they put something that traditionally was reserved for, for for admins and and developers into the the end user world? It sort of didn't make sense. And now we're starting to see some changes here. So with the approval designer permission, you can give a user the ability to create, edit, delete, and activate flow approval processes without, again, without needing to be able to, edit or manage flows using the manage flows permission. That is super interesting. And, again, I I could I could have so many conversations around that, but I'm gonna force myself to move on to the next one. Otherwise, we'll be here all night. Okay. Cool. Now this one comes for when you're exporting a report to CSV. If you've exported a report to CSV before and it's got some data that starts with an equals, a plus, a minus, or whatever else, it can cause some issues with your, with the data inside of, like, Microsoft Excel. Because Microsoft Excel and other spreadsheeting tools look for these characters to perform functions. So by putting an apostrophe in front of it, it basically goes, hey. This is only there. That character is only there as, you know, something that you need to look at and you need to to be aware of. This is not a function. I'm not trying to add something. I'm not trying to minus something, take something away, whatever. So there's a function or a a feature, sorry, inside of reports and dashboards settings inside of setup that will allow you to, automatically put that apostrophe in rather than you having to build a formula after the fact just to clean up the data. So very, very handy. You can enable that in, setup, and it will apply throughout the entire org, which is good. You can improve your support analytics by enabling role based reporting. Role based reporting allows you to group filter and display the team role name inside of your reports. So I've got a demo I can quickly show you there as well as to what that looks like. Easily see the input on case, based on groups of users. So for example, you know, if you had different, people sitting in different seats when they're putting in effort on a on a case, you can now report based on that and make that a little bit easier and more granular as well. Now, again, there's there's there's so many things that I can't you know, we're gonna run out of time to talk about. This time I color coded them. So the pink is the service cloud pink. The orange is is marketing cloud orange. And I've said green. My wife corrected me before, and said this is actually teal. So teal is, is is sales. So these are all the bits and pieces that I thought would be would be beneficial if we had the time to talk about it. Particularly, I wanted to call out too. There's a lot of and probably this doesn't come as a shock at all. There's a lot of really powerful Salesforce stuff here. It really feels like a refinement of, Salesforce functionality in the winter twenty six release. Again, I would love to show, I think a lot more specifically around the Salesforce upgrades in winter twenty six, but we don't have the time. Also, I need an org that has access to see it all, which would be good. Alright. Onto the demo. Let me just switch over to my other display. Now immediately oh, sorry. I'll be peeping over your mouth. Oh, yeah. So I was just gonna say, for people if if you have questions, we're gonna do some q and a when, Tim is done. So pop them into the q and a section, and we'll be sure to get to those at the end. So while Tim's getting set up, you know, think about what, any questions that you have, and we'll, we'll try and cover those, then. Good call, Peter. Absolutely. Absolutely. And it's good to see as well. I've been seeing the the very lovely conversation going going on through the chat. It's always good. It brings brings a bit of, you know, life to the webinar. It's always good. Now the first thing I can feel I I was just talking about comments. Maybe hold the comments for a second because, yes, I'm looking at permissions on profiles. I know we're not supposed to do that, but talking about the whole, you know, when the road works heavy umbrella section, I'm having issues accessing permission sets at the moment in this particular org. It's not it's not a Windows 26 thing necessarily. It's just an issue at the moment with this. I'm not sure what's what's going wrong. So that's why I'm demonstrating this here. Okay? I've got a profile. I created a new profile, and I've applied the approval designer permission. Now, again, what this allows somebody to do is to go in and create, edit, and I think it was activate, maybe delete as well, the the, flow approval processes without having to have the manage flows permission. This is this is extremely unique. We we've never sort of seen this before where, you know, somebody is given the ability to edit a flow without being told they're allowed to edit flows. So we're gonna start this is, I think I've I've pinned them up at the top there. There we go. I put the automation one at the top here. Since the birth of the automation app and in the previous release, the approvals app, we've seen two things that were previously restricted to admins and restricted to the setup menu now put into the the main user domain. So I wonder if this is the sign of of more things to come where we're gonna hand off we'll have have a lot more flexibility around, functions in, you know, for things like flow, for example. Flow is is the key one that's been this has been happening for for users that wouldn't typically have that capability. That makes sense. So in a permission set is where you should apply this if you do choose to apply it, not on a profile. This is just to make sure I knew that, hey. Yeah. My permission sets are not working for me right now, but I've applied it to this profile. This user, which is a sales ops user, would be able to go in and, make changes to approvals as well. Alright. You know, wherever the prep admin is, I think there's a there's a chill going down her back right now, Tim. So Where where who? Sorry? Cheryl Feldman. The, she's the Oh, yes. Yes. Yes. Yes. No. Good. It it cut out the in in California and went like, oh my god. I just had a nightmare. It's cold sweat. Oh, man. Hey. I get excited. I get excited. It's it's it's it's good. You know, any changes, like, I think are are are good. Alright. So the properties list view, here that we got, I wanted to show you the sorting list views by multiple columns. So here, if you have a little bit quick look at this list view, I'm sorting by city, but you also see the arrow on beds. So I was sitting here and I got beds, which, honestly, if you if you ignore the the names here and you just pay attention to city and beds, it just makes my experience, looking for the right property a lot easier because I could be looking by city. I could be looking then by beds immediately. To change that, I just got here to sorry. I was a bit quick. To column sort. Column sort allows you, to select up to five columns. So I can add more if I wanted or I could not in this case because I think sitting in beds is perfect. And then I can choose either ascending or descending. I can move beds up to the top if I want. If I care about beds first, you know, we want all the beds sort of top to bottom there and we don't really want the the or, you know, cities not as important, then, you know, I would put beds first. Otherwise, city can be first. You get the point. Once you apply this, if you head over to the mobile app, which I I don't have a a demo of at the moment, but if you look closely at the list view, it will say sorting by, the fields that you're sorting by, which makes it a lot easier to to do what you wanna do across both desktop and mobile. Now the next thing I wanted to show was I had a report prepared, and here it is now. So here's a report that I've created. There's two things we're gonna talk about with reports. So I think, in the the window 26, you know, key features video that, was put up on the Salesforce Ben YouTube channel. One of the things that Ben mentioned was there was a lot of refinements to reports, and here's just a handful of them that we'll show you now, but I highly recommend going and watching that video as well, following this if you're looking for a little bit more. There's two things I wanna show you. Number one, team role by name. So we can see here, the, you know, for for the case who the, the team member was that was that had put in the, I think, the last effort, on the case. And then the other thing you'll notice in description is I've got minuses, I've got equal signs, and this has caused problems. So what I've done is I did go ahead in this org before this demo, because similar to what Peter was saying, you know, they wanna watch and type code just like you don't wanna see me sift through menus and tick tick tick boxes. So what I have done is I've downloaded the report prior, then I've got it enabled already. Now I hope you can see that. I'm getting an error in Excel saying, hey. Do you want me to convert some stuff? I'm just gonna go don't convert, and I wanna show you what this looks like now. This is what my exported report looks like. It's a mess. Right? I could I could go in here, create a formula, tidy all this up, but we can see that the problem is because of those minuses and equals and all that sort of thing. So, yuck, we don't want that. So if I now go ahead and export, this is after I've enabled that checkbox, to to automatically put the apostrophe in front of it. Right? So if I go export, I wanna go details only, and I'm gonna go CSV and export. There we go. I will open up my, thing. I'll go don't convert again. And here we go. Let me zoom in. We've got apostrophes in front of those fields. So this is clean data now. It's not trying to, you know, perform a function, which, you know, having those characters at the beginning, kind of that's what it's telling Excel to do. We We don't have to worry about that now. It's all the apostrophe sort of cancels that out. And, yeah, that's that's more or less what I wanted to to show you there. Let me just switch back to the the slides real quick. Conscious too that we have, five minutes left, so I will stop talk oh, no. I'll stop talking in a second. Sorry. You're gonna have to keep hearing my voice for a little bit longer. That's what I was saying in the comments before. I really wanted to go over this timeline again. So, as Peter was saying too, this is not window 26 isn't out now. It's not dropping now. It's not something that will be out in your org now. This is upcoming. So this in the past, August 21, the prerelease Salesforce orgs were, made available and refreshed to include the first iteration of widget 26. Again, we're gonna see changes, throughout this. So I gave you the example of Action Hub, where you can see a filter is in there, but it's not currently, working. We will continue to get updates before everything goes live. So we've already had the the, prerelease orgs. We've already had the, you know, thousand plus page release notes. Again, if you wanna do some light reading, that's there for you. September 4, that is today. This is the sandbox cutoff date. So if you want to refresh your sandbox prior to the the cutoff date, you'll need to do that. Now tomorrow, we're gonna see the sandbox preview starting. Salesforce will also put up the release badge on Trailhead that you can go ahead and do, which will give you some information about the key features per domain. They tend to do that as well. And there'll be the release sites to salesforce.com/releases. Coming soon, the release readiness, webinar that Salesforce themselves will run, the overview deck, and, of course, it will go live across three weekends depending on which instance you are running on. Make sure to check the trust.salesforce.com, site for more information about your instance. Beautiful. Peter, I might hand over to you. Yeah. Just, one more time, we want to give a shout out to our, sponsor. There we go. And, one of the things that, foundations is talking about this particular month is marketing and foundations. And they want you to know, what can, foundations do for your marketing team. Some examples are all your data would be can be unified, and you can personalize email campaigns with data from marketing, sales, service, and commerce. You can also get started quickly with prebuilt email templates and targeted segmentation. You can make data driven decisions with email campaign analytics. And remember that all these marketing features are available for free via foundations, and they would love it if you would try them out. Now we're gonna leave these QR codes up even though we're gonna move into the q and a right now. So you can scan these while we've got them up and learn more about foundations. Remember, it's free in your account and you can also learn more on Trailhead. With that, so one question that has come up, Tim, is about the multi, the multiple filter fields. There was a question. I I think it may have been answered by some of the other audience members. The list view that enables setting enable okay. I'm going way back now. Load old messages? Really? That far back? There was a question While while you find that one too, I just wanted to confirm a 100%. Yes. Orange was marketing. Sorry. That's my bad. I should've had a little legend off to the side. I was just up above there, actually. Goodness. I've completely lost it. But I believe the question was whether you could construct a list view for your for your users or if it was something that was user specific. I think it's both, isn't it? The so that you can construct a list view for your users. I'm 99% sure one of the the limit well, the limitation, in in the previous release anyway was that you had to sort it for yourself. And and the reason that I've I've oh, did you say something? Sorry, Peter? No. No. I said I guess I said got it is all. Yeah. Yeah. Yeah. So the the the the the the scenario that I, was questioned around was, okay. Cool. Yes. It applies to mobile. Like, if you set it up in desktop to apply to mobile, what about users that we don't want using desktop? So so one of the companies I was talking to had had mobile and the users. How do they do it? I'm like, that's a really good point. That's a gap. So, so I'm I'm not too sure in winter twenty six. I didn't see anything that mentioned a change there, but that's a really good point. Cool. Alright. One question that came up earlier when we were talking about security, I need to create connected apps in my sandbox. Where can I create them? The answer is you shouldn't create them in your sandbox. If you do that and you refresh your sandbox, the connected app goes away, which is bad. Connected apps are a very strange kind of metadata. They sort of, you know, they they're originated in one org and then they can kind of propagate to other ones because of their role as being kind of an authentication artifact, a piece of authentication. And that's part of the reason why connected apps exist in this sort of dual space where you can authorize with connected app and not have it installed in your org, or you can install it in your org. And this is actually a little bit of what the security, exploit has been about. And one of the recent changes was in fact some changes to, who could authorize a connected app without it being installed in the org. So also check out that information too. There are some other really, really good questions. Unfortunately, we are up on time. So, you know, if if you do have more questions, be sure to check out our feed on LinkedIn. Feel free to mention Peter or myself or, you know, just, you know, ask those questions and we'll try and get some answers to them. With that, I think, I wanna thank everybody on the webinar for participating. Really, like, very actively engaging in the chat and the q and a. And wanna thank my, my new, yeah, my new partner at arms in doing, webinars here, Peter, for joining me on this release webinar. Well, thank you for having me. This is always great. It's always good to, have a bit of a chat about, you know, new features and and see everyone's opinions and all that. Grateful to be here. Fantastic. Thanks, everyone, and, we look forward to seeing you soon on another Salesforce Ben webinar. Take care. Thanks so much.