Business rules Vs Flows

[MS12]

Wanted to know if anyone has any opinion on why we would use flows/subflows/actions instead of business rules going forward?

In my opinion there are scenarios where flows are useful - like catalog items, scheduled flows, integration related ones etc

But for things like when a field is updated do this logic - do you prefer a BR or flow? I don't like flow in this scenario since I find flows clunky to manage. No debug capability to stepping through code, no code search.

In a recent meeting with ServiceNow they recommend to use flow for scenarios where BRs were used in the past. I don't agree with it. I wanted to get some perspective from other developers. Thanks for your time.

[MS12]

Thank you for your response. I like the fact that I can step through breakpoints during the process instead of checking for variable values after processing has completed. But yeah, it's super nice to see the input/output of each step of the flow. We have had issues with flow not being able to process high volume transactions (big while loop). We had to change the flow steps and then create an action that runs a script for these type of transaction.