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

[Danish Bhairag2]

Hi @Community Alums ,

No it will not whenever State or Status gets changed in asset it will not have any impact on the CI. But if other fields are changed then it will. You can refer this table alm_asset_ci_field_mapping to see what all fields will be modified on CI as well.

Thanks,

Danish

[Danish Bhairag2 · Accepted solution]

Hi @Community Alums ,

If my response helped you please mark my solution as accepted so that other users can benefit from it.

Thanks,

Danish

[Community Alums]

if we start using the life cycle mapping, do we need use asset ci mapping also?

[Randy Fisher]

@Danish Bhairag2 

I see what you are saying, in that the state and status fields are not in the alm_asset_ci_field_mapping table.  However, there is also the business rule on the asset and CI tables that, in turn, runs the AssetAndCISynchronizer script include which does sync the install status with the asset.  Then there is the table life_cycle_mapping for maintaining the mappings between legacy install status and operational status with the new lifecycle stage and lifecycle status.  

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?  

Again, this is just theory, we are not using the lifecyle fields yet but would like to start looking into it.  This is certainly not a very efficient model as well but it seems like it would work, right?

Ultimately, it is past time for ServiceNow to address this.  They release the concept of lifecycle with CSDM but with the caveat of not using it fully yet.  When are they going to address the gaps in other tables?

Thanks,

Randy