If you are an architect or aspiring architect, one of the key challenges is to understand what features will be helpful for architects to look at. Given the volume of release readiness kit, it is hard to parse each and every feature and cloud. So what is the solution? How about leveraging the Salesforce well architected framework with EAT ( Easy, adaptable and trusted) . Let us explore the release with that point of view.

Trusted

User Access Summary – Understand a User’s Access in Under 5 clicks

Customer Need​

Admins have to make hundreds of clicks to determine what a user has access to, that is changing with the Summer release.  Now in one click they can see which user permissions, object crud, FLS, custom permissions, group & queue membership a user has!  They can view permissions of users, permission sets and public group in one click.

Reduce Risk

More Granular Access for Managing Users – Introducing new Permissions : ​ ‘Freeze Users’ / ‘Monitor Login History’

Customer Need​

Customers need granular control over user permissions. ‘Freeze User’ and ‘Monitor Login History’ perms are currently tied to ‘Manage Users’ perm, leading to excessive access on User records. There’s a need to separate these permissions for role-appropriate access.

Use Case​

An Admin can assign these permissions to a User through a Permission Set. “Freeze Users” grants the ability to freeze/unfreeze other users’ accounts; “Monitor Login History” grants access to view user login history via user detail page, setup and, using report permissions, generate reports on this data.

Well Architected framework Impact

Now admins can delegate the freeze user and monitor login history permissions to the super users and info sec teams using a permission set instead of providing manage user permissions which can lead to excess permissions.

Compliance view

Shield and Hyperforce Add ons for review

Hyperforce Based Retention Storage – Data retention capability now built on Salesforce core platform*

Customers often need to comply with data privacy laws and retain consumer data even though they no longer need it. They want to optimize storage space by moving that subset of data from Salesforce org and retain that data for a period of time in another retention storage.

Use Case​

Move Contacts older than three years out of my Salesforce org into a separate storage to minimize any risk of keeping it in the org. Retain that data for seven years due to compliance, before deleting it from the retention storage.

Well Architected framework Impact

For organizations looking at data archive solutions to meet there GDPR and other regulations, the above add on solution can be an option to explore.

Easy

Mobile Offline – Pro-code, LWC-based, offline app experience

Customer Need​

Organizations often need to ensure productivity offline.  When back online, they need to keep data consistent with regular syncs and record metering and conflict resolution.Within the Salesforce Mobile App, you can now select an offline app from the app launcher. Pro-Code solution​. Reps need to view and edit customer details while on the road

Well Architected framework Impact

With Mobile offline feature, admins can create offline apps for remote sales and service teams to access salesforce data easily which can result in increased adoption of your salesforce org.

Adaptable

Customer Need​

Customers have needed a way to manage Flows more efficiently, with features such as search, categorization, and availability outside of setup. 

Solution

With the Flow Lightning App, we have a new lightning list view that includes searching for Flows. We’ve also added custom category and subcategory fields that can be used to classify Flows by any taxonomy relevant to the customer. Additionally, the app includes a Home page that can be customized by Admins to further tailor the Flow management experience for all users in their organization. ​

Well Architected framework Impact

Admins can organize flows based on the categories of there choice which will help in long term maintenance.

Prevent Problems

Schedule-Triggered Flow- with ​Async Governor Limits

Customer Need​

Schedule-triggered flows previously used synchronous governor limits for their transactions. This was limiting to customers who had larger, more complex processes to automate.

Solution

Schedule-triggered flows (API Version 61+) will now be run with asynchronous governor limits.​ To apply these changes to existing flows, customers will need to update their schedule-triggered flows to the latest Flow API version. Newly created schedule-triggered flows will automatically be created on an applicable version.

Well Architected framework Impact

With scheduled triggered flows capable of performance similar to batch apex, admins and developers should look at scheduled triggered flows as a solution before getting into custom apex. So please update your existing flows with record triggered to meet the new API 61 plus version.

Do More

Repeaters – Enable users to create lists of data at runtime

Customer Need​

When you need to collect one or more sets of data, you may not know how many the end user will need to add. Previously, the only way to accomplish this was to manually reroute the user back to the same screen over and over again or to build a single-use component (full code). ​

Use Cases​

• Add work & education history to job application​
• Add vehicles & drivers to insurance policy

Well Architected framework Impact

With the ability to do repeaters, users in government and higher education can easily build multiple screen flows which can repeat for every individual in the family and collect information easily.

 Unlock Insights from Unstructured Data using Data cloud

Customer Need

Sometimes relevant customer information that you captured, such as call notes and chat sessions, resides as unstructured data. Now, Data Cloud Reports process unstructured data in a data model object (DMO) so you can analyze and report on it. For example, review customer satisfaction scores (CSAT) alongside their comments in surveys from the Survey Response DMO.

Well Architected framework Impact

Now customers can send unstructured data to Data cloud which would result in creating sentiment analysis and other insights from it. This will make it easy for sales and service team to review call logs and get a quick sentiment analysis of the conversations.

To summarize the key features for Architects in the Summer 24 release, here are the top 3 features which you can review the release notes to take some quick actions for your users.

1. Leverage the new summary features for users, permission sets and public groups to see if there is any unwanted access.
2. Before your point and click team goes unwieldy on flows, leverage the new category and sub category features to organize flows that can help in future maintenance.
3. If you are using record triggered flows, upgrade your flow to the new API version to get more power for your scheduled flows.

As always, you are welcome to email me at buyan@eigenx.com to me for any questions.