All,
I am currently working through an issue with life cycle mappings and I am curious if anyone else has encountered this.
In our instance we are seeing that when cmdb_ci_vm_instance CI's are updated by discovery to a install_status of "retired" that the life cycle fields do not also update. Additionally we are seeing that when the cmdb_ci_vm_instance is retired, if it has a relationship to a cmdb_ci_win_server object the cmdb_ci_win_server object is being set to retired but its life cycle stage and life cycle stage status aren't being updated.
We are totally OOB from a life cycle mapping perspective.
In reviewing ServiceNow's documentation for Life Cycle Mappings https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag... it tells us "Applies to a descending table unless there is a mapping configured specifically to the descending table." - as far as I can tell the OOB mappings for cmdb_ci should be applying to cmdb_ci_win_server and cmdb_ci_vm_instance.
I reached out to ServiceNow Support and so far the answer I've been given is that life cycle mappings DO NOT apply to descending tables. Which runs counter to my interpretation of the ServiceNow Product documentation.
Curious if anyone else has encountered this issue.
