Origin of incident record creation

[Marcos da Silva]

Hello friends, first time I post something here in the community.
I'll explain my situation and see if anyone can help me.

I recently identified that some incidents are being generated at work here.
These records are being generated without any information.
I created a BR to abort the creation of these records.
The BR is working perfectly. However, I wanted to know if there is any way to log in before the abort, which is the origin or which rule is trying to generate these incidents.

do you know if it is possible to somehow get which rule, whether it is a WF or even another business rule that may be trying to create these records.

Thank you in advance

[Prince Arora · Accepted solution]

@Marcos da Silva ,

Please check:

Is there any another business rule written on the incident table which is worked on 

After - update and you have used "current.update()" in the script, 

You can search as mentioned below:

if you find such entity. please made it active false for sometime and reproduce the scenario again!

If the scenario is not reproduceable, it means that BR is the culprit! 

If my answer solved your issue, please mark my answer as ✅ Correct & 👍Helpful based on the Impact.

[Prince Arora · Accepted solution]

@Marcos da Silva ,

Please check:

Is there any another business rule written on the incident table which is worked on 

After - update and you have used "current.update()" in the script, 

You can search as mentioned below:

if you find such entity. please made it active false for sometime and reproduce the scenario again!

If the scenario is not reproduceable, it means that BR is the culprit! 

If my answer solved your issue, please mark my answer as ✅ Correct & 👍Helpful based on the Impact.

[Marcos da Silva · Accepted solution]

Sorry for the delay in responding.
We found some BRs causing the problem.

Thanks