Wednesday, 30 September 2020

Avoid hitting maximum CPU time Limit error in Salesforce Using Before Save flows

Hi Folks,

The trending word is COVID-19.

Do you want me to talk about this? Naaah! Tired of Hearing CORONA.

Let's get to the business people. Before SAVE FLOWS. Yes, you read that right. Salesforce has introduced an awesome features and added one more vanilla and chocolate for the team called Functional/Implementation Consultants(IC's). Yeah, in Summer 20. 

For functional people working in Salesforce, now they have a new weapon. Flows can work before insert and before update calls.

There are a lot of benefits of using flows rather than using the trigger. Let's take them now:-

  1. Less Code and more config.
  2. Update New and Changed Records 10 Times Faster by Using Before-Save Updates in Flows.
  3. Save CPU time.  HOW??
As per salesforce, this vanilla feature(Before Save Flows), actually runs prior to the before triggers and it saves the round of assignment rules, auto-response rules, workflow rules, and other customizations that take time to execute.

Well, don't get excited, before you implement for your client read the considerations of flows.

https://help.salesforce.com/articleView?id=000314438&language=en_US&type=1&mode=1

Enjoy and keep learning more every day! 




1 comment:

  1. Great! You have shared your interesting ideas with us. Feel free to contact us for...

    Hire certified Salesforce developers who have expertise in customization, configuration, integration, app development, maintenance, and assistance.

    ReplyDelete

oAuth Use Case -  Headless API Explained in the Easiest way Wondering why? and When we use the Headless API flow Use case example: Imagine a...