- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2024 04:16 AM
Hi,
The Life cycle mappings table provide a mapping for the legacy status fields of the CMDB classes.
In case a class do not have a specific mapping defined for it, the system should go trough the class's parents list until it find a mapping.
So having the mapping on class cmdb_ci should be enough to handle all the CIs.
But when I disabled all the mapping but the ones for cmdb_ci, I get the value "To Be Determined" into the CSDM status fields.
Is there is something to add, configure or correct to make use of the inheritance of the classes?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2024 05:08 AM
I've found the reason why it is not working;
If a mapping is marked as inactive, it is still taken into account by the update script but its value is not used.
To ignore a mapping, it must be deleted.
So what is the utility of having the "Active" attribute? 🙄 It would be very simple to only retrieve active mappings in the update script.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2025 07:34 PM
A defect in 2024, for the basic Lifecycle mapping ability? Does any testing actually get done at SN, or do they expect all their customers to do that for them, as part of their ENTERPRISE contractual agreement?
