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

[gaidem]

Well there are 2 parts to this; technical and process.

Let me start with process:

Ideally you would retire CI's through the change process. If it is a CI, it is governed by change so an RFC should handle the decommission.

There is an active boolean on the CI table. You can use this to retire the CI. Optionally, this can be based on the state of the CI. Regardless of the approach for determining how to mark the CI as retired, you will need to update any references to the CI table to include this logic.

[Sashi K1]

May I know where is Active flag listed in cmdb_ci table? Do we have to manually add a boolean field? OR any out of the box has this?

Anyone please help?

[jfarrer]

The field isn't there by default so you would have to create a new field. You'll want to be sure and create it on the cmdb_ci table so it could be used for any reference to a CI and not just on a specific CI type.

[DrewW]

As for a technical solution to having to add a ref qual to all of your reference fields that look at the cmdb_ci table you can add a BR that runs on query that adds something like "active=false" for everyone but someone with a specific role. You can see something like this on the sys_user table. Only admins can query for inactive users.