Salesforce periodically releases updates that improve the performance, security, logic, and usability of your Salesforce org, but that can affect your existing customizations. When these updates become available, Salesforce shows them in the Release Updates node in Setup.
When?
- During the client onboarding process
- Prior to Salesforce Releases
- When the backlog is empty
Why?
Release Updates are an often neglected page in Salesforce set-up, but they serve a critical role in the ongoing stability, performance, and functionality. Without proper review, prior to the enforcement date, the client’s org can be impacted in ways both small and large.
Engage the Client!
Surface this with the client and track it in Jira. The client often doesn’t need to know the details of each update, but should understand what you are doing and why!
Scoping your Review:
Salesforce is used by one-person nonprofit organizations and multi-billion dollar corporations alike. Release updates get pushed to all orgs and tend to lean toward the technical and backend side of the platform. While these should be carefully reviewed before taking action, for most of our clients, this should be a relatively quick process (2-4 hours). Some things to keep in mind:
- Right-size it to the client ex. ICU Localization
- Don’t make assumptions
- When in doubt, get a second opinion
- Know what’s in your client’s org
To Test, or Not to Test?
For most updates, you have the option of testing in a sandbox environment first. This can be useful if you are concerned about possible impacts on the org. However, the majority of updates for the majority of your clients will not need this level of testing. Use your judgment.
Help: https://help.salesforce.com/s/articleView?id=sf.release_updates.htm&type=5
If you found this interesting or want to learn more, reach out a Plative consultant!
