What is the difference between flow designer and workflow?

[SS64]

What is the difference between flow designer and workflow?

[Curtis Paul]

I'm curious to know more about the specific kinds of issues you are running into with Flow.  Simply because I'm in the process of starting to build with Flow, looking to understand any potential gotcha's.  From my understanding, ServiceNow would like their customers to migrate to Flow.  The Flow Spoke integration is really interesting to me.  Although I understand it's technically possible, although kind of hacky, to call spokes from Workflow.  I'm fairly new to SN Flow and Workflows, but I've used the same kind of thing in other ITSM tools in the past extensively.  My first impression has been that Flow is better to build on then Workflow.  Not because of the low code nature of it, but it seems well organized and what SN intends to continue investing in.  I also understand it is possible to develop custom spokes (I have not had a need to do that yet) so with spoke development I expect any more advanced automation need is possible to build if something does not already exist out-of-box.

FYI... https://www.servicenow.com/community/workflow-automation-articles/flow-designer-best-practices-gener...

[John Spencer]

I liked your C language metaphor.   Felt totally appropriate for this discussion.  

Have used ServiceNow (at least as application built on ServiceNow for about 2 years) and am 'finally' studying for the CSA.  I can indeed see where the ServiceNow platform does allow for low / no code in many situations.  Where in other systems one would find oneself 'heads down' writing code to make things happen.

Again, a very good metaphor using the C language.

[RenuBabuA]

Thank you!!