Restrict CI insert/update in CMDB when operational status is 'Retired'

[Nishant16]

I need to restrict CI's insert/update in CMDB when the Operational status is 'Retired' from a CI. For this i tried writing a business rule on condition 'Operational status' is 'Retired' and abort the action, however it doesnot work, even when i update the operational status from 'Operational' to 'Retired' then also it gives the error and cannot update the CI operational status to retired.

why the Business rule fail when the Operational status is still 'operational' and not updated to 'Retired' still gives an invalid update error.

Can someone suggest? what is the best approach to restrict ci insert on Retired Operational status?

[Nishant16]

i only want the updates to be restricted on Retired status, it will work the same as it is now

[Dr Atul G- LNG]

Did you try UI policy? 

[Nishant16]

how would UI policy help here? can you suggest why the Business rule wont work here?

[Michael de Boer]

Hi @Nishant16,

Create the following business rule with "changes from retired"

[Pratiksha]

Create a reconciliation rule. You need to give the discovery source and filter will be on install status. That will do