How are the Asset and CI Lifecycle Stage and Status fields synced?

[Erick18]

After adding the new lifecycle stage and status fields to the Hardware Asset table and the Hardware CI table I noticed that the status are not staying in sync. The scenario is that I updated the life cycle stage and status field on the Hardware record but the CI fields don't sync and vice versa. Is there a process that should be running to keep these in sync or can I add the Lifecycle fields to the existing Asset - CI Field Mapping table (alm_asset_ci_field_mapping)?

Thanks,

Erick

[HeatherC1]

It is located in this table alm_asset_ci_field_mapping.list 

[Erick18]

There is not an entry on that table for Lifecycle Stage or Lifecycle Stage Status as of Rome Patch 5. 

[shloke04]

Hi @Erick 

Asset-CI mapping and synchronization

The State field of asset record and Status field of CI record are synchronized so that changes made on one form trigger the same update on the corresponding form, ensuring consistent reporting.

Note: The Now Platform synchronizes updates between assets and configuration items only if the asset and configuration item are pointed toward each other.

The following diagram illustrates the concept of Asset-CI mapping and synchronization.

Asset-CI mapping and synchronization: An Overview

This synchronization and mapping is based on the following factors:

• Asset state and CI status are not mapped on one-to-one basis; rather they are mapped to the most logical counterpart on the other table. For example, for a hardware asset set to state In Stock - Pending disposal, the corresponding CI is set to In Disposition with no substate.
• This synchronization happens between the asset’s State field and the following CI fields:
  • Install Status field: Install Status does not have a sub status and must be used for non-hardware CIs.
  • Hardware Status and Sub status field: Hardware Status is visible only for Hardware CI.

• Drive changes by updating the state on the Asset form. The Asset-CI synchronization can be driven in the following ways:

  • Asset to CI synchronization: Change to the asset’s status updates the logically mapped CI’s Install Status or Hardware Status and sub status.
  • CI to Asset: Change to the CI’s activate Status or Hardware Status updates the logically mapped asset’s states and sub states.
• For a CMDB hardware CI, if both Hardware Status and Install Status is updated, the Hardware Status change is considered for mapping the corresponding state of the asset.
• CI’s Install Status and Hardware Status work independently, so the two fields aren't related. CI’s Hardware Status change does not change CI’s Install Status and vice versa. To avoid confusion, keeping both status for CMDB CI Hardware is not recommended.

This has been taken and discussed clearly in ServiceNow doc, please have a look at below link:

https://docs.servicenow.com/bundle/quebec-it-service-management/page/product/asset-management/concept/c_ManagingAssets.html

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[Scott Halverso1 · Accepted solution]

I agree Erik, it feels like a miss in the product. 

If you migrate to use the new lifecycle fields and update the value on the asset side there is nothing syncing lifecycle to the cmdb. 

On the CMDB side if you update the lifecycle fields, there is a business rule called update legacy from CSDM.  That BR goes and updates the legacy CI status fields which then if mapped in the syncer tables as Shloke mentioned above, will sync to the legacy asset fields which then hit a BR on asset called Update lifecycle from legacy which then update the assets lifecycle fields.  A big Rube Goldberg machine.

It doesn't feel like these fields are ready for prime time which is probably why ServiceNow's CSDM team to date only advised clients to start migrating to the new lifecycle construct on the hardware models.