💃 Flow v Code: The Great Debate🕺

Automate all the things! But ... how??

Good morning, Salesforce Nerds! I don't know about your team, but mine is comprised of admins, devs, an architect, QA. When a story is plucked for work the first decision is how to proceed. Flow or Apex? The mothership recommends Flow for almost everything, right? But, how do we really decide? Fret not! The ChaCha is here to set your minds at ease! The answer is ... there is no clear answer! But, there is a path to a decision. Sort of.

Agenda for today includes

  • Automate all the things

  • Daily Principle

  • All the Memes

Automate all the things!

Before we start - 📣shout out📣 to the Salesforce Architect site. In case you don't already know, this site a goldmine of information for us tech geeks working on the platform. It's absolutely packed with resources. One of the resources covers the topic of Record-Triggered Automation. This is what my team is using to guide our Flow v Code decisions.

Let's summarize the key takeaways listed in the article:

Subscribe to keep reading

This content is free, but you must be subscribed to SalesforceChaCha to continue reading.

Already a subscriber?Sign In.Not now