Do I need "Sync Ops Status for CMDB CI" Business Rule?

Bob D
Tera Expert

[Rome]

Do I need the OOB Business Rule "Sync Ops Status for CMDB CI"?    It acts on the Hardware Status value of a CI, and our organization does not maintain or otherwise use this attribute, even for synching with Asset table.  (I understand it is mostly legacy attribute from the pre Asset table days).   Having this Business Rule active has caused some issues.  For example, if a server CI's Hardware Status is Installed and we try to set Operational Status=Retired...this Business Rule sometimes reverts Operational Status to Operational.

Deactivating this BR would solve my problems, I hope.  Do I need this BR active for other reasons?  

1 ACCEPTED SOLUTION

emir
ServiceNow Employee
ServiceNow Employee

It was intended to keep the legacy hardware_status in sync with the then new install_status. Now we have new CSDM lifecycle status codes too.

Check out this portion of my playbook to see if you have any linkages of that code to the asset module.

Once you validate that, you should be able to consider de-activating that BR. also, check this KB to see if this helps your issue.

View solution in original post

1 REPLY 1

emir
ServiceNow Employee
ServiceNow Employee

It was intended to keep the legacy hardware_status in sync with the then new install_status. Now we have new CSDM lifecycle status codes too.

Check out this portion of my playbook to see if you have any linkages of that code to the asset module.

Once you validate that, you should be able to consider de-activating that BR. also, check this KB to see if this helps your issue.