If you are an architect, the well-architected framework is the guideline for salesforce solutions across the enterprise and business units. So with this framework, here are some key winter 23 release features that you need to look at as an architect to make decisions for your org. As an architect, it is important to design solutions that are trusted, easy, and adaptable for your clients.

Trusted

Evaluate your Experience Cloud site security

We’ve enhanced Health Check settings to now include the number of objects that guest user profiles have Read and Edit access to in the Informational Security Settings.

Why this feature is a must for architects?

As a key stakeholder for security in your org, it is important to review the CRUD permissions for objects that are accessible by guest users who are anonymous users in your communities and salesforce site. With the debacle of objects exposed to guest users, it is very important that as an architect you recommend your admins run the health security check and identify the objects that are exposed to guest users. The best practice is to lock it down by making it private or read-only at the most.

Adaptable

Upgrade to Dynamic Forms on many LWC-enabled standard objects

Dynamic Forms is now supported on hundreds of LWC-enabled standard objects. With this feature, you can enhance page performance and build highly dynamic, flexible pages for your users, showing them the right data at the right time. Previously, you could use Dynamic Forms only on custom objects and a handful of standard objects.

Note: Dynamic Forms is supported for most but not all standard LWC-enabled objects. If you open a record page in App Builder and you don’t see the ability to upgrade to Dynamic Forms, that’s your indication that it’s not supported. For example, the Note object doesn’t support Dynamic Forms because it has a fixed layout. Dynamic Forms isn’t supported on objects that aren’t LWC-enabled, such as Campaigns, Products, and Tasks.

Why this feature is a must for architects?

As you prepare to move your security from profiles to permission sets, there is a key question what happens to the page layout assignment that is going to be in the profiles?

Salesforce has made it clear that they are not going to move the page layout assignment to permission sets because it will cause a conflict with one user who has 2 permission sets assigned and has 2-page layouts on each permission set assigned. This will cause a conflict and hence Salesforce’s decision makes sense. Start planning to move all your page layout assignments to dynamic forms. Imagine the number of record types and page layouts you will save on your objects !!!

Easy

Make your screen flows reactive! (GA)

Create single-screen apps and a better user experience with minimal screens for your screen flows by making them reactive! This was Beta in the Summer ’23 Release and is now GA. Configure screen-supported standard screen components or your custom Lightning web components to react to changes in other screen components on the same screen, rather than placing the reaction on the next screen.
To enable for use of screen flows configured to run on API versions 57.0 and 58.0, select Enable Reactive Components for Screen Flows running API Version 57 and 58 on the Process Automation Settings page in Setup. Note: The Enable Reactive Components for Screen Flows running API Version 57 and 58 is set to expire in Winter ’25.

Why this feature is a must for architects?

This is one of the coolest features now available for admins and architects to use in your org. You can see below the screenshots of what you can do with this screen flows. This will help you to enhance your user experience and help your users to dynamically select radio buttons, and run price comparisons and selections based on dynamic components.

To summarize, as An architect, here are the top 3 features that would be of value to you to implement in your org.

1. Run a health security check on guest users and reduce your risk by restricting access to objects for guest users that are not needed.
2. Start advising your teams to use dynamic forms and move away from old habits of creating unnecessary page layouts.
3. Wow, your users with reactive flows that are point and click and help your users to reduce the number of clicks.

As always you are welcome to email me at buyan@eigenx.com for questions and I would be happy to discuss further with you.