Successfully reported this slideshow.

Speed up your Org with Before Save flows & Platform events, Narender Singh Singh

0

Share

1 of 20
1 of 20

Speed up your Org with Before Save flows & Platform events, Narender Singh Singh

0

Share

Download to read offline

Tell me something:

1. Are your end users complaining about Salesforce being slow?
2. Does it take ages to save a record in your org?
3. Are you running into issues like Apex CPU time limit when mass updating data?
As your org matures and business scales, you’re very likely to encounter these issues in your orgs if not already.

Join me to learn how you can set up your org’s automation which is more scalable and efficient.

Tell me something:

1. Are your end users complaining about Salesforce being slow?
2. Does it take ages to save a record in your org?
3. Are you running into issues like Apex CPU time limit when mass updating data?
As your org matures and business scales, you’re very likely to encounter these issues in your orgs if not already.

Join me to learn how you can set up your org’s automation which is more scalable and efficient.

More Related Content

More from CzechDreamin

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Speed up your Org with Before Save flows & Platform events, Narender Singh Singh

  1. 1. My Salesforce is SLOW!!! by Narender Singh
  2. 2. #CD22 Senior Dev @ Salesfive Consulting GmbH 3x Salesforce MVP Blogger @ forcePanda.wordpress.com 3x Trailhead Ranger @Nads_P07 /narendersingh07
  3. 3. #CD22 Define Slow Page Load Time Record Save Time
  4. 4. #CD22 What makes your org slow? Performance Technical Debt Hardware Integrations Data Volume & Quality Inefficient code/low-code Packages
  5. 5. #CD22 Record Triggered Automation Choice of Execution Context
  6. 6. #CD22 Synchronous or Async
  7. 7. #CD22 General Automation Architecture Example: When an Opportunity is Stage updated to Negotiation: - A task is created for the Client Care Manager* *Client Care Manager is a custom lookup field to the User object on the Opportunity object.
  8. 8. #CD22 General Automation Architecture Opportunity Stage Updated Task created for Client Care Manager Refresh 200ms* *For a fresh developer org.
  9. 9. #CD22 General Automation Architecture • Synchronous; single transaction • Coupled • Slower
  10. 10. #CD22 Decoupled/Async Automation Architecture Opportunity Stage Updated Create(Fire) Platform Event/ Call logic Async Refresh 70ms* (for PE) Task created for Client Care Manager *For a fresh developer org.
  11. 11. #CD22 Decoupled Automation Architecture • Asynchronous; multiple transactions • Decoupled • Faster • Easy on Governor Limits
  12. 12. #CD22 • PE transaction runs async so results are not visible on the UI after page refresh. • Can be very tricky to debug. • Governor Limits existing Integrations usage. • Running user is Automated Process (can’t be changed, yet). • Requires more planning and time to implement. • There is a lot more beneath the surface to be considered(for complex implementations and external integrations). What’s the catch?
  13. 13. #CD22 • Always select “After Commit”. • Implement extensive error handling. • Avoid use cases where “Automated Process” user can cause problems. • Review your org’s PE specific governor limits consumption before choosing PE for your solution. Best Practices
  14. 14. #CD22 Before Save or After Save
  15. 15. #CD22 Order of Execution
  16. 16. #CD22 Before Save or After Save 10x faster Before-save Flows After-save Flows
  17. 17. #CD22 When to choose what? Before-save Flows When you’re making updates to same record After-save Flows When you want to update related record(s) or do some other action.
  18. 18. #CD22 • If your business logic relies on fields that’re populated in after context, then you’ll have to implement the logic in after-save context. For example, Id, Auto-number, Formula etc. type fields. Before Save Exception*
  19. 19. #CD22 Pro Tip: Be mindful when using Formula for Entry Conditions
  20. 20. Thank you! #CD22

Editor's Notes

  • Not considering deployments, scratch org creation etc.
  • ×