Health scan result on Flows vs Business rules

[Suggy]

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?

[Kieran Anson]

No not quite.

Flows are an alternative to running a business rule and have a smaller technical debt because of their low-code nature. However, replacing business rules with flows is only beneficial for async or after business rules as flows don't run in the 'before' context.

[Ankur Bawiskar]

@Suggy 

ServiceNow recommends using flow wherever possible as an alternative to BR as it's low-code, no-code.

But it's not possible always to use flow instead of BR if there are some complex conditions to be used.

BR has an advantage there as you can use condition field there where you can write javascript logic or invoke script include

It all depends on your business requirement and complexity of requirement

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

[Suggy]

@Ankur Bawiskar @Kieran Anson Hey I got your points, and I am aware of it. My question is what exactly ServiceNow meant by this recommendation "you could use Flow Designer as a way to consolidate multiple asynchronous Business Rules"

[Kieran Anson · 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