When to use Flow Designer vs Workflow Editor?

[peterraeves]

I am learning up on the new Flow Designer / IntegrationHub.

What confuses me is, what this offers more than the workflow editor. It just seems like WEv2, with the same functionality, but with a different UI around it. Though I have to admit that it makes flows easier to create, there is one very big flaw with FD, what makes me think I will not use it often, is the fact that you cannot script the condition... 

So in what cases should I best use the WE? And in what cases should I best use the FD?

[Hitoshi Ozawa]

>s the fact that you cannot script the condition

Concept and how to workflow design is different between Flow Designer and Workflow.

To use script in condition in Flow Designer, you'll need to create a custom Action that return True/False.

The result can then be used in the If step.

Comparing Flow Designer with Workflow is like comparing Workflow with Script. Most of the things that can be done with Workflow can also be done by just scripting too.

There's still many places where Workflow is used. When using them, it's still necessary to use Workflow.

[phoenix516]

Any one know if Workflow Editor is expected to be End of Life by a certain date?

Was the intent to migrate off Workflow Editor to Flow Designer?

If so, I need an enhancement request to be able to write complex scripts in flow designer lol.

[Gaurav Shirsat]

Hi Phoenix

from the New York Release, Workflow is an Legacy Product of ServiceNow.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/workflow/concept/c_Work...

If we look into the Pros and Cons of Workflow v/s Flow Designer.

Flow Designer:-

flow designer, flow refers to different components like action, actions steps and spokes.

Important factor for Integration Hub

NO Coding

Can not be preferred for Complex Process.

Slower than BR, Workflow.

Importance of Flow Designer for Integration Hub:-

Promotes reusability by providing a reusable flow component library. Reduces upgrade costs by substituting complex custom scripts and safe platform logic. Enables hassle-free integrations with external instances and other third-party applications with Integration Hub subscription.

Workflow:-

Workflow is used to automate business process flow using tasks, notifications, approvals.

Biggest Advantage is Use of Script or we can call any server side script.

Works Fluent in any Complex Process.

Faster than Flow Designer.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/workflow/concept/c_Work...

Please Mark Correct and Helpful

Thanks and Regards

Gaurav Shirsat

[phoenix516]

When you call something 'Legacy' it usually implies an end of life.

All the references I read regarding the timelines of the Workflow editor just 'Code Shame' the Workflow editor without really stating if it is going away, as you would expect something 'Legacy' to.

Is there a documented end of life date is what I ask the community, as I am yet to find one.

---------------------------

Regarding functionality of one vs the other, I see the integration hub being the key selling point along with the ability to build logic scriptlessly (is that even a word? it should be).

I see why the advertisements against the use of the Workflow Editor are there, if one does not pay attention to best practices. To your points the Workflow Editor (given the right MID Servers) is capable of more than just tasks, notifications, and approvals. I have yet to find something I could not code around. The idea if giving up my scripting freedoms really disappoints.
#MakeServiceNowGreatAgain  <-- Is that too much lol.