Remove or hide related CIs that have been retired from the Related CIs section of the form.

[Mahesh Kallumad]

For this: APEX -FRIX Dev (Mapped Application Service), i am trying to remove the retired/non-operational CI's from the dependency view.

For example, iadapxappdev01 is retired and was replaced with iadapxappdev02. Even though iadapxappdev01 is marked as retired, it is still showing in the dependency view. Please suggest the way how i can exclude the retired CI's.

[Dr Atul G- LNG]

Hi @Mahesh Kallumad 

you need to remove the server1 manually from the relationship table. Click on the + icon and then remove it from there.

[Mahesh Kallumad]

Hi @Dr Atul G- LNG ,

Thanks for your response. I should have mentioned this earlier, actually there are more mapped application services where retired CI's are still show up in the relationships. 

Instead of removing retired CI manually, is there any other way to configure it for all application services? So, that retired CI's will be hidden from the view.

Thanks,

Mahesh

[Dr Atul G- LNG]

Hi @Mahesh Kallumad 

I doubt there is any other way to delete this other than manually.

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

If not, you can log a Now Support case and team will help you.

[Marshall Parker]

The dependency viewer will display all relationships that exist, no matter the status of the related CIs.

If you don't want to see relationships for Retired CIs you could create a Business Rule that deletes relationships for retired items. You should check the data governance rules in place for your instance before deciding to delete these relationships.

A Business Rule similar to below may be useful:

For cmdb_ci table

When to run: async - update

Filter: Install Status 'changes to' Retired

Advanced: Build a script that looks at cmdb_rel_ci where child=current

loop through these records & delete from cmdb_rel_ci

This BR would ensure that only relationships for active CIs exist by deleting relationships when the status moves to Retired.  If you go this route, you may have to also do a bulk update to catch-up remove any relationship for retired items as this BR would only process for new changes to Retired status.