Summer 2022 Candy for Nonprofits Cloud (Power of Ten) Organizations (Top 5)  

It's an increasingly fast-paced world, so I'm doing my best to make ten things three things whenever possible. I couldn't get my candy list it down to three but I did focus in on 5.   

Here are the features of Summer 2022 I think will make you happiest:  

1. Dynamic Related List component for Lightning Pages. I believe this will likely be met with the highest level of applause of all the release, unless you want to use it on mobile. I got to review this product with the product owner in preview. There are one or two hitches in terms of the initial user experience (which the product owners promised to quickly resolve in a future release, but you never know). Generally you can configure which related records to show (subset filter) and which fields to show right in the lightning page builder. This is a big win for users and admins! Enhanced Lighting Grid component (free from Salesforce Labs) is still better if it is OK for you to add and manage. (Reference my Lighting Page Makeover workshop slides on Mightyforce.org if you thing it may be time for a Lightning Record Page makeover on some particular app in your org!)  As an example, you can show confirmed Volunteer hours separately from completed or canceled Volunteer hours. Same for program deliveries. It works for opportunities (open and close lists, OR part of a recurrence and singletons lists).  

2. Triggered Flows: Manage your record trigger flows and edit run-time order in a graphical explorer. Even create a new flow with relevant context from the explorer. And you can find triggered flows and open the explorer from object manager (which really makes sense). We also get entry conditions using a formula rather than just field conditions with this release! These really help make your implementation higher performing.

Everyone wants Salesforce to answer an architectural question of should there be just one flow per object. Clearly they just silently answered the question with the record triggered flow explorer... why would we need a run-time flow execution order manager otherwise? One Process Builder per object was never a good idea. It was a convenient answer to avoid b*nging into performance limits of the horribly slow Process Builder engine. My advice: don't repeat yourself in design (google Keep it D.R.Y.), always meet your needs based on user stories as best you can, and consider your total cost of ownership including maintenance. That very clearly means multiple flows per object. Performance orgs also need to make full use of entry conditions on all the flows.   

Everyone also wants Salesforce to say how soon we need to convert workflows rules and process builders to flow. I don't think you should (you can't likely do them all yet anyway) UNTIL you need to modify ones of the business processes implemented with the Process Builder and Workflow Rules. Then consider upgrading the related items and build a more modern streamlined implementation. Don't repeat yourself, consider the whole user story set, and opt for lower cost of ownership. Conversion will get easier and easier over time. But don't ignore it. Do it when it makes sense. (Reference my Technical Debt presentation on mightyforce.org if you are overwhelmed in this area.)  

3. Flow debugging: you can record a successful debug and test future modifications to see if they get the right answer answer! I suspect this capability will only grow over time. It will be a huge win for admins. The debugger has come a long, long way in the last year. If you don't use it, it's time. And soon it may be capable of double checking your work when you tweak a flow!  

4. Screen Flows: Name and address support in screen flows using record fields model.  Collapsible sections in screen flows. Both of these mean better user experiences and fewer clicks for flow admins.  

5. Reports Browser Release? After limited and closed pilot last time, I debated whether to list this item. (I requested it on day one but but was turned down with a declaration that they had enough participants.) The report browser is in beta for browsing based on object filter. IF they get it right and bug-free, it's an area really ripe for improvement. It might impact your users on day one, so I think you should be aware either way. It expect it can be disabled in final release.  

Another thing to note: NPSP is bringing out it's new release for the first time as part of the Summer release. Unfortunately, they have not yet to be included in the release note documentation like other verticals. There is a new release of NPSP and  PMM, both of which I consider valuable additions to Power of Ten. V4SF and OFM don't appear to have new releases, unfortunately. Hoping it all gets folded in since we've moved to this new schedule. In for a penny... in for a pound... and all that.  

NPSP 3.217: The big item I see that may many happy are some automatic fields that summarize onto the contact and account the status of the most recent recurring donation (current, lapsed, former). And the NPSP Data Import got some needed love. It now supports tribute field import and you can now import selected rows from the list view rather than all or nothing.  

PMM 1.29: PMM keeps getting better for those who have to enter data. You can now take attendance rapidly with a new component. So now you can enter a program delivery individually, in bulk to searched for groups, for a scheduled session, or as attendance. And there is now a way to limit the interface to show participants who are classified as active.  

Near as I can tell, no update news on OFM, V4SF, and Elevate, which is not free but is pay-as-you-go workable product for many small nonprofits who receive Power of Ten.  

One very important thing to note: I don't consider Slack a Power of Ten program as their license grant for nonprofits is much more narrowly defined than Power of Ten. I expected Salesforce to adjust this policy but it's been more than a year and they haven't. I'm disappointed in Salesforce for this! My organization is among those who can't receive grants or reductions on Slack as a non-profit. They choose to exclude quite a lot of the nonprofit world on the basis of several criteria. It simply makes no sense in the context of all their other work on diversity and inclusion to divide the nonprofit world in this way. But it's their product. Just not one I can use or recommend using. We're all better together and reducing the Power of Us makes no sense. I encourage everyone to continue to bring this to the attention of Salesforce.   

Orchestrator remains a very complex beast and pricing just isn't clear for the value-proposition win at nonprofits, especially small ones. It is sometimes described as a replacement for approval processes, but honestly you'd have to be crazy to support the cost of ownership and licensing for this purpose. Orchestrator offers a way to make a user run a flow at the right time. This is it's truly unique ability un the Salesforce standard product line. I imagine there are other and better ways to do that, frankly. 

 @Nonprofit Hub @Nonprofit and Education MindShare #Summer22Treasure #Release Readiness #Nonprofit @Nonprofit Success Pack  @Education Hub

 @Hub Heroes @MVPs & AppExchange All Stars @Salesforce.org MVPs 

@Program Management Module (PMM)