Learn how apex design patterns and limits apply to flow, and how you can use flow to become a developer. Hear about Meighan’s journey from Admin to developer and the impact Flow had on that journey. See how best practices in Flow that are used every by admin apply to code, and can help you make that jump from admin to admineloper less scary, and how the confidence you have in your admin skills can be used to help lead the way to writing better code with Apex.

1. ”
“
Casablanca, 19.10.2019
Using Flow to Become a
Developer
Meighan Brodkey
Practice Manager Architecture
Salesforce MVP
Xede Consulting Group
@MeighanSF

2. Why am I telling this story?
● Once upon a time….

3. With Great Power
Comes great responsibility

4. In the Beginning
• Flow was so exotic
• It was launched by Apex or Workflow Rules
• Most didn’t want to touch it or they put it all over
• It’s Power is equal to that of Apex
• It’s Danger is equal to that of Apex
• In the wrong hands it can break all your data

5. I DO NOT SAY THIS TO SCARE YOU!
• BUT… With Great Power Comes Great Responsibility
You can’t just dive in and throw in a flow
• You need to Plan and Consider things

6. Declarative Work as Whole
Basic
• Workflow Rules
• Custom Objects
• Actions
Intermediate
• Validation Rules
• Process Builder

7. Flow
• Now we’re getting tricky
• Hitting limits
• 50k records
• 100 SOQL
• 150 DML
• Messing with code
• Hitting errors

8. You can do So Much More!!
• Connect with Related Objects
• Connect with Unrealted Objects
• Integrations
• Work with JSON defined Objects
• Use Components in Screens
• Redirect after automation with actions

9. How to Deal
• Start thinking like a Developer
• Change How you work
• Learn about Limits
• Not just learn the rules but USE THEM

10. What are Some of these Rules you Speak
of?
• Loops
• Null Check
• Order of Operations
• Exceptions/Error handling
• DML at the End
• No hard coding

11. Best Practices
• Plan Plan Plan
• Use that Sandbox, you should be anyway
• Don’t be hard coding IDs
• Record types should all have a lookup or choice
• Don’t update and create along the way, do it all at the end
• Take away the back button if it’s not needed
• Save… all the time
• Keep trying different ways to do your design
• Don’t touch external objects after your DML
• If you need help, ask for it!!!

12. Questions?
”
“ Using Flow to Become a
Developer

13. THANK YOU
for attending this session
And thanks to our sponsors