1 huge workflow or separate into several workflow

amalina
Mega Contributor

Guys, i just want to ask, i have a very huge workflow but it recently started to hang mid-request., Really huge like the screenshot x3.

So i was thinking to re-dsign the workflow and split it into several smaller workflow and calls from the original flow.

Would it be better or stick with one huge workflow?

find_real_file.png

1 ACCEPTED SOLUTION

Dave Smith1
ServiceNow Employee
ServiceNow Employee

I'd consider breaking it into subflows - the typical "divide and conquer" strategy.



Each subflow would concentrate upon a specific set of process activities, with a "parent workflow" deciding which subflow to call, delegating tasks out accordingly.



Functionally, there will be no difference to the end-user - but behind the scenes, it makes the whole workflow more maintainable since it encapsulates change impact to one particular subflow, reducing work and risk when amending... as well as making it easier to diagnose when things are going wrong/slow.



Now, how you decide to split it - or even have subflows calling subflows - is another matter. But certainly, a diagram THAT huge strikes me as an overcomplex approach to process management.   I'd hate to be the BPC that drew that up.


View solution in original post

5 REPLIES 5

Dave Smith1
ServiceNow Employee
ServiceNow Employee

I'd consider breaking it into subflows - the typical "divide and conquer" strategy.



Each subflow would concentrate upon a specific set of process activities, with a "parent workflow" deciding which subflow to call, delegating tasks out accordingly.



Functionally, there will be no difference to the end-user - but behind the scenes, it makes the whole workflow more maintainable since it encapsulates change impact to one particular subflow, reducing work and risk when amending... as well as making it easier to diagnose when things are going wrong/slow.



Now, how you decide to split it - or even have subflows calling subflows - is another matter. But certainly, a diagram THAT huge strikes me as an overcomplex approach to process management.   I'd hate to be the BPC that drew that up.


Tell me about it.


Thanks for your opinion. I'm 80-20 on doing subflows, but yeah that 20% is all about have to do it all over again.



Thanks a lot Dave.


Dave Smith1
ServiceNow Employee
ServiceNow Employee

Thanks for your opinion. I'm 80-20 on doing subflows, but yeah that 20% is all about have to do it all over again.


Or rather, "redo it in the way it should have been designed originally".



As a matter of interest, do you know if ALL paths are actually exercised?   Wonder if there's any mileage in checking for deprecated activities and trimming the fat a bit - given you may be re-engineering it, perhaps taking the opportunity to review the entire process and update it with more modern concepts.


Ajai S Nair
Giga Guru

Hi Amalina,



Its always better to have separate subflows then calling that in main flow. Even for troubleshooting later it will be easier for you.The execution will anyway be the same since we are defining the flow.


Using Subflows - ServiceNow Wiki



Workflows used as subflows