I believe this is fixed in Paris.

I believe so, too, but I haven't yet proved it out.  The enhancement request I mentioned above was converted to an idea, and on 27Oct2020, I received an email from the Community Team stating the following:

The state of idea Prevent flows/workflows from running when GlideRecord setWorkflow(false) is used has been marked as Already exists
This idea was implemented via PRB1381927: https://hi.service-now.com/nav_to.do?uri=problem.do?sys_id=76240fdfdb1ec810feb1a851ca96196a

When I tried looking at the PRB, I didn't have access.  In addition, I reviewed the Paris release notes and didn't find reference to this PRB.  I could have missed it.

tested this with one of my custom tables (on the GLOBAL scope). It works fine. The setWorkflow(false) method prevents the insertion of records into the sys_flow_context and sys_flow_plan_context_binding tables, which means that the flow I have set up (to trigger on update of a record in the custom table) is not getting triggered

Hello @Karthick Nagara ,

I'm facing one issue where there is an existing line "current.setWorkflow(false);"  present in After update Business rule and it's stopping the flow designer to run the flow when we submit a record from draft state is there any other way we could trigger flow without removing this line of code.

Your inputs would be highly helpful.

Thank you,

Raj

System Property 'trigger_engine.ignore.set_workflow'

Incase you wondered why a flow triggers when you add a setWorkflow(false) to a script