if asset life cycle stage &status is changed, will it affect the ci life cycle stage and status

[Community Alums]

HI 

if asset life cycle stage &status is changed, will it affect the ci life cycle stage and status

[Jon Runheim]

Basically, this implies that to be able to use the CSDM Lifecycle attributes and have them synced between the CI and asset, the CI management needs to rely primarily on the hardware_status and hardware_substatus fields and not the install_status fields.

If using the install_status field the sync will no be bi-directional as the Asset-CI sync only syncs the Hardware Status back from the CI to Assets on hardware type CI's.
https://docs.servicenow.com/bundle/vancouver-it-asset-management/page/product/asset-management/task/... 

This is more than mildly confusing for most, let's hope getting Asset to CI sync based on the CSDM Lifecycle Attributes is on a list to get fixed soon..

[Alec Hanson]

Hi,

We have just recently rolled this out so can comment from my experience:

"Given the above, in theory, wouldn't any change to the CI lifecyle, update the legacy status fields from the mappings, which would in turn update the asset with the AssetAndCISynchronizer script include? And visa versa?  

This is correct, if you change the CI lifecycle this will update the legacy status fields, which in turn updates the Asset Status and SubStatus and in turn changes the Asset Lifecycle fields.

However at present (unless fixed in Vancouver) it is not the same in reverse:

1. If you update the Asset Lifecycle values they do not reflect back to legacy Asset fields.

2. If you update the legacy Asset fields they will update the CI legacy and therefore the CI Lifecycle fields.

To achieve this we have had to amend the ordering of the Business Rules around status updates as well as Asset creation as the system will behave differently:

1. Business Rule "Update legacy from CSDM -> Order changed to 999 to happen before Asset Creation

2. Business Rule "Sync Ops Status for CMDB CI" -> order changed to 900

I have spent hours working through this for my client ensuring that the flow works bi-directional between CI Lifecycle <-> Hardware Status/State <> Asset State.

We have also had to make some configuration changes to the mappings to work 100% and also to meet the expectations of the clients

[Community Alums]

Hi Alec Hanson

I followed above steps I modified the order for business rules

 testing in my pid when I change Ci install status on server table it's not updating the life cycle stage & life cycle state status fields on the server table?

any help ?

[Alec Hanson]

Hi, I assume you have performed the pre-requisite CSDM Activation process?

[Community Alums]

Yes I've enabled the Activation button on the life cycle mapping &I have installed plugin  com.snc.cmdb.csdm.activation & set the csdm.lifecycle.migration.activated system property to true