Salesforce Summer '24 Release Notes Highlights

So you're most recently modified. Flus. It also, let allows you to search for flows using keywords, and it allows you to filter those flows by type status. It's really handy to be able to have these different flows that you can. Um. Filter in different ways. It also has the flow errors on that same page. So when you don't have to go to a different object to see what the errors are. It shows you all on the same view. I really like that as well. So.

Another thing about this is that you're able to group your flows into categories and subcategories. So on the next slide, you're gonna see that the um category subcategory um can be added into the flow details, and you're able to add that into your views inside of the automation. The new automation look view. So. Um another great way to be able to filter and look at those. Items inside of salesforce. So this is my my last slide. And then we're gonna talk. I'm gonna hand it over to Ian. But these are a couple of interesting things that I just liked. The 1st one was. Finding records that um by using personal labels so you can add personal labels onto, let's say your leasing contacts. Let's say you're a golfer, and you want to have a group of individuals that you connect to in your database. Um, because they are also have an interesting golf. Maybe you invite them to a golf tournament once a year, or you send them little golf snippets every now and then.

And to just touch base with them, and you can. Easily. Now label them as part of your golf group. And add us that part of that golf group. You can pull a list view of them and be able to add it to to do list items and and different list views so that you can see how these um. You know, have a list view of this golfer group and easily call through it, or. You know. Do other actions through that list view. So I think that's really handy. Uh. The only thing you can't do with it is share that um out to other users. It's your personal label. It's not a label that you can share. I I'm hoping that's coming in a future release.

And the last thing I want to talk about is being able to do salesforce backup on, read only objects. So in the past you've only been able to. Aye. Cover, read only objects. Um or cover only standard objects or custom objects that were not read only, and there are some objects inside of salesforce that you only have access to. Because and you could only read them. You can't edit them or update them. Uh the, this is a new. Pack, manage package that allows you to download and store this data and be able to keep track of it, so that if anything ever were to get changed in some way you would have access to it.

So I'm gonna go ahead and turn this over to Ian. To talk about. Thanks, Sandra. Yeah, yeah. Yeah. Uh alright! Well, uh.

Every single release uh the flow section of the release notes is always my favorite section. It's where I go to first.st When I 1st am opening up the release notes. Um. And uh, I actually wrote a blog post uh that we posted recently. Um, you can see it listed there uh, so definitely go check that out if you want to see some more details about some of the uh flow updates in this release. Um. I am super excited about that uh automation app that Sandra shared about. Uh, and I'm very excited about what's going to become coming next. With that I don't know exactly what that'll be, but it just feels like it's really right for a lot of future. Uh Development. There. Uh today I wanted to talk about. Uh, I I just wanted to pull out some of those items from that uh blog post that I shared there. Um! As to just to highlight some of the uh new updates to flow. So the 1st one is uh the repeater screen component. Uh. So this was actually, it was released last.

Release. As a beta feature, so as uh you could test it during the last release. But now it's actually officially out and available as uh generally available. Um! It's now fully supported by salesforce. Um, and what this component allows us to do. Um. So let let's say that we have a screen flow where users can add contacts related to a parent account. In the past. Uh, if we if we knew how many contacts they wanted to add, then uh, we could do that on one screen, or maybe have a series of screens where they're adding each of those contacts separately. Uh. If we didn't know how many contacts they wanted to add, then we had to do kind of a workaround with with. And um and checking if they wanted to add another one and loop back, and it it got kind of.

Complicated. Now, this repeater, component. Allows users to just add another record. Add another record, add another record, and they can add as many as they want, all on the same screen page. Um. So it'll just really simplify. The uh workflow of building that sort of setup on the back end and also streamline it for the users who are uh completing the screen flow.

The next one uh, similarly was was uh released into beta during the last release uh, but now is generally available. Uh, and this is the transform element. So uh, the transform element allows us to map data from one source. To a target uh to a destination. Usually that's going to be from one object to another object. Um. And uh. So, for example, let's say that we have a collection of opportunities. And for each of those opportunities we want to update the parent account. Uh, they might be different accounts for each of the opportunities. Um.

And so in the past. What we would have needed to do to accomplish this is loop through each of those opportunities. And then within the loop. Set a variable for the account. Add that account to a collection. And then at the end, after the loop finishes, then we can update that collection of accounts.

Now with this transform element. We can take the collection of opportunities. Map, the data. And it'll output the collection of accounts automatically. Uh, no need to build a loop uh and build those those variables. It'll just give us that collection uh, and you can see in the screenshot there. Um! One of the lines has little symbol. Uh, that means that there's actually a formula being applied to the mapping. So uh.

