3 new salesforce glide capabilities to shout approximately in summer ‘20
Waft designer changed into changed by using the brand new go with the flow builder lower back in spring ‘19. It changed into a welcome improvement for folks who have been used to building in any of the new lightning builder gear (method builder, lightning app builder, even the community builder) and felt quite acquainted from the moment it launched. Click For Salesforce Implementation Partners
With its simplified toolset and cleanser ui, it had laid the principles of what might turn out to be the most effective declarative automation tool that income cloud had to offer. Every time the salesforce launch notes are posted, I get straight to analyzing them due to the fact i recognize that there could be new functions for salesforce flows – the summer season ’20 release, of direction, has new enhancements that I want to shout about!
1. Earlier than/after dealing with in drift triggers (‘report changed’ float) we currently saw flows inherit a capability from apex: the capability to behave as a cause. You can pick out standards which a float could be known as routinely, and cope with statistics. With summer ’20, we’re seeing but another step in glide turning into a completely-fledged declarative opportunity to apex: the capability to address before and after activities. This is a large step to go with the flow and could provide even more energy to declarative users. Instead of being a vehicle-released glide, this will now be referred to as a ‘document modified’ waft (one in all a number of of latest float sorts).
2. Glide loop variables are mechanically created
this is a big non-public peeve of mine! In every new release of glide builder and designer to date, we’ve needed to create our loops, then create a separate loop variable useful resource. It’s just an extra step that felt so pointless. Salesforce has addressed this by means of developing this resource routinely while you create a loop. Allow’s say you had a loop known as ‘lead_loop’, go with the flow builder will mechanically create a aid referred to as ‘contemporary object from lead_loop’. The end result? It'll prevent a ton of time, and make it a whole lot less difficult for brand spanking new go with the flow customers to learn how to use the device.
3. Rollback mode in waft debugger
with rollback mode enabled to your go with the flow debugger, any adjustments which might be done by way of your flow received be stored whilst you check it. This facilitates to hold your facts clean and tidy whilst you create and test your flows. This is one of those tiny changes in order to have a big impact. Sincerely take a look at the box on the first display screen of the debugger to enable it, and your database will remain one hundred% intact.
With its simplified toolset and cleanser ui, it had laid the principles of what might turn out to be the most effective declarative automation tool that income cloud had to offer. Every time the salesforce launch notes are posted, I get straight to analyzing them due to the fact i recognize that there could be new functions for salesforce flows – the summer season ’20 release, of direction, has new enhancements that I want to shout about!
1. Earlier than/after dealing with in drift triggers (‘report changed’ float) we currently saw flows inherit a capability from apex: the capability to behave as a cause. You can pick out standards which a float could be known as routinely, and cope with statistics. With summer ’20, we’re seeing but another step in glide turning into a completely-fledged declarative opportunity to apex: the capability to address before and after activities. This is a large step to go with the flow and could provide even more energy to declarative users. Instead of being a vehicle-released glide, this will now be referred to as a ‘document modified’ waft (one in all a number of of latest float sorts).
2. Glide loop variables are mechanically created
this is a big non-public peeve of mine! In every new release of glide builder and designer to date, we’ve needed to create our loops, then create a separate loop variable useful resource. It’s just an extra step that felt so pointless. Salesforce has addressed this by means of developing this resource routinely while you create a loop. Allow’s say you had a loop known as ‘lead_loop’, go with the flow builder will mechanically create a aid referred to as ‘contemporary object from lead_loop’. The end result? It'll prevent a ton of time, and make it a whole lot less difficult for brand spanking new go with the flow customers to learn how to use the device.
3. Rollback mode in waft debugger
with rollback mode enabled to your go with the flow debugger, any adjustments which might be done by way of your flow received be stored whilst you check it. This facilitates to hold your facts clean and tidy whilst you create and test your flows. This is one of those tiny changes in order to have a big impact. Sincerely take a look at the box on the first display screen of the debugger to enable it, and your database will remain one hundred% intact.
Comments
Post a Comment