- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 10:14 AM
Hi all,
We have activated CSDM life cycle mappings in our instance and some of the CIs are set as "To be determined" in lifecycle stage and lifecycle status. All these CIs has install_status as "Retired"
Does anyone have an idea on how to resolve this issue?
Your help is much appreciated.
Thanks,
Vennila
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2024 11:21 AM
In what classes are those CIs? As pointed out, you get this value when the Life Cycle Mapping could not find a mapping entry for your combination of class, legacy status field and value.
When you activate Life Cycle Mapping, a script does a mass once-off update of life_cycle_stage and life_cycle_stage_status.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2024 06:51 AM - edited 03-08-2024 06:54 AM
The OOB Life cycle mapping should set the Life Cycle Stage to "End of Life" and the Live Cycle Stage Status to "Retired".
I suggest you confirm that this mapping is active in your instance. You can also do a mass update to set these fields manually. Or depending on the number of records you have, use the Import feature to get an Update spreadsheet.
Here is how it looks OOB

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2024 11:21 AM
In what classes are those CIs? As pointed out, you get this value when the Life Cycle Mapping could not find a mapping entry for your combination of class, legacy status field and value.
When you activate Life Cycle Mapping, a script does a mass once-off update of life_cycle_stage and life_cycle_stage_status.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2024 03:54 AM
Hi all,
Thanks for the reply.
The mappings fall back to the base table when there are no specific mappings created for the tables.
In our case , we created life cycle mappings for the application table and missed out to create mapping for retired status. Hence , it was set to "to be determined"
Thanks,
Vennila

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2024 02:57 PM
If my previous reply was helpful in getting to your solution, can you please mark it so.
Thank you