Flow designer drawbacks

[Balakrishna_ABK]

Are there any drawbacks of flow designer wrt workflow in practical implementation?

[Abdullah12]

Are you trying to compare flow designer with workflow? or you mean something else . please clarify?

[Sandeep Rajput]

@Balakrishna_ABK I have used both (Workflow and Flow designer) and my experience with both of them has been satisfactory so far. Flow designer is more friendly when it comes to low code/no code implementation whereas Workflow requires some amount of technical know how. 

[Sumanth16]

Hi @Balakrishna_ABK ,

low Designer will run in the background, similar to scheduled jobs and asynchronous business rules. There will always be a delay between the actual trigger and the start of the flow. low Designer flows are more maintainable, since they are more structured. Flows created by Flow Designer are more comparable to "legacy" Workflows and are meant to replace these. There is a bit of overhead in creating and calling a flow compared to a business rule, but they also have the big advantage that you can later go back at an execution context and inspect what happened in a particular flow execution - this provides some good auditing possibilities.

I don't think we have hard and clear rules on where flows are appropriate compared to business rules, but my philosophy is that wherever there is a longer running piece of business logic that doesn't directly have to interact with the user interface, try using the flow designer. (If for example you are just setting a single field outside the context of a larger flow, a simple business rule is probably better).

Please refer below thread:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0789014

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda