- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 06:23 AM
Hi,
we have a business application that has multiple application services (AS) related to it. Some of those AS are retired.
When I check the related items of the business application, all AS show, also the retired ones.
Is there a way to exclude the retired AS without deleting the relationship in the cmdb_rel_ci table?
Or is there a way to show those in a different color so you see on first sight which ones are retired?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2023 05:50 AM - edited 03-10-2023 05:52 AM
Your screenshot is from the CI Relations formatter. There you can only exclude relationship types, but not CIs. In case the filter is needed and you want to keep the relationship also for retired CIs I would suggest to create a new relationship type, that you can then exclude from this view. But this would mean, you need to change the relationship always you retire a CI.
However my assumption is, that ServiceNow does not intend to keep the relationships valid after a CI was retired. Because the CMDB reflects the current operational setting and not historian operational setting. I didn't validate it, but I assume, that you will also have an issue with the ITSM processes, when we talk about automatic adding of affected CIs and services to a task.
PS: Please do not forget to mark answers as helpful or correct, if they answered your question. Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2023 12:57 AM
The CMDB data manager allows you to define a policy process for this. But please be careful in setting it up, as this can change and affect your whole CMDB. You can find more informations here.
PS: I am not yet an expert in the CMDB data manager. I highly suggest to contact your implementation partner, before planning to use it. Because you will need to migrate to the new lifecycle status model.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 10:01 PM
This is a good question and I look forward to seeing an answer!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 11:08 PM
Hey,
I do not know a way to show it in different colors. But I would suggest to work with a predefined filter. You could create a predefined filter, that removes all "retired" CIs from the dependency map. If you need to see them, you would need to change the filter. You can do that with the following steps:
1. Define a predefined filter over the table "map_view"
2. Use the filter in the dependency map
If it should be a default filter:
3. Copy the sys_id of the predefined filter
4. Set the predefined filter as a global user preference as described in the docs
I hope that helps.
Kind regards
Sebastian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2023 03:21 AM
Hi,
I tried it out and that works for the dependency maps. Great!
But when looking to the relationships, it still show the retired application services. See picture attached. The application services with '_prod' '_test' '_QA' and '_dev' are all retired but still show.
Is there a similar solution for the relationships?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2023 05:50 AM - edited 03-10-2023 05:52 AM
Your screenshot is from the CI Relations formatter. There you can only exclude relationship types, but not CIs. In case the filter is needed and you want to keep the relationship also for retired CIs I would suggest to create a new relationship type, that you can then exclude from this view. But this would mean, you need to change the relationship always you retire a CI.
However my assumption is, that ServiceNow does not intend to keep the relationships valid after a CI was retired. Because the CMDB reflects the current operational setting and not historian operational setting. I didn't validate it, but I assume, that you will also have an issue with the ITSM processes, when we talk about automatic adding of affected CIs and services to a task.
PS: Please do not forget to mark answers as helpful or correct, if they answered your question. Thanks.