CMDB CI status fields - install_status vs life_cycle_stage

bpolo
Tera Guru

We are currently implementing Vulnerability Response, and we noticed that OOB functionality in VR checks the status of a Configuration Item using the life_cycle_stage field. We do not have this field populated on our CIs. We use the install_status field to check the status of a CI. Please could someone explain the difference between these two fields, and when should which field be used. Is it best to start using the life_cycle_stage field rather than the install_status field? Or do they have different purposes?

Any help would be much appreciated. Thanks! 

1 ACCEPTED SOLUTION

Ashok Sasidhara
Tera Sage
Tera Sage

Install status is one among the many different status fields present for CI classes in ServiceNow. There are others also like hardware status (applicable only for hardware CIs), operational status etc. Life cycle stage and Life cycle status are the new CSDM aligned fields aimed to ensure a consistent format for indicating CI status (by replacing the multiple legacy status fields) across all CI classes. Life Cycle Mapping [life_cycle_mapping] table shows how the various legacy status fields are mapped to Life cycle stage and Life cycle status values. You can find more details about this in the following URL:

 

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-managem...

View solution in original post

8 REPLIES 8

Ashok Sasidhara
Tera Sage
Tera Sage

Install status is one among the many different status fields present for CI classes in ServiceNow. There are others also like hardware status (applicable only for hardware CIs), operational status etc. Life cycle stage and Life cycle status are the new CSDM aligned fields aimed to ensure a consistent format for indicating CI status (by replacing the multiple legacy status fields) across all CI classes. Life Cycle Mapping [life_cycle_mapping] table shows how the various legacy status fields are mapped to Life cycle stage and Life cycle status values. You can find more details about this in the following URL:

 

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-managem...

Hi Ashok

Thanks so much for your response! So just to confirm, is the SNOW recommendation going forward, to convert to using the CSDM aligned fields like  Life cycle stage and Life cycle status? Thanks again!   

Yes. That is right. The usage of these 2 fields are recommended by ServiceNow for ensuring a consistent representation of the lifecycle stage & status across various types of CI classes. Let me know if you need any further clarifications. If there are no further queries, please close the thread by accepting the solution. 

Thanks very much, Ashok for your help with this.