How do I map a new LifeCycle Stage and LifeCycle Stage Status

Erick18 · ‎02-16-2022

I am wanting to use the Lifecycle fields on our location table and the only status that are mapped to the End of life stage are Obsolete, Sold, and Lease Return. I would like to add Retired which is already an existing status that is mapped to other tables to this list. The table life_cycle_control which dictates which stage and status combinations are allowed on each table is locked down by several ACLs. Is there a different way to add additional stage and status combinations or should I adjust the ACLs?

Thanks,

Erick

scott_lemm · ‎02-16-2022

Erick,

ServiceNow does not want the new Life Cycle Stage and Status objects modified. These objects were locked in order to maintain consistency for current/future products that rely on knowing the status of critical data and effecting its life cycle process.

The values provided for End of Life on locations have the following meaning:

Obsolete - no longer needed
Sold - no longer owned
Lease Return - no longer leased

We feel a value of "retired" is not descriptive enough for Locations. We need a value that provides more detail as to why a location is EOL so it can relate to potential use from facility management, financial management, and etc.

Hope this helps,
Scott

View solution in original post

kchapman87 · ‎10-02-2023

@scott_lemm - I looked through the CSDM 4.0 white paper, and I see the broader charts for lifecycles, but I do not see the breakdown of the definitions for each of these. Can this be found somewhere?

CJPeterson · ‎01-10-2023

Hi, thank you for explaining this.

Is there an ACL that controls if we can/can't update the Life Cycle Stage field in list view but can in form view.

Community Alums · ‎04-19-2023

Hi Scott,

What if a CMDB sub-table has inherited cmdb_ci controls and we want to add a life_cycle_control record for that table because a status or stage doesn't apply. Is that possible?

Thanks,

Peter

declannolan · ‎01-21-2025

Hi,

I've exactly this issue...I wanted to effectively use the same Life Cycle Controls that are currently associated to cmdb_ci_hardware, for the cmdb_ci_comm class. (Currently the Life Cycle Controls for cmdb_ci_comm are just the controls listed for cmdb_ci as there are no specific controls available for cmdb_ci_comm. These controls are very limited i.e. only 7 combinations compared to the 26 for cmdb_ci_hardware).

What's the current CSDM thinking on this? (It's for a brand new Xanadu instance so no need to map legacy status values, we just want to use the CSDM Life Cycle Stage/Status values, but this issue could be a blocker).

Michael Walsh · ‎07-16-2025

Did you ever get an answer to this one? I'm in a similar situation, but with the cmdb_ci_peripheral table. Peripherals are linked to hardware assets too, so i'm seeing some oddity too where I can change the lifecycle stage/status on the hardware assets to something like End of Life/Disposed and it changes ok on the Asset (though you do see the error popping up from the CI when you do it manually) but the update to the CI is aborted so you end up with End of Life/Disposed on the asset, but the CI still says Operational/In use.