Rather than just taking the data from one spot to another. We can actually transform that data as it's being mapped across uh and change it in some way to fit uh the destination. How we need it to. The next update uh that I wanted to. Highlight is that uh, when we are creating new records in a flow. We can now actually check for existing matching records. Uh, based on whatever criteria we define. Um and then uh, if it finds a match based on that criteria. Uh, we can choose whether we should either update the most recently modified matching record um, or we can just. Skip. Making that update altogether for that particular record. Um. So what this does is it essentially gives us the functionality within flow which is super nice. It helps us to. Uh. We don't have to do as many, you know, decision elements, or uh, perhaps even just risking making duplicate records.

Uh. Now we can cut down on some of that a bit. And then uh the last one I wanted to highlight uh debugging. Everybody's favorite activity uh, and especially for scheduled flows uh. Debugging has always been such a pain. Um in the past, it would always just grab whatever was the 1st record that it found that it met the entry. Uh. And so it was always really hard to test different scenarios. Um, so testing whether the record has this data versus has this data. It was really hard to do that, because it would just select whichever record 1st met the criteria. You had no control over that.

Now debugging for scheduled flows is going to act just like it does for record. Triggered flows where you'll be able to choose. Which record to run the test on. Ah! Which makes it super easy to test different scenarios. Uh, and you can even just like in record flows. You can even choose to optionally. Skip the entry criteria um. Just to test a lot of different scenarios. Uh the Debug screen will also uh tell us how many records would have met the.

Criteria, the entry criteria for the scheduled flow. Uh, so uh, that makes it a super nice way to double check that you're not gonna run into a data volume issues or issues with the flow, timing out that sort of thing. So I'm very excited about all of that. Uh next. So Sandra mentioned earlier salesforce uh migrating uh from having permissions on the profile to using permission sets and permission set groups. And uh you were correct, Sandra. It is uh early 26 uh the. February. Release.

In 2,026. Is when that is going to be enforced. So we do need to start thinking now about ah. Planning or uh even already starting to migrate all of that, all of those permissions over into permission sets. Thankfully. Uh! Since Salesforce announced this, they have been adding a lot of new features uh, that'll help make uh the permissions more transparent and make it a little easier to manage all of this. So the 1st one is that uh, while you're viewing a specific user uh, you can click a, there's a view summary button.

Now to. And when you click on that it'll take you to a brand new page that will summarize. Uh all of the permissions and access that that user has. So that's the uh user permissions. The objections. The field permissions which you can actually filter by object. And then custom permissions. As well as their membership in public groups and queues.

So uh nice way in in one single page to really see all of the different access that a single user has. Um in order to maybe want to double check. Hey? Why does this person not see this field? Or maybe, why are they seeing this when they shouldn't. Um, you can double check from here. Do they have the access that they need. Uh. Similarly, when you are looking at a permission set. There is now a view summary button that lets you see a similar summary of what is included in that permission set, or in that permission set group. Uh. And this is something that I've really been wanting for a long time. It it in the past has always been really difficult to figure out what is included in a permission set.

Um, whereas now we can we have this nice summary page uh, it looks very similar to the the user summary page. Um other than I mean. It doesn't include the uh public group and queue membership. Of course. Um, and then it adds, Uh, on a permission set, it'll show which groups that permission set is a part of and on a group. It'll show which permission sets are part of that group. And then the 3rd big updates around this is that salesforce has developed a new feature called user access policies. Uh. These are a new way to actually automate the assigning of permission sets and package licenses and public groups, etc. Um so how it works uh you.

Set up a series of rules that you you put in a specific order, so you to make sure that they run in the right order. Uh, and within each of the rules you set criteria that salesforce should look at um. And then, if a user meets that criteria. Then you can either add or remove certain. Access. Um. You can. Uh. So this this is a super nice way. Let's say, if you have a codified.

Uh process for creating new users in salesforce, you know. Okay, this person always needs uh, or this role always needs this set of permissions. And access to this package. Well, now, you can just set up these user access policies where maybe it's by profile. Um, you don't need to manually assign all of those permission sets or permission set groups. You can just set up a rule that says, Hey, when you, when I create a user that has this profile. Give them these permission sets and permission set groups, assign them a license for this package, add them to this public group. All automatically uh, and.

