Best practice CSDM Life Cycle adoption for brand new Xanadu instance

declannolan
Tera Contributor

‎01-23-2025 05:16 AM

Hi,

 

I'm implementing a brand new Xanadu instance with CMDB/Asset management supporting a basic ITSM implementation.  Currently there is no Discovery and all CIs/assets will be imported and managed manually for the short-to-medium term.

We have no legacy data that needs converting/mapping and no immediate need for Operational Status values on CIs.  So my question is, what's the best practice in adopting CSDM Life Cycle Stage/Status?  Can we effectively ignore all the legacy status fields (my preference to keep everything nice and clean) and just use LCSS in isolation? (If so, does that mean we don't need to use the "Enable Life Cycle Sync" button on the Life Cycle mappings table?).

Thanks,

Declan

  • 1,387 Views
5 REPLIES 5

declannolan
Tera Contributor

‎01-26-2025 07:07 AM

Ok thanks....I'm still not entirely clear why i need to bother with Life Cycle Mappings if we can effectively ignore the legacy status fields but it's probably just safer to use the "Enable Life Cycle Sync" button on Life Cycle mappings tables.

I really think though that ServiceNow should be able to be more specific in their advice for new instances from Xanadu onwards (rather than only focussing on older instances where mapping is required).

Thanks,

Declan

0 Helpfuls