Download to read offline
Uploaded byRichard Clark
Getting to Grips with Process Builder
The document discusses the transition from Salesforce workflows to Process Builder, outlining its benefits such as better control over execution order, easier maintenance, and additional declarative options. It provides examples of workflows suitable for migration and offers considerations for businesses contemplating the move. Additionally, the document emphasizes the importance of ensuring that any new requirements are met and that testing is conducted with tools like Provar before deploying changes.
More Related Content
Similar to Getting to Grips with Process Builder
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
Getting to Grips with Process Builder
- 1. Getting to Gripswith Process Builder How to migrate your workflows to process builder richard.clark@provartesting.com, @RichClark808 Richard Clark, Head of SF Engineering at Provar Testing
- 2. This presentation maycontain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Statement under the Private Securities Litigation Reform Act of 1995 Forward-Looking Statement
- 3. Richard Clark Head ofSalesforce Engineering Co-organiser London SF Dev UG @RichClark808 http://ProvarTesting.com
- 4. About Provar Highly MaintainableTest Cases • Binds to Salesforce Metadata to support Classic, Lightning and Mobile Testing in a single test Point and Click Test Creation • Easy to use Test Builder to record UI interactions, no Selenium knowledge required Aligned to the Salesforce Roadmap • Keeps test cases current and working across Salesforce releases Continuous Integration • Provar tests can be executed under ANT and integrated into your ALM and DevOps processes Provar is the automated testing tool for Salesforce
- 5. Why Migrate YourWorkflows? 1.Control order of execution 2.Easier to maintain 3.Additional declarative options 4.Versioning & Rollback 5.Centralise touchpoints (GDPR) 6.Future of Salesforce
- 6. Example 1 Follow upEmail Survey Existing Workflow “High Value Customer Survey” ● Case Create or Update ● Case Closed AND Annual Revenue > $10m ● Action: Send Survey Email 7 days after case closed date
- 7. Demonstration 1 Migrating aworkflow to Process Builder
- 8. Demonstration 1 Migrating aworkflow to Process Builder
- 9. Example 2, 3,4, ... Set target resolution date based on Support Plan 3 existing Workflows Case Create ● Account.Support_Plan = Premium, Target Resolution = NOW() + 1 ● Account.Support_Plan = Standard, “ “ = NOW() + 2 ● Account.Support_Plan = Basic, “ “ = NOW() + 5
- 10. Demonstration 2 One processto rule them all...
- 11. Demonstration 2 One processto rule them all...
- 12. Does it work? Drumroll please...
- 13. Which Workflows shouldI migrate ? Avoid ● Objects with single workflows, unless you want to change the actions ● Objects with bulk creates/updates ● Workflows with Outbound Messages Consider ● Objects with new workflow requirements ● Objects with multiple workflows already ● Objects where you need to control the order How to proceed on your PB trail
- 14. Achieve more withProcess Builder ● Available to customers using Professional Edition ● Chatter for Internal Messages ● Automate Approval Request Submissions ● Update Multiple Records and any Related Record ● Quick Actions ● Invocable Processes, Apex and Flows Some additional Use Cases to consider
- 15. Gotchas Be aware ofthe following ● Debug log, Chatter Posts & Error Email ● Flow trigger means PB or Flow ● Record visibility & security ● IsNew, IsChanged, PriorValue() and recursion ● Values are evaluated at the start: ○ Criteria cannot fire based on earlier changes; use recursion checkbox ● Process versions unique to the Org ● Activate after deploying ● Workflows & Processes share the same Limits
- 16. And finally... Last butnot least
- 17. Further Reading ● SalesforceBen: WF Rules vs PB : http://bit.ly/2rgdxY2 ● SFDC99 : Workflow, PB, Flow, or Apex? : http://bit.ly/2rfm0e4 ● Trailhead Trailmix: https://bit.ly/G2GwPB Time to take that photo on your phone...
- 18. Summary - Rememberthe following Getting to Grips with Process Builder Trailhead https://bit.ly/G2GwPB Implement new requirement Develop Process Test (with Provar!) Identify Object to migrate Deploy & Activate Iterate
- 19.
Editor's Notes
- #3 Obligatory FLS slide, it is actually relevant for one item I’ll talk about today, the Lightning:Messages base component.
- #4 As I said, my name is Richard Clark, I’m the H of SF Eng at Provar plus I’m also one of the co-organisers of the London SF Dev User Group, where we’ve just exceeded 2000 members, and a regular attendee of the London SF Admin User Group.
- #5 Just a quick word about the company I work for, Provar Testing and our product Provar. If you’re interested in learning more come speak to myself or my colleagues at any time today. You’ll see us wandering round in our matching blue and pink t-shirts, we also have some to give out to any existing customers or anyone that signs up for a demo.
- #7 This is quite a simple example, but as you can see we would need a workflow for every different Customer SLA category or rule with this solution. It’s not uncommon to start like this and find after a few months you have 20 or 30 workflows just to set the Target SLA! Talk through and ask the questions "Which one executes first", “If the Standard one fires, why does the Premium one also fire?”, and "Are your users fed up of getting emails from Salesforce, do they ignore them? How about those emails you send to tell them a record is ready to submit for approval? What if I tell you PB can eliminate all this for you?
- #8 So let’s see how we can do that same business logic in Process Builder. https://provardemo--summer18.lightning.force.com/one/one.app Show the Workflows being replaced. Discuss how some can now be collapsed into a single update Discuss how the update record steps can be combined into a single update too Actions aren’t reusable, in the same way, but that means no one else can break your business process quite so unknowingly! You can, and should, use invocable processes for reusable actions.
- #9 So let’s see how we can do that same business logic in Process Builder. https://provardemo--summer18.lightning.force.com/one/one.app Show the Workflows being replaced. Discuss how some can now be collapsed into a single update Discuss how the update record steps can be combined into a single update too Actions aren’t reusable, in the same way, but that means no one else can break your business process quite so unknowingly! You can, and should, use invocable processes for reusable actions.
- #10 A little more complex now, we have 3 workflows, which we could have written as 1 originally but probably didn’t know the full requirement and just kept adding to it. Let’s add this to our Process and rather than repeat the mistake lets be smart in our field update and use a single formula to set it.
- #11 Now we have one process with all our case business logic, that’s great but what if someone creates a case that’s already closed, what’s going to happen to my SLA reporting? So let’s fix that by re-ordering our logic here and telling PB it should keep executing more than one step, without needing to use recursion!
- #12 Now we have one process with all our case business logic, that’s great but what if someone creates a case that’s already closed, what’s going to happen to my SLA reporting? So let’s fix that by re-ordering our logic here and telling PB it should keep executing more than one step, without needing to use recursion!
- #13 Now we have one process with all our case business logic, that’s great but what if someone creates a case that’s already closed, what’s going to happen to my SLA reporting? So let’s fix that by re-ordering our logic here and telling PB it should keep executing more than one step, without needing to use recursion!
- #16 Talk about the other Actions you can call and demonstrate some of them: Quick Action Invocable Process Invocable Flow Invocable Apex Chatter Posts
- #17 Debugging can be annoying: Chatter Posts & Error Email (wait for it) Record visibility & security (insufficient access cross reference id) Values are evaluated at the start: Criteria cannot fire based on earlier changes; consider sub-process Process versions unique to the Org, v7 in you dev sandbox can be v2 in Production Always activate processes after deploying Workflows fire before Processes - but try and avoid mixing the two if you can avoid it Workflows & Processes share the same Limits (as do Assignment rules, Escalation Rules and Flows). It’s 50 per object as standard with SFDC able to flex up to 300 (which you need to justify)
- #21 Thank you all for attending, if you’d like to know more about Provar please visit our website or come see myself or Geraint. If you have any questions about this talk I’ll be available for questions for the next 30 minutes or so.