Further Guidance on Use and Purpose of Lifecycle Mappings?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2024 02:42 AM
'ello fellow CSDM aficionados! 🙂
Does anyone know of any guidance that exists (or perhaps maybe coming soon in the next release of the CSDM whitepaper...) for better making use of the CSDM Life Cycle (stage and status) fields?
The clearest proposal for how to use I've seen so far comes from this community post (CSDM 4.0: (any) Status attribute vs. Life cycle - ServiceNow Community), but I'd rather see something from the CSDM product team (ideally) or hear from customers or partners who have made this work in a live process.
The two main parts that still confuse me are:
1. It seems like the intent is to make the state(s) consistent across asset and CI, but there is no synchronization (that I can see) between the life cycle stage and status fields between asset and CI records, and in some cases even the statuses available differ for the same stage.
2. Is it intended that customers cease using the old fields entirely or (as suggested in the community post above) is the idea simply to continue to use those fields and have the life cycle stage and status fields as a way of standardizing? If so, which legacy fields should still be used for what purposes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2024 04:44 AM
Maybe the following video is helpful: https://youtu.be/GluOG7aHiGk?si=cD7Qmdya1zG31kW7&t=2004
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2024 08:07 PM
Hi @G_Ede
You can refer this video it might be helpful
https://youtu.be/eocv2GbhgfU?si=tNb-yufgxIyPBecV
Mark it helpful and Accept Solution!! If this helps you to understand.