Business Rules with "insert","update", "delete", "query" fields set to false. Is it possible?

ashwindatre · ‎07-19-2017

I can see there are lots of OOTB business rules that have all "insert","update", "delete", "query" fields are set to false. I thought the whole purpose of using a business rule is to enforce rules against database CRUD operations, then how can these conditions be false?

How does a business rule work in such condition?

In what situations such BR conditions are used?

regards,

Ashwin

chrisshellhamme · ‎07-19-2017

Display Business Rules do not have insert, update, delete, or query set. Also there could be a case where a Business Rule is being called from another script, or possibly a scheduled job and you do not want it to run when an action is taken on a record.

Regards,

Chris

View solution in original post

Dennis R · ‎07-20-2017

For the first question, it's because they're two separate things. I honestly don't know why there are two mechanisms to accomplish the same task, it might be that the sys_trigger jobs are old legacy stuff that just hasn't been retired. For the second, I just know that the fcScriptName=[business rule] is a "magic" value that causes the business rule to execute out-of-band from any field changes in a record. I don't think these sys_trigger or values are documented anywhere. If I had to guess, I'd say that it's probably something baked into the Java back-end of the system that we're not privy to, but I honestly don't know. I just know that this is one mechanism by which business rules might execute without being triggered by a record being viewed or edited.

ashwindatre · ‎07-21-2017

Thanks Dennis.