Business rules we moved into PROD instance are not executing. Can't figure out why

[Myron Smith]

We created a scoped app to monitor the Progress Worker table and create an incident if errors are found. Even though we find errors when we search the table our business rules are not executing. Does anyone know how we can find out why they are not executing? Is there a permission tied to a scoped app that would prevent it from running in PROD? Everything works in all of our DEV and TEST instances.

[Anurag Tripathi]

Hi,

Can you look at the condition of the business rule and try to match it to the actual data from production?

Also, how are you testing it in QA VS Prod. Like in QA do you manually generate error or let the progress worker throw the error itself?

If anywhere in the transaction setWorkflow(false) is used then the BRs will not trigger for that transaction.

That would be a place to start investigating.

-Anurag

[Myron Smith]

Is there anyway to check to see if permissions are correct for the business rule or if it is being executed at all? We are seeing the error condition in PROD but we are not seeing anything in our log files.

[Myron Smith]

We found the issue. The "contains" clause in the Business Rule is case sensitive, so it satisfying our query.

[Anurag Tripathi]

Yea, I was saying that look at the condition of the BR, there is something there.

glad you solved it.