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]

Regarding the below:

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.

This is still not fixed in Vancouver, the Update legacy from CSDM Business Rule is not present on the alm_asset table. It only updates CSDM Lifecycle Status from legacy on Assets.

On the other hand, heard on the Vancouver CMDB webinar: The Unified Map (replacing Dependency Map and Service Mapping map) is dependent on CSDM Lifecycle stage / status. They mentioned that this is among the first to start using it and that Asset was in line as one of the following.. so perhaps there are good things coming in this area.

[Sebastian R_]

They fixed this with Washington. If you now change the Life Cycle values on an asset, state and substate is updated accordingly, but this leads to multiple issues.

1. OOTB if you set Operational / In Use, state is set to consumed and ACL prevents further editing
2. Various UI Policies / Business rules run afterwards and you see the impact only after saving, e.g. clearing assigned to after retirement etc.

Hope they will sort this out soon or remove the legacy functionality completly