Because this is all automatic. That also means that this can be a really great way to uh assist with the migration from profiles to permission sets. So as you're building out your new um your new setup for how you're managing and organizing all your permission sets. If you have 300 users that you need to move over to the new setup and. Rather than needing to go through one by one on all of those users and assign each of those permission sets and update their access. You can set up these rules, and it'll just move all 300 of them all at once. Uh! So super nice saving feature. Um, both. During the migration and also ongoing later on.

We also have a number of updates for the lightning app builder and the dynamic forms. Uh, so a lot of this is to help uh bring features that have been available in classic record pages. Now they're available in dynamic forms. And so the 1st one is that uh, when you're creating a new custom field uh, we we all know that uh that screen. That shows, hey? Do you wanna add this field to this record page. Um. Well, now, if the object has a lightning record page that has dynamic forms enabled, it will also ask, Do you want to add this field to this lightning record. Page. Um nice way to just. Make sure you're not forgetting to add it to the page uh, and then.

Uh get confused. Why, your users can't see it because it hasn't been added. Ah! Next one. When you're viewing an existing custom field, there's the where is this used button. And that's always been a nice uh nice way to see where a field is being referenced, whether that's in a formula or in a report, or in a flow uh or on a record page. Uh, and now they've added it so that it'll also display. Lightning record pages with dynamic forms.

That reference, this field. Um. So just another way to to keep on top of where your fields are being used. When you are building the the page with dynamic forms. Uh, you can also now add blank space uh, similar to in the classic record pages. Um, so you can see a screenshot over on the left. Um, this can help with just helping to keep the page look uh organized and and cleaner uh, and maybe keep your uh. Related fields next to each other, without necessarily needing to move them to a separate section. Um! Just helps to keep the page clean.

And then uh, I'm very excited about this last one uh so for. Tabs on a lightning page. Uh in the past. We can set the conditional visibility on the entire tabs component as a whole. So this person should see all of these tabs, or should not see all of these tabs. Uh now.

That Salesforce has added the ability to set that conditional. Per tab. Which I'm very excited about, because it's going to help us to streamline a lot of things. So, for example, let's say that we have a lightning page for our donors. And. Uh, we have one tab that's for just the general contact details. Um, another tab. That's for the related lists. And maybe we have another tab. That's just specifically the information about Major.

Um. And we only want that to show for our major donors. Uh now we can do that. Uh. So when you're looking at someone who's not a major donor, you won't see that tab. You won't be cluttering up the page. Uh, and showing information. That's uh. Not. Uh pertinent.

But on a major donor record we will see that tab and have access to those fields. Alright. Next, I want to dive into some updates for nonprofit cloud. Specifically. So first, st I guess not. Updates. Uh, these are actually uh retirements. Uh, so uh. Last year. It was announced that uh elevate is going to be retired. Um! Already organizations are not able to renew elevate. At this point. Um. They haven't been able to since uh the end of last year uh! And Salesforce is now saying the anticipated deactivation dates for elevate when it'll if you still have a current contract for it. Um, it will stop working on October 1st of this year.

And then the other one is foundation connect. So this is a new announcement of theirs. Organizations won't be able to renew foundation, connect. After January 31st of this coming year. Um and uh, and so then anyone who has an ongoing uh contract for it uh it will. It's anticipated to be deactivated at the end of January of. 2026. Uh, and then there, my, my, the rest of my updates. Um, are all about nonprofit cloud. Uh, and this is the new. Product by a salesforce that came out last year or the the year before that. More recently, it's not.

The Nonprofit success. Um similar to uh Eda. There, there has not been a whole lot of new updates for Npsp. But I am very excited about some of these updates in nonprofit cloud. Um, so the 1st one is uh documentation being uh available. Ah! Just within salesforce, without needing to use a 3rd party. Ah, package or app. Um.

So this is managed using omni studio uh, you can. Uh you upload a template. And then it will uh pull in data from the salesforce records and uh, and populate within the document. Um. And so you can use this for a lot of different things you could use it for uh, for giftments. You could use it for Grant letters. You could use it for various program uh related documents. Um. And you can see in the screenshot over on the right side. Uh, there are buttons. You can download the document as a word file, or as a Pdf.

It'll also attach a Pdf. Of the file to the record. Uh, and then uh, it might be kind of small. So uh we can circle it here. Uh, there's a little checkbox uh for sending the uh sending a docusign envelope. Uh. So you can connect this to docusign to streamline the process of getting signatures and um. Making your documents, official. Next for grant making specifically a couple updates here. Uh. So the 1st one is uh grant making objects are now configured to work with outcome management. Um, and just for clarification, the outcome management is already available for fundraising and program management.

