Limitations in Flow Designer vs Workflow

[Astik Thombare]

Hi Community,

Are there any things that cannot be achieved through Flow Designer but can be achieved with Workflow? I have seen threads where it is mentioned that SLA timer-related things cannot be handled via Flow Designer, but these actions are available in Flow Designer.

[Dr Atul G- LNG]

Hi @Astik Thombare 

I am not sure but you can refer this

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0789014#:~:text=If%20the%20pr....

[Ankur Bawiskar · Accepted solution]

@Astik Thombare 

Flow is not a complete replacement for Workflow.

there are lot many things which are not supported in Flow but works well in Workflow

But there is no definite list for this

It will be only known when some particular requirement comes in and you get to know that flow cannot handle it

Below are some items which Flow doesn't support

1) complex scripting

2) rollback approval

more details here

Flow Designer vs Workflow 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[J Siva]

Hi @Astik Thombare 
I know one, which is related to approval.
Use case:
After submitting the service request, an approval needs to be triggered to the designated approver. If the approver does not take action on the record within 3 days, escalate the approval to the approver's manager.

Difference:

If the RITM lifecycle is being managed by a workflow, we just need to update the approver value to the approver's manager in the approval record. This allows the manager to act on it, and the RITM will move to the next stage based on the result.

However, if the lifecycle is being managed by Flow Designer, simply changing the approver value in the approval record won't work. The entire flow needs to be re-triggered, or additional steps need to be taken.

Regards,
Siva