Lifecycle synchronisation for Configuration Items without Assets

[JakePowers]

Hello,

As per Enabling CSDM life-cycle sync between asset and CI to support product instance, there is no longer a direct synchronisation between legacy field values and lifecycle values for records within cmdb_ci. Instead, these records get their lifecycle values from their Asset counterpart. This works if there is an Asset linked to a CI, but this is not always the case, such as with the Service table (cmdb_ci_service). Consequently, the records in this class are no longer updated properly when a change is made to the value of one of the legacy status fields.

Is this by design, and if so, how should the lifecycle fields in these assetless Configuration Item classes be approached?

[Padraig O_Kane1]

I'm running into similar issues where we've loaded in Business Processes and want to filter out any obsolete processes so that they cannot be chosen on an INC or a CHG. I added a Lifecycle Mapping record to change Operational Status to Retired when Lifecycle Status is Obsolete and set the Reverse Sync Choice to true but when the Lifecycle Status of a Business Process is set to Obsolete, Operational Status is still 'Operational'. We therefore can't exclude those from the out of the box filter. I've had to introduce a flow to counteract this and set the Op Status accordingly...which isn't ideal but it's a temporary fix until they resolve the issue. 

[damianfell]

Has anyone figured out how to enable the sync in a brand new instance for service instances? obviously none of them have a corresponding asset record.

We're looking at only using CSDM stage and status when we re-platform, and whilst I don't think we need to update the operational status manually - I have a suspicion some ITOM alert and event functionality might not work if a service instance has got a null value for operational status.