What is Flow, Really? A Feature?
I recently shared on LinkedIn that flows are getting a lot of attention. I wrote that we need a dedicated certification for flows and a flow champions program.
That post stirred up some debate. I wanted to share my thoughts about this in a long form. I will do this in a Q&A format and then drive a conclusion at the end. Here we go:
What is flow? A Salesforce feature?
One of the topics that came up was whether flow was a feature. It is not imperative to emphasize the categorization, but this topic demands clarification. For me, "account teams" is a feature, and "quotes" is a feature you can turn on on the platform. Flow is a low-code platform, or even if you refrain from this title, a group of products on the Salesforce platform that spans over clouds and products: You can use flow on Sales, Service, Community (Digital Experience) Clouds, and Field Service. Flow has several solutions available that have dedicated product teams in Salesforce. When you go to the release notes, Salesforce flow is one of the top-level pages you see. This was not the case a few releases back. But when addressing some of the topics I mentioned above, this categorization is less important than the definition of the target audience and skillset required to utilize this product to the full extent.
Can flow topics be rolled under administrator or developer headings?
Not really. Administrators do not have to use flows. In fact, there are Salesforce licenses that don't offer flows or limit flow usage. Developers do not have to use flows, either. It would be great if they did, in any case.
What is the skillset required to use flows?
Flow skillset sits right between admin and developer. A talented admin may never make the transition to building advanced flows. However, they can still customize their Org to address the needs of the business. On the other hand, developers who work in big development teams in giant corporations do not have to master flow or admin skills to do their job. They can deliver specialized and well-documented solutions merged into bigger releases to address business needs. However, if they did master admin and flow skills, they would be super valuable.
What are the prerequisites to learning flow?
Power-user or basic admin skills are required. However, you can start learning flow without being an advanced admin. Some developers in the ecosystem argue that basic development and coding concepts should be studied before learning flows. While this study would help you with flows, this is not a prerequisite to learning flows.
What is the target audience for flows?
The target audience is admins and developers interested in using low code to customize the Salesforce platform through automation.
Flows have their own release readiness webinar separate from Admin and Developer. Jacinta Burke shared that this has been the case since 2019. She said, and I quote: "It was a no-brainer given our audience".
Have you ever wondered why the Salesforce MVP David K. Liu named his website "SALESFORCE CODING LESSONS FOR THE 99%"? Unfortunately, code and low code are not for everybody. I taught thousands of people flow, and I will be the first to say that there will be people who will not or cannot do flow. They will be able to do simple things like email alerts, but they may not be comfortable tackling some more advanced ones.
Generally, the flow target audience is a subset of admins and developers. There could be exceptions.
领英推荐
Which certification should address the flow skills?
Currently, Platform App Builder is the one that includes flows. It is a mixed bag, though: What do Lightning Apps/Pages have to do with flows? Very little. On the flip side, I know many people with this certification who can only flow a little. I explained above that I do not think every admin should be required to flow. So we either need to revamp the PAB certification or give flow it's own certification.
Can flows be part of Platform Developer 1 or 2 certifications? They can be, to some extent, if this is what you want to do, but there will be a big audience who flows who never want to do coding. Therefore I think flow needs to be addressed separately.
In summary:
???????????????????? Skillset???????????????? Audience
Admin??????????????? Admin?????????????? Admin & SU
Flow???????????????? Low-code?????????? Admin & SU & Coder
Code Developer???????Coding??? Admin & SU & Coder & Low-coder
Note: SU = Super-user
Whether Salesforce launches a Flow Champions program is totally up to them, but I know tens of people do this already without Salesforce's funding and support. I would be hesitant to list them here, fearing I may leave a few out. Instead, please tag them below; we all know who they are.
Let me know what you think in the comments.
???My bestseller Udemy course is on sale for $9.99, the year's lowest price. Buy it now and get lifetime access to the course and the reshoot that will be published soon.?Click here to buy?or use the code: JANUARY3 ??
---
Visit?https://SalesforceBreak.com/?for more awesome posts like this.
If you ?? the newsletter, please recommend it to a friend or colleague.
Consultant Software Architecht/Developer at Abbott
2 年After a couple of years' experience, not so much of writing Flows as of the consequences of people who claim to be unable or unwilling to write 'code' writing Flows, I'd tentatively propose a 'best practice': Make an informed decision on whether to use Flows or to use Apex Code and be VERY reluctant to mix the two together. Do this on a per-Object* basis and, if at all possible, on a per-Org basis. * actually on a per-group-of-objects basis, i.e. objects which are tightly connected (e.g. by master-Detail relationships) should be considered together
Salesforce MVP | Founder at Flow Canvas & Salesforce Break
2 年Great Points made by Claire Jones ? here: " Whatever your feelings on the subject, the fact is, with the announced retirement of workflow rules and process builder, that if you don't embrace flow or have at least one person on your team who does, your wings are about to be clipped. "?
Consultant Software Architecht/Developer at Abbott
2 年The idea that Flows are 'low code' or 'no code' is entirely disingenuous. Like Process Builder, Flows are code, albeit dressed up in a Flowchart-ish user interface. This is almost entirely cosmetic and ALSO makes the code MUCH harder to read, analyze and understand. The fact that Flows can be created and/or activated on a production Org without any test execution is also a menace to important live systems.
Salesforce Business Process Specialist at FOSS
2 年Janyl (Zhanyl) Saparbekova, M.S. Ed let's attend this event together
IT Security | Cybersecurity Analyst | actively looking for a new mission
2 年In my opinion flows should be for the developer as this uses programming logic, it should not be within the scope of the admin.