Related entries in CI identification rule - Need Clarification

[Anitha17]

Hi Experts, 

Need your kind explanation,  

Last weekend we have upgraded ServiceNow from Quebec to San Diego release in Dev instance, after upgrade while doing IRE testing we have notice few new rules are automatically added for many class tables in Related Entries under identification Rule. 

For Example:

Can we disable the Related entries rules(12 entries) in Dev instance? if we disable, whether it will impact any identification process ? and what benefits we get if we keep this entries rules as it is for every class table. 

Your explanation is much appreciated !!!

Regards,

Anitha.  

[DaveHertel]

Hello Anitha - 

 The "related entries" are not used for the identification of CIs, i.e. to determine if a CI already exists, or if a CI should be inserted/updated.  These related entries are used to define a reference to other classes, related to the current class... so CI's in those related classes might be updated too.  I know...  confusing...

docs here

Hope this helps a bit?

[Anitha17]

Hi Dave Hertel, 

Thanks for the prompt response.

Hope it will be same scenario for all customers who have upgraded to San Diego release, Just though to get clarify my doubts, So we can leave those entries as it is, in all class table ,.... am i right....? it is not going to harm any class table.

Regards,

Anitha 

[DaveHertel]

Hi - well, I can't guarantee anything 🙂 but assuming the docs are accurate <grin> I wouldn't think leaving them (related entries) as-is will harm anything.  Nevertheless, thorough testing in your DEV sub environment should be used to validate any lingering concerns.  

As you know, good DEV & TEST environments that closely mirror production so that they can be relied upon to confidently know how PROD will behave when changes are introduced.

Hope this helps?

[doug_schulze]

I covered these pieces in this post, hope it can help.