We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Health scan result on Flows vs Business rules

Suggy
Giga Sage

ServiceNow says "

Number of Business Rules to maintain - Recommendation:
The more Business Rules, especially on one table, the more to manage and test. Consider other methods, for example, you could use Flow Designer as a way to consolidate multiple asynchronous Business Rules."

 

If anyone has understood this, can you give me the context or example?

 

Is it like, each time we get a new requirement which needs a Business rule, we need to edit the exsiting flow and keep adding the logic in it?

 

1 ACCEPTED SOLUTION

It's referring to an architectural design pattern. You may have a number of flows with a similar trigger condition. You could use a single flow with a dynamic subflow step that calls all necessary subflows. 

 

You wouldn't need to edit the master flow - only the child flows that are called and the decision table that is used 

View solution in original post

5 REPLIES 5

Thank you @Kieran Anson