Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

How does Life Cycle Controls work?

ameliom
Tera Contributor

My company is currently undergoing the transition from Install Status/Asset Status to Life cycle stage and statuses. I was told that the life_cycle_control table can be used to identify what life cycle stage and status fields would be able to use on each table. However when I filter the life_cycle_control table to look at what stage and statuses are available for a specific class in the CMDB, I do not see that it is accurate. For example, when I look at the life_cycle_controls table and filter it down to table=service, I see 4 possible values for Life Cycle Stage:

 

Screenshot 2025-03-17 092918.png

However when I go look at a CI that is a child of the Service Class (application service), I am seeing more than the 4 life cycle stages that were listed in the controls table for this class. 

 

ameliom_0-1742218268067.png

Is there some sort of inheritance that is happening on the life_cycle_control table? If so how do you know which values are being inherited or not because I have seen some of the values are being inherited from Server's parent class Configuration Item and some are not being inherited. Thank you in advanced!

2 REPLIES 2

tom_p94
Tera Contributor

Hi @ameliom, did you ever get an answer to this? Cheers

Justin Loftas
Tera Guru

The reference qualifier on the Life Cycle Stage is produced by the function filterLifeCycleStage in the Script Include LifeCycleUtil. Looking at the code it returns any Life Cycle Control [life_cycle_control] where the table matches that of the record and then any other base tables in the hierarchy, i.e.:

Bot Process [cmdb_ci_rpa_process] >

Base Bot Process [cmdb_ci_base_rpa_process] >

Automation CI [cmdb_ci_automation] >

Business Process [cmdb_ci_business_process] >

Configuration Item [cmdb_ci] >
Configuration [cmdb]