Understand Xanadu CSDM new feature- enabling CSDM life-cycle sync among CI, asset and IBI

[John Zhang1]

The Common Service Data Model (CSDM) lifecycle sync between Asset and Configuration Item (CI) in ServiceNow is essential for ensuring that the asset and CI records are consistent across the platform, providing a single, accurate source of truth for both physical and logical aspects of IT assets.  Aligning asset and CI data helps ensure that IT services are delivered based on accurate information. For instance, when troubleshooting, the relationship between a CI and its corresponding asset is crucial for identifying issues quickly.

In Xanadu release, ServiceNow has made more easy to enable CSDM life-cycle sync between CI and asset entities.   When the one-time data sync operation finishes, CSDM life-cycle values for each product instance as represented in the asset and CI tables will be identical.

I would like to walkthrough steps to enable CSDM life-cycle from the followings:

CSDM Life-cycle Diagram to be enabled

Overall process is to click Enable life cycle sync on the Life cycle mapping list view, which will set the csdm.lifecycle.sync.between.ci.and.asset.activated system property to true.  However, the discrepancy report displays the list of missing or inactive mappings that you need to repair after clicking this button.  We need to repair all records that are displayed on the discrepancy report.

Step 1 - Open list View of Life Cycle Mapping

Navigate to CSDM Configuration and open a list view of Life Cycle Mapping (see below screenshot).  You will see "Enable Life Cycle Sync" button, which is used to enabling CSDM life cycle among CMDB, CSDM, Asset and IBI.   After you click this button, if there are any missing life cycle role in your record, the discrepancy report will be displayed (see blow),

Step 2 - Results of Discrepancy report 

The discrepancy report (below)  will be displayed after you click "Fix no mapping table" button.  You will see the "Life cycle control" filed is empty.  You need to populate this field value to fix the missing data.

Step 3 - Fix each discrepancy record

Your fixed record will be looks like the following screenshot after mapping Life Cycle Control filed.

Step 4 - Verify Results of Discrepancy report 

Step 5 -CSDM Life-cycle in sync list view

Final results will be displayed below after CSDM lifecycle in sync among CI, asset and IBI.

If you enjoy my ServiceNow posts, please mark my post Helpful.

[Nikhil Bajaj9]

Thanks for sharing.

[diegopeuker]

@John Zhang1 ,

After activating the CSDM Lifecycle, I realized that some classes still didn't have the mapping of legacy fields with the lifecycle, as was the case with Cloud Resource.

After creating this item that didn't appear as a discrepancy, I can't find the Job to force the sync for these components, being the same action that the UI Action Enable Life Cycle Sync triggers when we haven't activated Lifecyle yet. Looking for the Lifecycle Jobs, I haven't found anything either, do you know what the script or Job is that forces the lifecycle of the CI's to be updated after an adjustment/inclusion in the life_cycle_mapping table?

Thank you

[Moe9]

Hi @John Zhang1 ,

Q? How do you know what values to populate to fix the missing data - after running the Discrepancy Report?

Is there a refence to know what lifecycle values correlate to the legacy values?

Thanks.

[Ashi4]

Hi @diegopeuker 

Any update on the job or script that does the sync between the statuses of the CI? I'm also facing the same issue. As I've made some changes in the mapping after enabling the sync.

[AmolJ]

I have these that are not fixed. How to fix them: