We’re super excited about the new Salesforce Summer ’20 release which is just around the corner. It’s going to be packed with lots of dynamic new features and enhancements to help make the platform even better.
To help you make the most of that important sandbox preview, we’ve put together a quick list of the six most impactful changes in Salesforce Summer ‘20: what they are, how they might affect your org and how to make sure that your team is ready.
Just remember that Summer ‘20 is still in preview, so these features aren’t yet generally available (GA). To get access, check the sandbox preview instructions and plan your sandbox refreshes accordingly. Remember that details of the release may still change before the release becomes GA.
If you’d like to see everything that’s coming out in Summer ‘20, take a look at the official release notes here.
Let’s take a look!
#1: Record Changed Flows and Platform Event Flows
These two great features are now GA and your Salesforce team will want to start taking advantage of them once Summer ‘20 becomes available.
Record Changed Flows are important because previously you had to use the Process Builder to invoke a flow on record save. The added ability to execute flows before the Save action now gives this declarative feature more parity with Apex Triggers. (Note there are still plenty of more complex scenarios where you still need Apex triggers.)
Platform Event Flows are important because it allows admins to configure custom events and invoke flows to execute them. This can be based on any custom action rather than waiting for a record save. This allows communication between multiple declarative and code components which do not rely on a record being updated or saved first. Impressive!
What’s the impact?
Once Summer ‘20 is released, your Salesforce team will want to start taking advantage of these updates and may look at reworking existing Apex Triggers, Process Builder and Flows to follow the new model. For Provar customers, the good news is that you can use your Provar tests to retest these changes to give you confidence they are working as expected. We also encourage you to check if existing functionality is being extended using Flows to ensure your test coverage reflects the whole user journey and business/data processing rules.
#2: Dynamic Forms and Dynamic Actions
These are two great new features previewed at Dreamforce. In Summer ‘20 these features are still in preview mode and are limited to custom objects only. For more information and to get early access in a pre-release org, take a look at this Salesforce blog.
Dynamic Forms are a big step forward for Lightning record pages, allowing admins to configure multiple record detail fields and sections inside the Lightning App Builder. This is (unusually) a non-GA preview feature and initially only available on custom objects, but it’s great news for those looking to avoid the development of unnecessary custom components. One of the most exciting features of this is the new ability to dynamically display fields, e.g. if picklist value A is selected, display fields 1, 2 and 3.
Dynamic Actions are a similarly exciting feature as admins can now customize the action buttons that appear based on specified factors such as record field values or the user’s device type. At long last users should not be faced with a tempting “Request Approval” button if there is no process to execute the approval!
What’s the impact?
Both of these new features represent a small paradigm shift in how Lightning record pages should be approached and/or tested. Dynamic Actions mean new rules for field visibility outside of field permissions or page layouts.
For Provar customers, you’ll need to review your existing tests when this feature becomes GA and your Salesforce team begins to adopt it. We’re working on a new solution to help you test both Permission Sets/Groups, Dynamic Forms and Layouts so you can validate your org deployments. This will eventually supersede the Extract & Compare Layout options.
#3: Respect target values in formula field hyperlinks
This change to the working of formula field hyperlinks means that if you have formula fields that use the HYPERLINK function, the target value for that hyperlink will now be honored in Lightning, whether it’s explicitly configured in the formula or set by default. Previously, Lightning Experience has ignored the target value when attempting to open the link.
What’s the impact?
This may seem like a small change but it will become the default behavior in Summer ‘20 so you should test any affected fields as soon as you can. Hyperlinks created with a target location populated may no longer work as expected. If you have Provar tests that interact with hyperlink formula fields, you might need to amend these to select the correct parent window depending on the target value.
#4: MyDomain URL changes
Another change in Summer ‘20 affects your Salesforce URLs. Summer ‘20 is enforcing two critical updates that were made available in earlier releases. These updates affect orgs that have a deployed My Domain.
Firstly, Salesforce is removing instance names from MyDomain URLs for sandboxes. For example, MyDomain–SandboxName.cs5.my.salesforce.com will become MyDomain–SandboxName.my.salesforce.com. This update was first made available in Summer ’18 and is enforced in Summer ’20.
Secondly, Salesforce is removing instance names from Visualforce, Experience Builder, Site.com Studio, and content file URLs. Once this update occurs, URLs that include the instance name will automatically redirect to the new host name. This update was first made available in Spring ’18 and will be enforced in sandbox orgs on Summer ’20 on July 11, 2020. The update won’t go live in production orgs until Winter ’21.
What’s the impact?
Your team should check for hard coded URLs in configuration or code that may break as a result of these changes. Provar customers can use their existing tests to help identify where these breakages are occurring — as well as validate fixes put in by their admins and developers.
#5: Lightning community action overrides
In Summer ‘20 community admins can now override standard actions in Lightning communities. This allows a community to respect the same Lightning record action overrides used by internal users, such as View, New or Edit actions.
This could be a very helpful update if you want to apply the same action to a Lightning community as you currently use in Lightning Experience. We’re hoping for a future enhancement where different actions can be applied in the community, as applying the same actions for internal and community users won’t suit all use cases.
If you adopt this new feature, remember to test that the override behaviour works as expected for your community users. For Provar customers this means you may need to modify your test cases to make sure they cover the right layout.
#6: Skip identity verification
Finally, here’s one new feature that could be exceptionally handy. There is a new permission coming called Skip Identity Confirmation at Login that admins can assign to discrete users. This allows highly trusted users to log into Salesforce from a new device without verifying their identity with a second factor, such as an SMS code.
For Provar customers, this could be helpful when running tests on remote servers or alternatively for granting access to a support rep to help troubleshoot issues effectively. This could potentially save you from having to whitelist IP addresses or jumping on a call to pass on the security token. It’s evidently not recommended for normal use, however, and make sure you have planned careful use to ensure the security of your org. But granting it to a specific user could be more secure than adding an IP address to the profile as a whole.
Want to learn more?
If you’d like to learn more, why not join our upcoming webinar What’s New in Summer ’20? In this webinar on Thursday June 4 we’ll highlight the most impactful Summer ‘20 changes that you’ll need to be aware of, share the best of Provar’s latest features and give you a sneak peak of what’s coming next on the Provar roadmap. Click here to register.