If you are an architect in the Salesforce ecosystem wondering what features will be of value to you and your customers, my blog will help you pick the right feature based on the Salesforce well architected framework and my own extension to it. In addition to the framework, which is based on EAT ( Easy, Adaptable, and Trusted), I look at features with my own framework (STRAP), which will help you to identify features that can Scale (do things faster), Time savings, Reduce costs, Achieve more, Prevent problems.

Trusted

User Access Summary

Following the user access summary feature, now an admin can easily tell where a user is getting that
permission from the user record. When an admin wants to understand how a user is getting access to a specific permission, he can click the below screen to see the permissions.

Why is this value

An admin or architect can quickly understand what objects and data a user has access to and prevent problems by resolving unwanted permissions.

Object Access Summary

Understand how access is granted to an object directly from object manager
directly from object manager see which perm sets, permset groups, and profiles are granting access to an objectand the level of access.
Why is this value
When an admin wants to understand which perm sets, perm set groups, profiles are granting access to an object

Easy

Enhanced User List View with Inline Edit
The user list view is moving to lightning and now has inline edit. The user list view needed modernization.
to easily manage their users, find the right user, and
quickly edit a user.
Why is this value
This makes it easy for users to edit data in bulk than running reports or generating csv data imports.

Compliance

Database Encryption (TLE)
Shield customers can now transparently encrypt the entire core transactional database with a tenant-specific keys. Customers want to encrypt more data (all fields, apex, and custom metadata) in a transparent manner. It also provides an option to encrypt transparently without tradeoffs.
Why is this value
Achieve security compliance in part by encrypting more data and maintain encryption at rest status. No need to encrypt all fields in Salesforce.

Get things done faster(Scale)

Parallel Processing with Platform Events
Have multiple triggers processing events. Customers are spending too much time waiting for their platform events to process within Salesforce. Users can now create up to 10 triggers and setup each trigger to process only a subset of events that they receive at the same time, greatly reducing the time
needed to process a large number of events.
Why is this value
Customer is using platform events to generate orders within Salesforce. After
the customers new sales push the number of platform events that are incoming
need to be processed faster to to meet the demand.

Generative Formulas for Flow
Generate formulas using natural language prompts and AI . Admins are often mid-stream building their flows when they need to write a formula. Tricky formula syntax means that admins are
constantly context switching to brush up on their formula writing. Newer flow builders especially struggle with learning how to write a formula and understanding the syntax rules.
Why is this value
An admin is building out a flow that requires a formula resource on a decision element. Instead of Googling the right syntax, they simply enter a prompt and let Einstein write the formula for them.

Prevent problems

Pub Sub API can now keep track of the last processed replayID so the customers do not need to
write custom code to keep track of where they left off a subscription.
Use managed subscriptions (beta) to keep track of the events a subscriber client consumed and
resume a subscription from where it left off after a client disconnects. The subscription starts
from the last Replay ID that the client successfully committed on the server, therefore, there is
no need to write custom code to keep track of the latest event consumed.
Feature is auto enabled in UE, EE, Developer & Performance editions orgs.
Why is this value
Customers will now be able to use “ReplyId” option over “Earliest” without any extra steps,
stopping the pattern that wastes processing on de-duplication and causes customers to hit their
event delivery entitlements unnecessarily on using “Earliest”. This will help in preventing problems caused due to network issues and exceptions and use the last replay id to process data.

Do More( Gen AI Features)

Einstein Knowledge Creation
AI Generated Knowledge Drafts from Service Interactions. Creating and editing knowledge articles can be time consuming for agents and knowledge managers. However, a complete and up-to-date knowledge base is crucial for customer self-service and agent productivity. Based on a customer conversation, Einstein Knowledge Creation drafts fluent, relevant knowledge articles that agents review, edit, and save. In Winter ‘25 we will beta Revise with Einstein which allows users to use AI to edit their
knowledge articles for style, tone, or format. We have introduced 3 out-of-thebox
prompts (grammer, readability, conciseness) and a customer can create
their own prompts in Prompt Builder for AI editing purposes.
Why is this value
As an agent, I’ve created a Knowledge Article Draft (either manually or with
Einstein), but I want to make it more easy to read – I select Revise for
Readability and AI will update the format of my article to account for readability. Based on the prompt , more knowledge articles can be created using Einstein1 helping organziations to save knowledge
Save Costs

Duplicate Prospects Report
Help keep a clean prospect database by identifying duplicate records. Identify duplicate records that may be causing confusion and resulting in unexpected processing.
Why is this value
A marketer finds that a certain email has over 100 duplicate records, all with slightly different information. To help keep the database clean, she deletes 99 of the records and keeps the most accurate
one in their prospect database for marketing.

To summarize Winter 25 with my framework and salesforce well architected framework, here are top 3 key aways for you.

1. For folks worried about compliance and security, try to leverage the tenant level encryption feature now available with shield to meet encryption at rest requirements.
2. Increase your adoption with your salesforce org by turning on inline edit and display fields based on user personas on the record highlights panel
3. Prevent problems by leveraging pub sub replay id to avoid duplicate data and ensure your integrations can handle duplicates.

As always you are welcome to reach out on questions and feel free to email me at buyan@eigenx.com