Using the new Operational / Pending Retirement Lifecycle Stage & State

[PG2]

I've started to use the new new 'Operational / Pending Retirement' Lifecycle Stage & State to reflect CIs that are being prepared for decommissioning.

I've noticed that any update to the CI in this state will retrigger the OOTB life cycle mapping rules and reset the Lifecycle Stage & State to 'Operational / In Use'.

With no equivalent legacy state for Pending Retirement on CIs outside of the cmdb_ci_service class hierarchy, how can we make use of this new Pending Retirement state without it being reset any time the CI is updated across any one of its attributes? 

Has anyone experienced this same issue? I've attached an example, explaining the above scenario.

[Tomas Lozano]

it's a clear limitation. You could do worse than going through Scott though...

If you can, let us know how ServiceNow intends on fixing this in this post as it would save me from logging my own hi case, so much appreciated 😉

Cheers,

Tomas

[scott_lemm]

@PG2 

Thank you for bringing this to our attention. Please submit a case for tracking and include the attached video. Email me the case number for tracking and we will investigate.

Thank you,

Scott

[PG2]

Thanks Scott, appreciate it! Just sent you an email with the case details.

[CMDB Whisperer]

Unfortunately I have not found a good consistent way around this, aside from defining a custom value for Pending Retirement in the legacy status field and modifying the Life Cycle Mapping, and it's an understatement to say that's not going to be a good or feasible option for everyone.  I too wish there was a good solution for this in the CSDM Life Cycle mappings, but currently there doesn't seem to be.

[PG2]

Thanks @CMDB Whisperer . I think you picked up on this quite a while back because I noticed your findings in another community response:  https://www.servicenow.com/community/common-service-data-model-forum/flow-designer-and-business-rule...