I, for one, know that it was a hard pill to swallow when Flow was introduced. Oh no, a new thing. I already know how to use Workflow.
But it has been a while, and I think it is time we let reality dawn on us. ServiceNow is heading in one direction and not the other.
Workflow has been a great friend and will continue to be with us (at least for some time).
But flow, Workflow's cool younger brother - that was quite annoying at first - has matured into quite the tool.
Yes, you knew how to use workflow, though no one wants to be dependent on you (as much as we all like you). You are busy and have important stuff to do other than managing our service catalog.
That is why we now have Flow and citizen development; Flow allows for no- to low-code development of fulfillment and approval flows—any flow you may need.
Additionally, its debugging has become far superior to the dear Workflow (see link).
So at this point - and please do the challenge if you disagree - there is no point in developing a workflow that a flow could have solved.
