Lightning Process builder

Advertisements

<

Tag: Lightning Process builder
- Getting Started with Process Builder – Part 91 (Ride the 10 Horses Carriage to Become an Automation Expert in Style!!)
  
  Posted at 10:45 AM by Rakesh Gupta, on November 14, 2018
  Process Builder is a like a double-edge sword – on the one hand, it is one of the most powerful tools provided by Salesforce to implement business automation declaratively; on the other hand, if one implements process builder sloppily then, it may turn into a nightmare by flashing errors like SOQL 101 error, CPU timeout, etc.
  
  Let us first understand the role Process Builder plays in streamlining businesses processes and procedures. First and foremost, Process Builder helps businesses save time, as well as money, by enabling users to implement solutions quickly. Implementation of Process Builder is straightforward – you create a Process; test it; and then, use Change Set, to deploy it to Production. The best part is, you do not have to write test classes for your Processes or Flows.
  
  We all desire to be on the right side of the sword! The question is, how? How can one learn to adhere to best practices to implement process automation declaratively?
  
  Well, look no further! For, 100+ blogs, on Process Builder, are on Automation Champion alone.
  
  To get you started, this article summarizes best practices and strategies to implement Process Builder processes.
  
  #1 Always! Plan before you build
  
  The key to successful project implementation is – design first and then implement. Process Builder is no different – the same logic applies here too. I have seen many cases where people start creating process(es) as soon as they get requirements. As a result, more often than not, users end-up getting some weird error messages.
  
  I am a seasoned trainer. Time and again, I have to remind my trainees not to rush into implementing the process as soon as I give them requirements! Furthermore, I get number of requests from the community to help them identify errors in their process builder. My first question to them is, please show me your design. Almost always, their response is – Design? Huh? What? I can show you my process, why do you need to see a design? So, please, save time and sanity – Design first!
  
  Reference – Getting Started with Process Builder – Part 79 (Auto Remove Managed Package License from a Deactivated User!)
  
  Here are my suggestions – once you get the requirements do the following:
  
  Advertisements
  Share this:
  Twitter
  LinkedIn
  Facebook
  Pocket
  WhatsApp
  Reddit
  Tumblr
  Pinterest
  Skype
  Like this:
  Like Loading...
  Posted in Process Builder | 0 Comments | Tagged adm 201 certification, Automation Expert Salesforce, Lightning Flow, Lightning Flow error email, Lightning Process builder, One process per object, Process Builder Best Practice, Process Builder Design patterns, Process builder use case, Salesforce admin certification, salesforce Admin exam, Salesforce Freelancer, Salesforce Independent Architect, Salesforce Online Training, Salesforce Training
- Getting Started with Process Builder – Part 87 (Untangling the Perplexing Filter Logic of ‘Updating Records Action’!)
  
  Posted at 10:30 AM by Rakesh Gupta, on April 17, 2018
  Check out my previous articles:
  In the aforementioned articles, I have discussed few advanced concepts that will help you to optimize your process. If you didn’t get a chance to read it yet, do it now! It will significantly improve your knowledge of Process Builder. Once you master the art of leveraging process builder, you will be able to easily create an optimized process!
  
  In this article, we will unravel a known limitation of process builder by understanding the logic behind using filter conditions in Update Records action.
  
  As far as Update Records action goes, currently, as of (Spring’18 release), only the following two scenarios are possible in process builder:
  1. When you use a field once, while filtering Update Records Action, then, the process builder will automatically use an ‘AND’ condition between the fields. For example, as shown in the following screenshot, both the fields (Rating and Source) are used once – and therefore, an AND condition is automatically used between them.
  However, there may be times when a user may encounter a scenario where, s/he may need to use a field twice, as shown in the following screenshot:
  
  In the above scenario, the Source field is used twice. In such a scenario, the process builder automatically creates an OR condition between first and the second use of the Source Field.
  
  Remember, everything happens automatically so, you do not need to define anything.
  
  Now what happens if I use three different fields, where each field is used only once, to define my filter as shown below?:
  
  In this case, the process builder will use an ‘AND’ condition between all the three fields because they are all used only once while filtering the Update Record Action, as shown in the preceding screenshot.
  
  Got it?
  
  But, now, what if I want to define my own criteria? – as shown in the following screenshot:
  
  Nope! Can not do it!
  
  As mentioned above, one of the limitations of the process builder is that, you cannot write own filter logic in Update Records action – as shown in the preceding screenshot.
  
  However, we are Salesforce Ninjas and that means, we do not accept ‘can not do it’ without a good try/fight!
  
  So, wait for a second, and think! Is it possible to solve the above business use case using process builder? – if your answer is still no, or even maybe, – then, read-on! It is possible that when you reach at the end of the article you may hear yourself saying – Yes, it is possible!
  
  Always remember, impossible can transform into I’m possible if you don’t give up! That is exactly what I am going to show you how to do via this blog!
  
  Let us work through this via a business use case
  
  Business Use Case
  
  Edward Backhouse is working as System administrator at GurukulOnCloud. He has received the following requirement:
  
  Whenever an Opportunity is created/updated with a Stage value prospecting then, update the Account Description field to Yes I Can!, only if, the Account fields meet the following conditions:
  
  Account Rating = Cold AND Status = Active
  
  OR
  
  Account Source = Partner
  Share this:
  Twitter
  LinkedIn
  Facebook
  Pocket
  WhatsApp
  Reddit
  Tumblr
  Pinterest
  Skype
  Like this:
  Like Loading...
  Posted in Process Builder | 5 Comments | Tagged ADM 201, adm 201 certification, Automate process in Salesforce, dev 401, Filter logic for Update Records, Filter logic for Update Records Action, filter logic on Updating Records, filter logic on Updating Records Action, filter logic on Updating Records Process Builde, Lightning Process builder, Logic on Updating Records Action, logic to filter record in process builder, Platform App Builder, Platform App Builder Exam, Process Automation in Salesforce, Process Builder, Process Builder examples, Process Builder Sales Cloud, Process Builder Service Cloud, Process builder use case, salesforce Admin exam, salesforce certified developer exam, Salesforce Freelancer, Salesforce Independent Architect, Salesforce Independent Consultant, Salesforce Online Training, Salesforce Platform Developer I Exam, Salesforce Training
← Older posts
- Search
  
  Search for:
  
  Sort by
- Upcoming Trainings
  
  Salesforce Admin Certification
  Salesforce Platform App Builder Certification
  Pardot Specialist & Consultant Certification
  Visual Workflow & Process Builder
- Sponsor #1
- Sponsor #2
- Salesforce ID Converter Build on Visual Workflow
  
  Converting 15 digit to 18 digit Salesforce ID
- Buy My Book
- Buy My Book
- Buy My Book
- Recent Posts
- Blog Archives
  Blog Archives
- Categories
  Categories

%d bloggers like this: