How to fire Business rules when a record is created/updated/deleted via an update set

[yashxsharma]

Hello Community,

I have a requirement related to an existing Business Rule (BR) in Production that sets certain records in the Auto Flush Rule table to inactive and prevents users from reactivating them.

However, we’ve observed a scenario where, if a user captures an Auto Flush rule in an active state within an update set and promotes it to Production, the record gets created as active, bypassing the intended restriction.

I understand from a ServiceNow article that this is expected platform behavior.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867344

That said, I would like to explore whether there is any workaround or best practice to ensure that such records are not created as Active in Production.

Any insights or recommendations would be greatly appreciated.

Thank you!

[Juhi Poddar]

Hello @yashxsharma 

• As you mentioned, this is expected platform behavior. When records are created or modified through an update set commit, Business Rules do not fire, so the restriction gets bypassed. There is no out of the box way to change this, but there are a practical workarounds depending on your setup.
• If you have a release process in place, add a step where the person committing the update set manually runs a background script or fix script to deactivate those records right after the commit. Simple, no code change needed.

Hope this helps!

Thank you!

Juhi Poddar