Install Status for Application CIs discovered using custom pattern

[NirmalSharma]

I have a scenario of using a custom pattern to discover an application TIBCO Rendezvous. I am able to discover it successfully, "no issues". However when software is not available anymore discovery is not setting its install status as 'Absent'[which is my understanding that it should do]. I checked the deletion strategy but I could not find any record for its class as well for the pattern. N

Can someone help me understand what might be wrong. Expectation is that install status should be set to absent if discovery is no more able to find it.

#ITOM, #Discovery #Pattern

[srinija_itom]

Hi @NirmalSharma,

Sorry for the delayed response. These are tracked configuration files, which is a useful feature for bringing application-related files into ServiceNow. It really depends on the specific use case you’re trying to address.

If you don’t need these files in ServiceNow, it wouldn’t hurt to delete them—but it’s always a good idea to check with the application team first.

sometimes these tracked config files contains sensitive information. Please check this kb article. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1002122

Kindly please mark the answer as correct or helpful if it solved your issue. 

Regards, 

Srinija

[NirmalSharma]

Thanks Sirinija for your reply. However I feel like those files are differnt and does not participate any role in defining the deletion strategy for the main CIs created by pattern. Please correct me if I am wrong. 

[srinija_itom]

@NirmalSharma Yes, These files are different does not participate any role in defining the deletion strategy for the main CIs. But then look for relationship CI's between main CI and tracked config file in cmdb_rel_ci or related ci's ui action in the service map view. If you want to these files to be deleted you need to create a separate deletion strategy.

Regards, 

Srinija