How to Exclude "missing_ci" Task Type from CI Exception Process in ServiceNow?

MarxA
Tera Contributor

Hi all,

In our ServiceNow instance, we have CI Exception tasks (table: cmdb_ci_exception) with a field u_task_type that can be set to "missing_ci". I want to remove "missing_ci" from being processed by our CI Exceptions Task process, so that these tasks are not handled by the same logic as other exception types.

MarxA_0-1779812297291.png

I have checked Business Rules and Script Includes on the cmdb_ci_exception table, but I cannot find any logic that filters or processes by u_task_type or "missing_ci".

Where else should I look, or what is the best way to exclude "missing_ci" from this process?
Any step-by-step guidance would be appreciated!

Thank you!

3 REPLIES 3

Tanushree Maiti
Giga Patron

Hi @MarxA 

 

Do you have any existing BR or flow pr scheduled job on cmdb_ci_exception table to start the backend process.

 

Option 1: 

  • Navigate to System Definition > Business Rules on cmdb_ci_exception table
  • Locate and open the Business Rule that handles the exception logic.
  • In the Condition field, add the following condition so it skips missing_ci tasks:
    u_task_type != missing_ci,

Option2 : 

If you have scheduled job, 

Just add the condition

 

var gr = new GlideRecord('cmdb_ci_exception');
gr.addQuery('u_task_type', '!=', 'missing_ci'); // Add other query conditions if necessarygr.query();while (gr.next()) {
    // Your Process exceptions logic here}
Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

Hi Tanushree,

Thank you for your suggestions. However, my main question was not about how to add the exclusion, but rather how to find where the CI Exception processing logic actually lives. I’ve already checked Business Rules and Script Includes on the cmdb_ci_exception table and didn’t find any relevant logic. I’m looking for step-by-step guidance on how to systematically track down where this processing is happening, especially if it’s not in the obvious places.

Any advice on how to approach this kind of investigation would be greatly appreciated!

Thank you!

Hi @MarxA 

 

Check  Data policy , client script apart from BR, script include

 

Note: Take help of code search from studio-> give Key word as "missing_ci".

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin: