I have enabled Enable Life Cycle Sync under Life cycle mappings table in CSDM.

[Pravitha]

I have enabled "Enable Life Cycle Sync" under Life cycle mappings table in CSDM. All the data are now synced and automatically populated with Life cycle stage and Life cycle stage status values mapped in the Life cycle mappings table. After the sync, I'm manually updating one of the table record's operational status from operational to Retired, but the life cycle stage and life cycle stage status are not updated automatically. As per my understanding, the life cycle stage and life cycle stage status should be automatically updating by the system if any change occurs to the operational status/install status/hardware status (whatever the mappings defined in Life cycle mappings table).  I have installed Activate the CSDM Activation (com.snc.cmdb.csdm.activation) plugin. as per the https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag....

Can anybody please help where I'm missing, and do I have to enable any other configurations to work this mechanism.

[Damhoej]

In the white paper for csdm v5 there is a paragraph on life cycle mapping..

https://learning.servicenow.com/nowcreate?id=nc_asset&asset_id=3d7283e997616214e4fb72de2153af39&nc_s...

[ravi112]

@Pravitha Did you figure out the issue ?

[Louis28]

Hi @Pravitha,

If you're migrating to the Life Cycle Stage / Life Cycle Stage Status from the earlier status fields (Install Status, Operational Status, Hardware Status), there is a one-time sync tool you can run (so long as you're Xanadu or later). 

If you're already up and using LCS/LCSS as your primary attributes, you will need to have defined unique mappings for the particular table, the LCS/LCSS, and Life Cycle Control [life_cycle_control]. The same LCS/LCSS combo on a class cannot be used for different legacy mappings. Be sure to keep mind to the Priority for each Life Cycle mapping entry and ensure you don't have conflicting classes (ie cmdb_ci_serivce & cmdb_ci_service_auto) for a Service Instance. Also ensure that the LC Control that you are using is Active.

In case you're trying to sync across CIs & Assets, also check the Asset-CI Install Status Mapping [alm_asset_ci_state_mapping] and Asset-CI Hardware State Mappings [alm_hardware_state_mapping].

Next option is to check Business Rules which run. You'll need to unravel the OOTB logic and see if you need to introduce any Business Rules to manage the syncing.

Last but not least, check out CMDB Data Manager settings (CMDB Workspace -> Data Manager -> Settings) and review the list of active Retirement definitions.

[MDAQUIBK]

@Pravitha 

Did you fix the issue ? I am also facing the same issue .