Asset State Not Updated When Hardware CI Install Status Is Changed<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; max-width: 100%; } .kb-wrapper h2 { font-family: 'Lato', sans-serif; font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 24px; margin-bottom: 10px; } .kb-wrapper p { font-family: 'Lato', sans-serif; font-size: 12pt; margin-top: 0; margin-bottom: 10px; } .kb-wrapper ul, .kb-wrapper ol { font-family: 'Lato', sans-serif; font-size: 12pt; margin-top: 0; margin-bottom: 10px; padding-left: 24px; } .kb-wrapper li { margin-bottom: 6px; } .kb-wrapper code { font-family: 'Courier New', Courier, monospace; font-size: 11pt; background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 14px 0; font-size: 12pt; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 14px 0; font-size: 12pt; } .kb-wrapper .related-links-list { list-style: none; padding-left: 0; } .kb-wrapper .related-links-list li { margin-bottom: 8px; } .kb-wrapper .link-disclaimer { font-size: 10pt; font-style: italic; color: #444; margin-top: 2px; margin-bottom: 10px; } .kb-wrapper a { color: #032D42; } Issue An Asset record's State field does not update when the Install Status of its related Hardware CI record is changed. Symptoms Updating the install_status field on a Hardware CI record does not trigger a corresponding State update on the linked Asset record.The Asset-to-CI direction works as expected: setting an Asset to a state such as In Stock / Pending Install correctly updates the CI's install_status. However, the reverse — CI to Asset — does not apply for Hardware CI classes.Toggling the CI's install_status away from Installed and back again may trigger the sync correctly in some cases. The issue is specific to scenarios where hardware_status and hardware_substatus have not changed alongside install_status. Facts This is expected platform behavior for Hardware CI classes. The AssetAndCISynchronizer Script Include governs Asset↔CI synchronization and gives precedence to hardware_status and hardware_substatus over install_status when evaluating Hardware CIs.When neither hardware_status nor hardware_substatus is included in an update, the synchronizer exits without evaluating install_status, and the Asset State is not updated.Historically, the Business Rule Sync Ops Status for CMDB CI handled synchronization of install_status, hardware_status, and operational_status on CI updates. This Business Rule was deprecated and deactivated across all instances as part of the Yokohama release via the fix script Migrate 'Sync Ops Status for CMDB CI' BR, due to data integrity and performance issues. Release All Versions Cause The out-of-the-box Asset↔CI synchronization logic in the AssetAndCISynchronizer Script Include prioritizes hardware_status and hardware_substatus for Hardware CI classes. When a CI update contains only a change to install_status — with neither hardware_status nor hardware_substatus changing — the synchronizer exits early and does not evaluate install_status. As a result, the linked Asset record's State is not updated. Resolution The following options are available depending on your instance's CSDM adoption status and customization requirements. Option 1 — Activate CSDM Lifecycle Sync (Recommended) If your instance is ready for CSDM lifecycle adoption, enabling the CSDM lifecycle sync system property is the platform-recommended path for managing Asset↔CI synchronization going forward. When the CSDM plugin (csdm.lifecycle.migration.activated) is activated, synchronization between the Asset and CI tables is controlled by the system property csdm.lifecycle.sync.between.ci.and.asset.activated.When this property is set to true, the platform syncs CSDM lifecycle stage and lifecycle stage status values bidirectionally between Asset and CI records, replacing reliance on the legacy install_status, hardware_status, and hardware_substatus field mappings for synchronization purposes. Note: Before enabling CSDM lifecycle sync, review the lifecycle mapping configuration on your instance to ensure all required mappings are present and active. Instances with custom asset states or CI substates may require additional mapping rules. Refer to the official documentation for the full activation procedure. Option 2 — Customize the AssetAndCISynchronizer Script Include (Optional) If CSDM lifecycle adoption is not currently planned, a customization to the AssetAndCISynchronizer Script Include can be implemented to allow install_status changes to drive Asset State synchronization for Hardware CIs when hardware_status and hardware_substatus are not changing. Important: Modifying the AssetAndCISynchronizer Script Include is a customization to a core platform component. Any changes should be thoroughly tested in a non-production environment prior to deployment, and the customization must be reviewed and re-evaluated after each upgrade to ensure continued compatibility. This approach is the customer's responsibility to implement and maintain. Option 3 — Re-enable the "Sync Ops Status for CMDB CI" Business Rule (Not Recommended) Re-activating the deprecated Sync Ops Status for CMDB CI Business Rule would restore the previous synchronization behavior. However, this rule was deliberately deprecated in the Yokohama release due to known data integrity and performance concerns. Re-enabling it is not recommended without careful consideration of those risks. Important: Re-enabling the Sync Ops Status for CMDB CI Business Rule reactivates a component that was deprecated due to known data integrity and performance issues. Any decision to re-enable this rule is the customer's responsibility. It should be thoroughly tested in a non-production environment prior to deployment and reviewed carefully with awareness of the risks that led to its deprecation. Related Links Work with Asset and CIEnabling CSDM life-cycle sync between asset and CI