But now they are, it's also available within grant making um. And in case you're not familiar with what outcome management is. Uh, it's a way for you to track your your outputs and your outcomes and your measures. And uh, based on time periods. Uh, that you set uh, and uh, you can organize it based on your organization's logic model. So it's a nice way to help to track and demonstrate your organization's impact. Uh, and then the second update uh. So when applicants are filling out. There the grant applications through the grantee portal, through the experience cloud site. Uh, they can now add collaborators to help complete certain sections of the application. Uh. So, for example, maybe the Grant writer needs a program manager to fill out a a section describing the activities and impact of their specific program.

The Grant writer rather than needing to handle that externally from salesforce, and then maybe copy paste into the application. Now they can just invite that person to uh update the application themselves. Uh, so they can manage that all right within the grantee portal. Program and case management has one big update, and that is that they have added a series of objects to track participant cohorts. Um, so uh, this could be a particular group that's moving through the programs together. Uh, so maybe a specific class or uh, people who are meeting at the same time something like that. Uh, or it could be time based uh. So maybe all of the participants who enrolled this month, or who enrolled this year. Uh! Whatever makes sense for you. Um. This does allow you to then compare one cohort to another, uh, maybe one class to another, or it could be um. Uh a cohort based on uh, compared to previous cohorts. Uh, or you can also use it to compare an individual to the rest of their cohorts. Uh, in order to monitor the individual's progress.

And then uh, finally, my, my last slide uh, so nonprofit cloud for fundraising has a number of updates uh. So we all know that uh in fundraising. It's super important to know somebody's address. Of course. But not everyone always stays in the same house. Uh, you know. Uh, people like to move around. Some people have seasonal addresses. Uh and Salesforce has now added some new standard fields to the contact point. Address objects. Uh that help to uh manage and track. Those uh changed and seasonal addresses. So that you can keep track of where your donors are and how to reach them.

Uh next, updates uh in. Th. They have updated gift entry uh. And again, this is gift, entry and nonprofit cloud, not gift entry in Npsp. So they have updated gift entry to allow you to add recurring gift commitments. Right from within gift entry. So previously you could add transactions. So that's the the specific gift. Uh, but in order to add the commitment uh for the recurring gift. Uh, that would have to be handled externally from the gift entry process.

Whereas now, as you're entering those gifts, you can enter the commitment at the same time. Uh, and then salesforce is also added uh what's called rfm. Scores. Uh, and that stands for recency and monetary. Uh and uh it. Represents the donors, ability, and their propensity to donate. Um, so it can help you to identify your top donors, or maybe the donors who you think are most likely to increase their giving, or to give more frequently.

Um. And you could also use it for uh segmenting your your uh solicitations. Um, I I can see a lot of uh really nice use cases for this. Um. So it is. Uh, it's based on or uh, it is calculated using data processing engine using information from the donor gift summary. Um, which means, which is also calculated using data processing engine. So you'll want to make sure that this.

Job is set up to run after the other job to make sure that it's uh, based on the most recent information. Um in setup uh when you're setting this up uh, you can set what is the range of scores, so is it. One to 3. Is it? One to 5, 1 to 9? Uh. Whatever makes sense, however uh detailed, you want to go with dividing up your donors. Uh, and then you also set what is the criteria. For how someone ends up with a particular score. Uh. So the uh the recency score is based on the number of days since they last donated.

The frequency is based on the total number of gifts that they have made, and then the monetary score is based on the total dollar amounts of their gifts. Um, and so uh, a lower score is better uh, so more recent or higher frequency, or more money. Um. And uh, and then the the numbers also get combined. You can see uh down below there's that composite rfm, score. Um, so that's just a uh a way to reference these 3 scores, but all within a 1 field uh, in case that uh is. Uh helpful in your reporting, or your formulas, or your uh segmentation. Anything like that. And that is all that I have. Wonderful.

Alright. I am going to um. Give everyone a moment if you had any questions to put them in the QA. Um. Since we do have our experts still here, they can answer those questions for you. And while we're taking that moment, I did want to just say, Thank you so much to Sandra and Ian. Um. Not only for contributing your time this morning, but also all of the prep. Time that you guys put into. Pulling together these highlights. Um! I know that we all really appreciate it. Um! I don't see any comments or questions coming through. I that's not true. There is a comment. Ben says, Thank you, very informative. So thank you so much. Um to all of you participants who joined us this morning, and I do help hope that you um found this information very helpful. Um, we will be sending out a recording of this, so you can revisit any of this information. Um, or any. Of the links that are provided.

And with that we will go ahead and sign off. I hope you have a great day.