Looking for details on a system business rule called "Sync Ops Status for CMDB CI"

[pcorbin]

For the business rule "Sync Ops Status for CMDB CI" that is auto-updating the operational_status and install_status on a CI, I need to understand if this rule is part of CI Lifecycle Management, ITAM or some other process. I cannot find any information about this rule and it's impacting the status indicators on our CIs.

Example: If a Service Offering CI has an install_status of <NULL> and the Operational status is changed to "Retired", the install_status gets set to 'QA'. Inversely, if the install status is set to 'QA' and the Operational status is set to retired, by updating any other column on the record will force the operational status to change to "Non-Operational".

Not sure if this part of CI Lifecycle Management or a core feature. Need to understand it. 

[christianmalone]

Core feature and loosely associated with the Asset-CI status sync as well. https://docs.servicenow.com/bundle/madrid-it-service-management/page/product/asset-management/concept/c_ManagingAssets.html

[pcorbin]

Thanks Christian, I've read all that before, but the service offering is not an asset record; only a CI record so the behavior is still not explained. It does call out the hardware status integrations of which I'm familiar, but not the specific syc script I mentioned above. 

[pcorbin · Accepted solution]

For those interested I figured out the basics on this business rule. The Operational Status and Status (install_status) are linked, especially with respect to the state of "Retired". If one is set to retired the business rule ensures that the other is also set to retired. The same applies for the Hardware Status and sub-status.

In short, the platform is ensuring that you can't have an ops status of retired and an install status of something else other than also retired. This is to ensure data quality remains high.