How to handle retiring Configuration Items?

[Luciodv]

We are currently seeing the need to retire configuration items and have found that there is no out of box functionality handling this.
I would expect this to behave in the same manner as making an "Assignment Group" inactive which makes the "Assignment group viewable for all historic records but is not selectable within any record once it is inactive.

This functionality doesnt exist for CI's, has anyone implemented something like this?

Some other posts indicate creating filters on Incident records, which is great for incidents but CIs could be used in many other modules and doesnt make sense to have to create rules and filters in every module when it could be done in the Confiuration module.

Thanks

[Mark Stanger]

I agree with Drew. You'll want to be careful with before query business rules so that you can still see the inactive CIs in places where you've already linked them to other records. See this article for details.

http://www.servicenowguru.com/scripting/business-rules-scripting/fixing-before-query-business-rules-flaw/

[DrewW]

And thank you for the link, I was just poking around wondering how to fix that... 🙂

[jfarrer]

We added an Active flag on the cmdb_ci table for just this reason. We defaulted it to true and I think we had to run a script to update all existing CI's to be active (it's been a little while).

Then for any CI type that we need to deactivate things for we can just add that field to the form or list and then add the appropriate filters to the modules and reference fields.

We primarily use CI's as part of the Service Catalog order processes and it has served us pretty well so far.