Retire a CI Best Practices

Jason Stuart
Tera Expert

Good Afternoon,

        What is the best practices when it comes to retiring a CI, I am having trouble wrapping my mind around this.  You have a parent CI, say a Server - and this has been discovered by Discovery.  Now there is a whole bunch of stuff created, CI_IP's, software, running processes, ETC.  This is awesome, and all is well and good.  

       I will preface this by saying we have activated Life Cycle Migration (even though we are not using those status yet).  I have read Doug's article about the retirement process.  I have looked into Data Manager to try and address this, and it does not.  I am lost, I just see a bunch of articles saying "Use Business Rules for retirement".  How can you do this, and try to maintain this while discovery fills in whatever data, and whatever records.  How do you deal with this from a maintenance perspective?  Also does anyone have any examples? 

     When you retire a parent CI, how do you account for retiring all of the CHILD ci's (er relationships).

 

Thanks in Advance! 

1 ACCEPTED SOLUTION

emir
ServiceNow Employee
ServiceNow Employee

Doug's article is intended to address this requirement. There is a retire related item UI action to do this.

View solution in original post

5 REPLIES 5

emir
ServiceNow Employee
ServiceNow Employee

Doug's article is intended to address this requirement. There is a retire related item UI action to do this.

Akshatha Balla1
Tera Contributor

Can you please link Doug's article?

Can you please link Doug's article?