Forcelandia 19 How to Use Flow to Become a Developer
Download as PPTX, PDF0 likes155 views
The document outlines best practices for using Flow in Salesforce, emphasizing the importance of planning and understanding its power and potential risks. It encourages developers to think strategically, adhere to certain rules, and utilize sandbox environments for testing. Key recommendations include avoiding hard coding, managing processes effectively, and ensuring data integrity throughout automation.
Forcelandia 19 How to Use Flow to Become a Developer
- 2. How to Use Flow to Become a Developer
- 3. Meighan Brodkey Practice Manager Architecture Salesforce MVP Xede Consulting Group @MeighanSF
- 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 Custom Objects Actions Intermediate Validation Rules Process Builder
- 7. • Now we’re getting tricky • Hitting limits • Messing with code • Hitting errors Flow
- 8. • Connect with Related Objects • Connect with Unrealted Objects • Integrations • Work with JSON defined Objects • Use Components in Screens • Redirect after automation with actions You can do So Much More!!
- 9. • Start thinking like a Developer • Change How you work • Learn about Limits • No just learn the rules but USE THEM How to Deal
- 10. • Loops • Null Check • Order of Operations • Exceptions/Error handling • DML at the End • No hard coding What are Some of these Rules you Speak of?
- 11. DEMO FLOW
- 12. • 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!!! Best Practices
- 13. Q&A
- 14. Thank you!
Editor's Notes
- #2: Can use as a general divider
- #3: This will have sponsor logos added when they are finalized
- #4: Single speaker Title Slide
- #5: General content slide
- #6: General content slide
- #7: General content slide
- #8: General content slide
- #9: General content slide
- #10: General content slide
- #11: General content slide
- #12: General content slide
- #13: General content slide
- #14: This will have sponsor logos added when they are finalized
- #15: This will have sponsor logos added when they are finalized