As 2020 is coming to an end we would love to share our 2 favorite Salesforce Releases. Jan Youlton, one of our very own Salesforce Developers, is always up to date with the latest Salesforce news and the best man for the job. He picked the dynamic forms and record-triggered flows and tells you why. Let’s zoom in:
This feature really needs no introduction. Dynamic Forms was the number 1 requested feature for as long as Lightning Experience has been around, and for good reason! Let’s sum up what Dynamic forms is and why you should be excited. Shortly put, Dynamic Forms is an expansion of Lightning Record Pages which allows us to control record fields on this level instead of the classic Page Layout. This means that we no longer need to create multiple Page Layouts for different profiles because we can determine field visibility with just the Lightning Record Page. It also means that we are free of the “Details” component and can place individual fields wherever we want on the page. Unfortunately, this is only the first version of this feature, which means a few drawbacks shouldn’t surprise us. As of now there is no support for Standard Objects or for any layout in Mobile. We also need to keep using the conventional Page Layouts to control Related List access and their columns. However, Salesforce is already working on ‘Standard Object support’ for upcoming releases and we can assume they are working on other improvements too. This feature is already a big step forward in its current form though. If you want to learn more about Dynamic Forms, check out the official Salesforce Youtube channel where you can watch a showcase on the feature.
Salesforce is on a mission to make the Admin as independent as possible by providing declarative building blocks. Functionality like Lightning App Builder, Process Builder and Flows ensure that knowledge of coding is not required as much as it once was. The Record-Triggered Flows are another step in the right direction. Previously, if we wanted to perform additional logic or data operations during the creation or update of a record, we could make use of the Process Builder and configure an auto-launched Flow. This was still limited compared to the Apex Trigger because there was no option to perform the logic before saving the original record or on deletion of this record. Introducing Record-triggered Flows, a Flow which doesn’t need Process Builder and will be executed before or after creation, update or deletion of a record, just like the Apex Trigger. For Admins who are struggling to see why these triggers are beneficial, imagine wanting to make a change to a record’s field depending on the modification of another field on that same record. We could just perform 2 updates on this record but why not execute both actions in one update? Especially once our environment has many workflows or processes, these additional updates can become quite a big waste of time and resources so the Before Record-triggered Flow is effectively a much cleaner solution. One added benefit of an After Record-triggered Flow would be the ability to perform actions after a record has been deleted. There are many more use-cases for these types of Flows, which you can now discover for yourself.
Mark your calendar now for the next Salesforce releases, which are right around the corner. Stay up to date about all releases, product updates & more. Subscribe to our newsletter on our homepage!